Database Develop

[ROM][onyx][7.1.x][OFFICIAL][WEEKLIES] Lineage Android Distribution for OnePlus X

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.
Code:
#include
/*
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
KNOWN ISSUES
- Report with logs
!!! BUG REPORTS WITHOUT LOGS WILL BE IGNORED !!!
Android: adb logcat
Radio: adb logcat -b radio
Kernel: adb shell dmesg
Full Bugreport: Developer Menu -> Bugreport
HOW TO INSTALL LINEAGEOS
- Make sure your phone is running Marshmallow bootloader
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Unlock bootloader and install TWRP.
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- IMPORTANT: Do a Factory Reset. (Wipe data & cache)
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
DOWNLOADS
LineageOS:
https://download.lineageos.org/onyx
Old Downloads :
https://github.com/ashwinr64/LineageOSUpdater-API/releases/
Google Apps:
OpenGApps (recommended: arm, 7.1.1, nano)
SOURCECODE
Device tree: https://github.com/LineageOS/android_device_oneplus_onyx
Kernel: https://github.com/LineageOS/android_kernel_oneplus_onyx
HOW TO CONTRIBUTE
Use our code review system to send patches: https://review.lineageos.org
HOW TO BUILD
- repo init -u ssh://[email protected]/LineageOS/android.git -b cm-14.1
- add local manifest to .repo/local_manifests/
- repo sync -j4
- . build/envsetup.sh
- brunch onyx
Local manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="LineageOS/android_device_oneplus_onyx" path="device/oneplus/onyx" remote="github" />
<project name="LineageOS/android_kernel_oneplus_onyx" path="kernel/oneplus/onyx" remote="github" />
</manifest>
SUPPORT ME
Do you like my work? Consider donating me some beer!
​
XDA:DevDB Information
LineageOS, ROM for the OnePlus X
Contributors
ashwin007
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2017-01-13
Last Updated 2017-01-27

Reserved
Changelog:
17/1:
-Synced with Lineage.
-Sneak peak of our new bootanimation ;P
-Fixed the string derp in Settings dashboard.
-Added support for automatic updates.
NOTE: I'll look into the incall audio very soon. Users need to flash superSU separately in order to have SU , we are planning on an addon SU release
.
10/1:
-Rolled back to old RIL stack , no more network instabilities
-Enabled SDcardfs
-WiFi hotspot fixed.
-No need to flash 3rd party kernels ( sorry for the delay guys,no network here,STILL :/ )

First!!
Going to flash it later today!
Edit- running smoothly with stock kernel and dynamic gapps!!
Hotspot working! And every thing else I tried.
One bug I guess(see ss ).

for me

Download queued ... Thank you
Edit: Finally get some LinOS logos, nice!

Super Machi

Sactgr said:
Going to flash it later today!
Edit- running smoothly with stock kernel and dynamic gapps!!
Hotspot working! And every thing else I tried.
One bug I guess(see ss ).
Click to expand...
Click to collapse
It isn't a bug but yeah will fix it in next build

@ashwin007 Thanks a lot Happy new year, btw!
Did you manually fix the kernel because other builds (Lineage and AICP) still require you to flash the kernel? Just asking out of curiosity.

I'm eager to see it here! Nicely done @ashwin007

BrokenBee said:
@ashwin007 Thanks a lot Happy new year, btw!
Did you manually fix the kernel because other builds (Lineage and AICP) still require you to flash the kernel? Just asking out of curiosity.
Click to expand...
Click to collapse
Must've fixed something as it's listed as fixed in the changelog.

The Bug that the preferred Sim changes after every reboot from Sim2 to Sim1 still persists.

Not official, but very close to what the first official weekly will be

The bugs i found out-
1.In call volume control for earpiece(speaker works fine)
2.Split screen size changing.
3.The file explorer
4.In the camera app the shutter sound option doesn't work.
Btw huge thanks to @ashwin007 to let us have a hands-on on possibly the best 7.1 rom till date.

Exciting!
Works fine so far!

Shall i flash arsenic kernal or not?

aryaraj said:
The bugs i found out-
1.In call volume control for earpiece(speaker works fine)
2.Split screen size changing.
3.The file explorer
4.In the camera app the shutter sound option doesn't work.
Btw huge thanks to @ashwin007 to let us have a hands-on on possibly the best 7.1 rom till date.
Click to expand...
Click to collapse
Have you tried the other LineageOS builds?

shyamalgarg said:
Shall i flash arsenic kernal or not?
Click to expand...
Click to collapse
Shall you or should you? You don't need to (see changelog).

can i dirty flash this over CM14.1-20161207-UNOFFICIAL Build?

Monitormann said:
can i dirty flash this over CM14.1-20161207-UNOFFICIAL Build?
Click to expand...
Click to collapse
I make it, and work fine, but in 20161222
Enviado desde mi ONE E1001

The ROM is perfect at least the way I use it. What I don't understand is why the signal strength fluctuates so much and drops off completely. It's not something I experienced in this ROM but in all nougat Roms. I'm getting a range of -90 to -109 dBm and I see the indicator drop off completely. I wonder if I may miss a call or text, if I initiate a call the indicator will jump up and once off call it drops off again. It something that is not present in OOS. (OOS avg. -70 to -90 dBm)

[ROM][ham][7.1.x][OFFICIAL][WEEKLIES] Lineage Android Distribution for ZUK Z1

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.
Code:
#include
/*
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
KNOWN ISSUES
- Report with logs
!!! BUG REPORTS WITHOUT LOGS WILL BE IGNORED !!!
Android: adb logcat
Radio: adb logcat -b radio
Kernel: adb shell dmesg
Full Bugreport: Developer Menu -> Bugreport
HOW TO INSTALL LINEAGEOS
- Make sure your phone is running the firmware last shipped on cm-13.0.
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Unlock bootloader and install TWRP.
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- IMPORTANT: Do a Factory Reset. (Wipe data & cache)
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
* * * MODERATOR WARNING: users who violate FORUM RULES in this thread will have their account restricted or disabled without further warning! Please follow Forum Rules when posting * * *
- Reboot
DOWNLOADS
LineageOS:
https://download.lineageos.org/ham
Google Apps:
OpenGApps (recommended: arm, 7.1.1, nano)
SOURCECODE
Device tree: https://github.com/LineageOS/android_device_zuk_ham
Kernel: https://github.com/LineageOS/android_kernel_cyanogen_msm8974
HOW TO CONTRIBUTE
Use our code review system to send patches: https://review.lineageos.org
HOW TO BUILD
- repo init -u ssh://[email protected]/LineageOS/android.git -b cm-14.1
- add local manifest to .repo/local_manifests/
- repo sync -j4
- . build/envsetup.sh
- brunch ham
Local manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="LineageOS/android_device_zuk_ham" path="device/zuk/ham" remote="github" />
<project name="LineageOS/android_kernel_cyanogen_msm8974" path="kernel/cyanogen/msm8974" remote="github" />
</manifest>
SUPPORT ME
Do you like my work? Consider donating me some beer!
​
XDA:DevDB Information
LineageOS for Ham, ROM for the Lenovo Zuk Z1
Contributors
ashwin007
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2017-03-07
Last Updated 2017-03-07

Thanks man for your work and also for bringing Official Los 14.1 for this device:victory:

Good job.

Already installed.
Thanks a lot..
Sent from my ZUK Z1 using Tapatalk

needs a fresh install. will not install over unofficial Lineage.

Thanks man!
Inviato dal mio ZUK Z1 utilizzando Tapatalk

Do I need to install CM 13 or would a clean flash over unofficial CM 14.1 work?

Really great to see official LineageOS for ham :good:

ddishu2 said:
Do I need to install CM 13 or would a clean flash over unofficial CM 14.1 work?
Click to expand...
Click to collapse
Clean flash over CM14.1 unofficial.

Finally!! Thanks a lot.

Great. Thanks a lot. Can I try a dirty install over unofficial Lineage 30.1.17?

Thanks a lot.
bug:
ipv6 usb tethering not working.
it possible to add ipv6 USB tethering in this ROM ??
any unofficial patch available?

Thank you @ashwin007 ! Great job, everything is perfect here.
One question, can we make FINGERPRINT UNLOCK without pressing the button? To be able to use touch home button without pressing it.
It was possible on the unofficial rom and as well on official LOS14.1 for Mi5 it's working perfectly.
If it's not possible can you provide separated fix?
Thank you!

At last. Thanks for great job. LOS 14.1.1.

I am getting some error while flashing this ROM.. please check out my screenshot and guide me.

tanmeshn said:
I am getting some error while flashing this ROM.. please check out my screenshot and guide me.
Click to expand...
Click to collapse
Mate you sure you're not directly coming from COS? If you are, you might want to flash MM Firmware first and then try flashing the zip.
This error usually occurs when the present firmware isn't up to date.

I am facing very slow charging rate..

Shivver said:
Thank you @ashwin007 ! Great job, everything is perfect here.
One question, can we make FINGERPRINT UNLOCK without pressing the button? To be able to use touch home button without pressing it.
It was possible on the unofficial rom and as well on official LOS14.1 for Mi5 it's working perfectly.
If it's not possible can you provide separated fix?
Thank you!
Click to expand...
Click to collapse
it doesn't need to press. Just touch.
---------- Post added at 06:27 AM ---------- Previous post was at 06:24 AM ----------
sahu.prashant said:
Mate you sure you're not directly coming from COS? If you are, you might want to flash MM Firmware first and then try flashing the zip.
This error usually occurs when the present firmware isn't up to date.
Click to expand...
Click to collapse
here too. i flashed it after wipe /system /data /cache
so i disabled check zip...

sahu.prashant said:
Mate you sure you're not directly coming from COS? If you are, you might want to flash MM Firmware first and then try flashing the zip.
This error usually occurs when the present firmware isn't up to date.
Click to expand...
Click to collapse
Mate I tried many Roms.. and currently I am using CM13 latest and last official nightly ... Don't know why I am getting that error.

tanmeshn said:
Mate I tried many Roms.. and currently I am using CM13 latest and last official nightly ... Don't know why I am getting that error.
Click to expand...
Click to collapse
Now that's funny.... :silly:
Like @magnet1215 suggested you can try disabling check zip signature in TWRP settings.
If that doesn't work either, I'm sorry I'm outta ideas then.

[ABANDONED][ROM][7.1.2][UNOFFICIAL] dotOS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
" #DroidOnTime "
Code:
/*
*
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
*
"This is a user friendly thread, all your suggestions are important to us and will be taken into consideration.."
dotOS is an Android Rom which focuses on performance and stability. Our aim is to enable a user to extract as much juice as possible and get most out of his/her device.
Initially started by Mohan CM and later joined by Ganesh, Sam, Kuber, Iacob and Hari. Together we stand strong.
Stability and Performance
Lagfree with High Performance Results
Clutterless UI
Perfect Interface for every User
Enhanced default apps
Redesigned settings and QS panel
Full OMS support
Colour Engine Support
DotExtras
STATUSBAR
* Clock Customisation
* Battery Customisation
Quick Settings
* Quick Pulldown
* QS Tiles Customisation
* Advanced Quick Setting Easy Toggles
Buttons
* Volume Key Cursor Control
Display
* Wake on Plug
* Pocket Detection
* Accidental Touch
Lockscreen
* Fingerprint Tweaks
* Powermenu Tweaks
* Double tap 2 sleep anywhere
* Lockscreen Media Customisation
* Blur Screen Lockscreen
Recents
* Clear all Button
* Immersive Recents
* Show Memory Bar
Navigation Bar
* On screen navigation Bar tweaks
* Home Button tweaks
* Menu Button tweaks
* Back Button tweaks
* Power Button tweaks
* Volume Buttons tweaks
Misc
* Advanced Reboot
* Disable Force Close
* ScreenShot Tweaks
* Camera Shutter Sound
CLEAN FLASH :
Download the latest build and GApps
Reboot to recovery
Make NAndroid backup (Not Necessary)
Wipe System, Data, Cache , Dalvik
Flash the latest build and GApps
Reboot
DIRTY FLASH :
Download the latest build
Reboot to recovery
Flash the latest build
Wipe Cache
Reboot
Download ROM:
DotOS v1.2
Download Gapps:
Note : Pico or Nano Gapps are recommended. We Don't prefer STOCK/HEAVY Gapps
OpenGapps
dotOS team
LineageOS team
ResurrectionRemix team
AospExtended
crDroid team
AICP team
And all other open source Devs/Teams.
Djeman (Main Developer)
Danijel (Developer and Tester)
PixelBoot (Developer and Thread Manager)
BUGS
Wi-Fi Connections
#AlignTheDots
​
XDA:DevDB Information
dotOS N, ROM for the Samsung Galaxy J3 (2016)
Contributors
PixelBoot, [email protected], djeman
Source Code: https://github.com/djeman
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Abandoned
Created 2019-06-24
Last Updated 2020-01-26

I don't recommend installing dotOS in it's status right now.
I had a hard time dealing with sources, resulting in Wifi issues.
But if you want to take a look, go ahead!

PixelBoot said:
I don't recommend installing dotOS in it's status right now.
I had a hard time dealing with sources, resulting in Wifi issues.
But if you want to take a look, go ahead!
Click to expand...
Click to collapse
Screenshots pleaaasee

GabiML said:
Screenshots pleaaasee
Click to expand...
Click to collapse
Here they are!

PixelBoot said:
Here they are!
Click to expand...
Click to collapse
Hey! PixelBoot what sources did you use in local_manifest.xml?? Please put all of the links!!! Thank you ^^

Andissace said:
Hey! PixelBoot what sources did you use in local_manifest.xml?? Please put all of the links!!! Thank you ^^
Click to expand...
Click to collapse
I used djeman's local_manifest, but changing the device tree to danijel's version.
I am aware of the wifi error being due to some sources being changed by me
I had many errors while building so some stuff had to be cut out (I think...)
I hardly think it is due to provided sources.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="external/busybox" name="LineageOS/android_external_busybox" revision="cm-14.1" />
<project path="external/stlport" name="LineageOS/android_external_stlport" revision="cm-14.1" />
<project path="packages/apps/SamsungServiceMode" name="LineageOS/android_packages_apps_SamsungServiceMode" revision="cm-14.1" />
<project path="hardware/samsung" name="LineageOS/android_hardware_samsung" revision="cm-14.1" />
<project path="external/sony/boringssl-compat" name="LineageOS/android_external_sony_boringssl-compat" revision="cm-14.1" />
<project path="bootable/recovery-twrp" name="omnirom/android_bootable_recovery" revision="android-7.1" />
<project path="vendor/nxp-nfc/opensource/Nfc" name="LineageOS/android_vendor_nxp-nfc_opensource_Nfc" revision="cm-14.1" />
<project path="vendor/nxp-nfc/opensource/frameworks" name="LineageOS/android_vendor_nxp-nfc_opensource_frameworks" revision="cm-14.1" />
<project path="vendor/nxp-nfc/opensource/libnfc-nci" name="LineageOS/android_vendor_nxp-nfc_opensource_libnfc-nci" revision="cm-14.1" />
<project path="device/samsung/j3xnlte" name="danijelj2001/android_device_samsung_j3xnlte" revision="cm-14.1" />
<project path="kernel/samsung/j3xnlte" name="djeman/android_kernel_samsung_j3xnlte" revision="cm-14.1" />
<project path="vendor/samsung/common" name="djeman/android_vendor_samsung_common" revision="cm-14.1" />
<project path="vendor/sprd" name="djeman/android_vendor_sprd" revision="cm-14.1" />
</manifest>

PixelBoot said:
I used djeman's local_manifest, but changing the device tree to danijel's version.
I am aware of the wifi error being due to some sources being changed by me
I had many errors while building so some stuff had to be cut out (I think...)
I hardly think it is due to provided sources.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="external/busybox" name="LineageOS/android_external_busybox" revision="cm-14.1" />
<project path="external/stlport" name="LineageOS/android_external_stlport" revision="cm-14.1" />
<project path="packages/apps/SamsungServiceMode" name="LineageOS/android_packages_apps_SamsungServiceMode" revision="cm-14.1" />
<project path="hardware/samsung" name="LineageOS/android_hardware_samsung" revision="cm-14.1" />
<project path="external/sony/boringssl-compat" name="LineageOS/android_external_sony_boringssl-compat" revision="cm-14.1" />
<project path="bootable/recovery-twrp" name="omnirom/android_bootable_recovery" revision="android-7.1" />
<project path="vendor/nxp-nfc/opensource/Nfc" name="LineageOS/android_vendor_nxp-nfc_opensource_Nfc" revision="cm-14.1" />
<project path="vendor/nxp-nfc/opensource/frameworks" name="LineageOS/android_vendor_nxp-nfc_opensource_frameworks" revision="cm-14.1" />
<project path="vendor/nxp-nfc/opensource/libnfc-nci" name="LineageOS/android_vendor_nxp-nfc_opensource_libnfc-nci" revision="cm-14.1" />
<project path="device/samsung/j3xnlte" name="danijelj2001/android_device_samsung_j3xnlte" revision="cm-14.1" />
<project path="kernel/samsung/j3xnlte" name="djeman/android_kernel_samsung_j3xnlte" revision="cm-14.1" />
<project path="vendor/samsung/common" name="djeman/android_vendor_samsung_common" revision="cm-14.1" />
<project path="vendor/sprd" name="djeman/android_vendor_sprd" revision="cm-14.1" />
</manifest>
Click to expand...
Click to collapse
Thank you so much for taking your time!

Everything seems to be working fine except wi-fi as you said

I installed the rom .. everything was pretty amazing
I love the smooth animations and the quiz settings that mimics the Android O
But the placement of date and time in quick settings is annoying i hope i can fix it ..and wifi is already a bug .
Other than that everything is perfect .
Prettiest rom till date?

whether later can update from ota?

Wi-Fi not work?

Fo rme same question: What excat is the wifi bug? General or sometimes?
I ask because some had wifi (disconnecting ) probs also with lineage 13/14 - but i never with same builds. In this case seems be depedency which wlan routers used/serve wifi.

BEST ROM !!

PixelBoot said:
Here they are!
Click to expand...
Click to collapse
Maybe in free time you will try to port UBPorts to our device? ^^ https://docs.ubports.com/en/latest/porting/introduction.html :highfive:
PLEASE READ EVERYTHING VERY CAREFULLY!!!
Start with building Halium!
Build like any custom LineageOS rom!

Korzin146 said:
Wi-Fi not work?
Click to expand...
Click to collapse
no, it isn't working, developers don't have enough time to fix this issue

I think this rom is little bit slow

ntrimurthulu said:
I think this rom is little bit slow
Click to expand...
Click to collapse
Turn off live display

Volte work ?

I like los, rr, oct-n roms, nougat roms only working fine in my device.
Im looking for new nougat rom with new ui style.
I have not try this rom because wifi bug you have said.

I really like this ROM, the look and the feel. Too bad the wifi is the bommer. I see comments in the different threats that TIME is a problem. Why not make one or 2 or 3 ROM's good and stable , instead of creating many different ROM's and not be able to finish the programming of the ROM's.

[ROM][8.1.0][UNOFFICIAL] /e/ For Osprey

/e/​
As always, you take responsibility for what you do to your phone. Don't go filing civil lawsuits against me if your alarm fails to get you up for work in the morning.
The Hell's An /e/?
"/e/ is a non-profit project, in the public interest. We build open-source mobile operating systems that respect users’ data privacy. We’re an international core team of experienced entrepreneurs, developers and designers, and a growing community of contributors." --taken from their website.
Basically think Lineage AOSP but instead of just leaving gapps out of it, they're trying to take it a step further and really give Google the finger. Their ultimate goal for the future is to make a mobile OS featuring an entire ecosystem (/e/cosystem?) that respects users' privacy and avoids the "big-companies-that-sell-your-data". They will have alternatives to the most popular Google services baked in: F-Droid instead of Google Play, something like Telegram instead of Google Hangouts, Bliss with an icon pack instead of a proprietary Google launcher, etc.
What Works?
Everything except what's listed below!
What Don't Work?
--There's no market for apps built in, so you'll have to use the browser to grab an APK of FDroid or something after install (in a future build I'll try to include FDroid in there)
--Verizon data seems a bit weird, like it'll work fine for a little bit then decide it doesn't want to and quit later on as soon as you reboot. What you need to do is reboot the phone with the SIM card taken out, then reboot it again with it back in and it'll work again. If this still doesn't work, changing the APN to Straight Talk Verizon apparently worked for some people
--USB OTG is apparently broken as well
Where's My Source Code, and How'd You Build this?
Don't worry, this took me forever to find too. I used the V1-oreo branch which is Lineage 15.1 based. The trees I'm using come from The Moto8916 Github Repo.
Here's the roomservice XML I used so you don't have to manually add it all yourself
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Device -->
<project name="moto8916/android_device_motorola_osprey" path="device/motorola/osprey" remote="github" revision="lineage-15.1" />
<project name="moto8916/android_device_motorola_msm8916-common" path="device/motorola/msm8916-common" remote="github" revision="lineage-15.1" />
<project name="moto8916/android_kernel_motorola_msm8916" path="kernel/motorola/msm8916" remote="github" revision="lineage-15.1" />
<project name="moto8916/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-15.1" />
<!-- Linaro 7.3 kernel toolchain -->
<project name="dev-harsh1998/GCC_BUILDS" path="prebuilts/gcc/linux-x86/arm/arm-eabi-7.3" remote="github" revision="master" />
<!-- Boringssl -->
<project name="LineageOS/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_external_bson" path="external/bson" remote="github" revision="lineage-15.1" />
</manifest>
To get the custom /e/ apps in your build you have to edit the portion of vendor/cm/config/common.mk that talks about "Custom CM Packages". Go to /prebuilts/prebuiltapks for a list of folders' names you can add to this list. Note that not everything will add properly, and adding some things may mess up your ROM, so experiment at your own risk
Where's My Download Link?
--MY GOOGLE DRIVE BUILD FOLDER
--If you want MicroG as well as a replacement for GApps, our resident MicroG expert @martianmarvel said he followed this thread here and got MicroG working on his /e/ harpia just fine
Can I See Some Screenshots? (It's an older Nougat build because I'm too lazy to get new screenies but it's more or less the same theme)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Who Should You Give a Special Thanks To?
--The /e/ team (including but not limited to Gael Duval)
--All the guys here on the harpia forums for their hard work in building the trees for this thing
--@bcrichster for showing me how to get the /e/ apps to build with the ROM on this thing so I don't have to steal from AOSP anymore
--The moto8916 github repo (and all its contributors) for the trees
--All the dudes on the english Moto G3 testing group for letting me know that the ROM is working fine, I don't have a G3 myself but they tested it all for me

Very fast and beautiful ROM... but spoofing signature missing and Micro g gms don't works!!!! Fix that please.

Gnzalobnites said:
Very fast and beautiful ROM... but spoofing signature missing and Micro g gms don't works!!!! Fix that please.
Click to expand...
Click to collapse
I don't know how to spoof a signature for a ROM, and I've never used MicroG GMS so I'm not sure how to fix that either. I'll look into it though, thanks for the feedback

Gnzalobnites said:
Very fast and beautiful ROM... but spoofing signature missing and Micro g gms don't works!!!! Fix that please.
Click to expand...
Click to collapse
You could try NanoDroid which has a system patcher to activate signature spoofing.
Sent from my Nvidia Shield Tablet using XDA Labs

jemail said:
You could try NanoDroid which has a system patcher to activate signature spoofing.
Click to expand...
Click to collapse
Didn't know this was a thing, thanks for making me aware. If this actually works out on this ROM, please let me know so I can cite it up in the OP for anyone else that wants to do it too

jasonmerc said:
Didn't know this was a thing, thanks for making me aware. If this actually works out on this ROM, please let me know so I can cite it up in the OP for anyone else that wants to do it too
Click to expand...
Click to collapse
I don't use OREO or PIE ROMs, only NOUGAT on my osprey. O and P don't run so well on osprey in my experience. The newest shiny thing is not necessarily the best ?.
Maybe you or another user can test NanoDroid system patching on your ROM ?.
Sent from my Nvidia Shield Tablet using XDA Labs

jemail said:
I don't use OREO or PIE ROMs, only NOUGAT on my osprey. O and P don't run so well on osprey in my experience. The newest shiny thing is not necessarily the best ?.
Maybe you or another user can test NanoDroid system patching on your ROM .
Sent from my Nvidia Shield Tablet using XDA Labs
Click to expand...
Click to collapse
/e/ os nougat is here: https://gitlab.e.foundation/e/wiki/en/wikis/device/osprey/info

Gnzalobnites said:
/e/ os nougat is here: https://gitlab.e.foundation/e/wiki/en/wikis/device/osprey/info
Click to expand...
Click to collapse
Be cautious with that though, as nougat Lineage (which /e/ is based off of) is no longer being supported or maintained. That's why I moved onto building Oreo roms, so we can get things like security updates down the road

jemail said:
I don't use OREO or PIE ROMs, only NOUGAT on my osprey. O and P don't run so well on osprey in my experience. The newest shiny thing is not necessarily the best ?.
Maybe you or another user can test NanoDroid system patching on your ROM ?.
Click to expand...
Click to collapse
Try du pie i am sure your gonna love it and its maintained on weekly basis

lonkar said:
Try du pie i am sure your gonna love it and its maintained on weekly basis
Click to expand...
Click to collapse
There is no official build of Dirty Unicorns for osprey. Osprey is not on the supported device list.
What is your link for this DU build?
Sent from my Nvidia Shield Tablet using XDA Labs

jemail said:
There is no official build of Dirty Unicorns for osprey. Osprey is not on the supported device list.
What is your link for this DU build?
Click to expand...
Click to collapse
Check latest builds here
https://androidfilehost.com/?w=profile&uid=23610159112650996

New April build is up for eelo on osprey. Not sure what changed, besides maybe a security patch update (maybe)
EDIT: Sorry about that, apparently the upload of the April build failed before, gonna reupload it again soon and hopefully it stays this time

lonkar said:
Check latest builds here
https://androidfilehost.com/?w=profile&uid=23610159112650996
Click to expand...
Click to collapse
Thanks for the link.
I may give it a try, although these are unofficial builds.
Sent from my Nvidia Shield Tablet using XDA Labs

Unofficial CrDroid-OSv6 Android 10

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Always Have a full functional Backup. Just in case!
Rom Download Link :
https://androidfilehost.com/?fid=8889791610682935022
Lineage Recovery link :
https://androidfilehost.com/?fid=8889791610682935019
Recomended Bootloader/Modem : https://androidfilehost.com/?fid=3700668719832239236 (I9506XXUDRB1_I9506XXUDRA1)
GAPPS: DOWNLOAD GAPPS - Not updated yet for 10.0 -- use Beta from link below
Platform: ARM
Android: 10.0
OpenGapps : https://opengapps.org/
BITAGaaps : https://androidfilehost.com/?fid=4349826312261650978
Device Source:
Device : https://github.com/Khalvat-M/android_device_samsung_ks01ltexx
Kernel : https://github.com/Khalvat-M/kernel_samsung_msm8974
Vendor : https://github.com/Khalvat-M/vendor_samsung
** Make sure you're running a proper working Recovery (TWRP is recommended)
TWRP Link : https://dl.twrp.me/ks01lte/
1) Copy crDroid zip, GAPPS zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
8) Flash GAPPS
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk v20.1 (whatever is most recent, Android 10 is now supported)
ROM Asking for Decryption key on boot:
This isn't a ROM issue, but an issue with your device. Kindly boot into TWRP and go to wipe - choose FORMAT - TYPE - YES
***This WILL wipe your INTERNAL storage. Backup before performing the format.
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
1. You tell me
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed
- have modified system files
Thanks to:
- fagyi - Can't stress enough how much you do. Thank you so much for everything!!!
- Google
- LineageOS
- SlimRoms
- AOSPA
- AOSIP
- AICP
- OmniRom
- NamelessROM
- Many others... (if you've been left out just send a PM )
XDAevDB Information
[ROM] [10.0] crDroidAndroid v6.0 [UNOFFICIAL], ROM for the S4 i9506( ks01lte)
Contributors
khalvat
Source Code: https://github.com/crdroidandroid
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Stable
Created 2019-12-10
Last Updated 2020-09-11

mod edit: translated
Long live the S4. Thanks for the input
Sent from my POCO F1 mediante Tapatalk
Larga vida al S4. Gracias por el aporte
Enviado desde mi POCO F1 mediante Tapatalk

Which bootloader and Modem is it built for?

DiamondJohn said:
Which bootloader and Modem is it built for?
Click to expand...
Click to collapse
Added in post

jegogo99 said:
mod edit: translated
Long live the S4. Thanks for the input
Sent from my POCO F1 mediante Tapatalk
Larga vida al S4. Gracias por el aporte
Enviado desde mi POCO F1 mediante Tapatalk
Click to expand...
Click to collapse
Hey there please remember to post in english! I translated it for you!

khalvat said:
Guys I will not update Havoc until its problams are resolved. Our new android 10 CrDroid is available and its stable working android 10 features well:good:
Click to expand...
Click to collapse
FYI: I cannot get Magisk 20.1 installed on crDroid. however, the playstore does download and install apps.
crDroid home launcher crashes every time(see attached for logcat), pixel launcher works.
I also didn't get a GPS Fix. Admittedly indoors, but my current Havoc-OS Oreo did right next to it.

DiamondJohn said:
FYI: I cannot get Magisk 20.1 installed on crDroid. however, the playstore does download and install apps.
crDroid home launcher crashes every time(see attached for logcat), pixel launcher works.
I also didn't get a GPS Fix. Admittedly indoors, but my current Havoc-OS Oreo did right next to it.
Click to expand...
Click to collapse
All good here. No any crash
1 Flash Rom without gapps and boot to rom
2 After working for a while reboot and flash latest beta gapps
3 magisk for root will fix soon in next builds

New build 2019-12-16 is Available
Device changelog:
Fixed some minor bugs
Added samsung Doze

khalvat said:
All good here. No any crash
1 Flash Rom without gapps and boot to rom
2 After working for a while reboot and flash latest beta gapps
3 magisk for root will fix soon in next builds
Click to expand...
Click to collapse
khalvat said:
New build 2019-12-16 is Available
Device changelog:
Fixed some minor bugs
Added samsung Doze
Click to expand...
Click to collapse
I just dirty flashed the latest build over the previous build. It tried to re-instate Magisk, but failed.
Would a clean flash enable Magisk?

DiamondJohn said:
I just dirty flashed the latest build over the previous build. It tried to re-instate Magisk, but failed.
Would a clean flash enable Magisk?
Click to expand...
Click to collapse
Sorry Magisk issue still not fixed.

When I launch the music player, it seems, that the sound is skewed. The some is when I use the "Duolingo". In the previous version is all right.

kiprio said:
When I launch the music player, it seems, that the sound is skewed. The some is when I use the "Duolingo". In the previous version is all right.
Click to expand...
Click to collapse
Yeah. I know.its was my mistake in latest build. Fixed audio bug now so wait for new build

khalvat said:
Yeah. I know.its was my mistake in latest build. Fixed audio bug now so wait for new build
Click to expand...
Click to collapse
I have successfully built the ROM from your source:good:, but I have not test-flashed it to see if it works.:fingers-crossed:
The changes I had to make to get it to build (from memory)
Code:
echo "# dummy" > hardware/samsung/AdvancedDisplay/Android.mk;
echo "# dummy" > device/samsung/qcom-common/doze/Android.mk;
## (geany [B]hardware/interfaces/audio/common/all-versions/default/service/Android.mk[/B])
## [B]remove line 56[/B]
## [B][email protected] \[/B]
Is that related to above issue?
I personally do not use bluetooth audio (so NO issue for me personally), but does the above mean there is an issue with bluetooth audio? or do you use another fix not in github?
So, the takeaway is the source can be built pretty easily :good:
Can anyone check bluetooth audio?
===================================
edit: the actual error
Code:
hardware/interfaces/audio/common/all-versions/default/service/Android.mk: error: "[email protected] (EXECUTABLES android-arm) missing [email protected] (SHARED_LIBRARIES android-arm)"

DiamondJohn said:
I have successfully built the ROM from your source:good:, but I have not test-flashed it to see if it works.:fingers-crossed:
The changes I had to make to get it to build (from memory)
Code:
echo "# dummy" > hardware/samsung/AdvancedDisplay/Android.mk;
echo "# dummy" > device/samsung/qcom-common/doze/Android.mk;
## (geany [B]hardware/interfaces/audio/common/all-versions/default/service/Android.mk[/B])
## [B]remove line 56[/B]
## [B][email protected] \[/B]
Is that related to above issue?
I personally do not use bluetooth audio (so NO issue for me personally), but does the above mean there is an issue with bluetooth audio? or do you use another fix not in github?
So, the takeaway is the source can be built pretty easily :good:
Can anyone check bluetooth audio?
===================================
edit: the actual error
Code:
hardware/interfaces/audio/common/all-versions/default/service/Android.mk: error: "[email protected] (EXECUTABLES android-arm) missing [email protected] (SHARED_LIBRARIES android-arm)"
Click to expand...
Click to collapse
Nice:good:. If u can start pixelexprience build and share in our XDA page.

khalvat said:
Nice:good:. If u can start pixelexprience build and share in our XDA page.
Click to expand...
Click to collapse
Two problems there.
1. I build for my own devices/uses and share on XDA if there is no-one else building it, or has provided a recent build.
2. I like the most eye candy I can get , and Pixel Experience is targeted for an AOSP experience :cyclops:. ie not for me.

I can not get the GPS fix. The phone sees many satellites, but does not fix the position. How can I solve this?
PS. GOOD ROM. The battery lasts a long time!
replaced by I9506XXSDPL2_I9506XXUDOJ2_bootmodem GPS fix- OK!!!

A rooted crDroid!
khalvat said:
Sorry Magisk issue still not fixed.
Click to expand...
Click to collapse
FYI I just did a build using @kyasu kernel, and the small changes I noted above, and it built without a hitch, and Magisk flashed AND is working. So I now have a rooted crDroid :highfive:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-17.0" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-17.0" />
<project name="Khalvat-M/android_device_samsung_ks01ltexx" path="device/samsung/ks01ltexx" remote="github" revision="10.0" />
<project name="Khalvat-M/vendor_samsung" path="vendor/samsung" remote="github" revision="10.0" />
<project name="Khalvat-M/kernel_samsung_msm8974" path="kernel/khalavat_samsung/msm8974" remote="github" revision="10.0" />
<project name="kyasu/android_kernel_samsung_msm8974" path="kernel/samsung/msm8974" remote="github" revision="lineage-17.0-test" />
</manifest>
Not being rooted meant not being able to actually install/use my most commonly used apps. So this will be good until you get your kernel sorted:good:
oooo.... it really did not like the install of the latest viper, which uses Magisk.

DiamondJohn said:
FYI I just did a build using @kyasu kernel, and the small changes I noted above, and it built without a hitch, and Magisk flashed AND is working. So I now have a rooted crDroid :highfive:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-17.0" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-17.0" />
<project name="Khalvat-M/android_device_samsung_ks01ltexx" path="device/samsung/ks01ltexx" remote="github" revision="10.0" />
<project name="Khalvat-M/vendor_samsung" path="vendor/samsung" remote="github" revision="10.0" />
<project name="Khalvat-M/kernel_samsung_msm8974" path="kernel/khalavat_samsung/msm8974" remote="github" revision="10.0" />
<project name="kyasu/android_kernel_samsung_msm8974" path="kernel/samsung/msm8974" remote="github" revision="lineage-17.0-test" />
</manifest>
Not being rooted meant not being able to actually install/use my most commonly used apps. So this will be good until you get your kernel sorted:good:
oooo.... it really did not like the install of the latest viper, which uses Magisk.
Click to expand...
Click to collapse
Yeah it was from kernel but im working on other devices so have not time for change kernel source for now.
Also add devicesettings in roomservices from linneageos

New build 2020-01-01 is Available
Fixed bugs
I had not time to fix root problam so i will fix in next build
Happy new year???️??Merry christmas

khalvat said:
New build 2020-01-01 is Available
Fixed bugs
I had not time to fix root problam so i will fix in next build
Happy new year?️Merry christmas
Click to expand...
Click to collapse
Great News Sir
HNY & MC , Wishes You All The Success in Your Pro And Perso life
Regards .