/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
Related
{
"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"
}
Introduction
I've moved from my OPO to the Z1 and was simply disturbed with the lack of development this device receives, including how Cyanogen Inc & CM treats it like the ugly duckling in the family.
This might not have been received as such by the public, but should you ever give the CM code (device tree, kernel, etc) a look you will know what I mean.
And even if you don't, you will "feel" it while using their software too (half working or missing features, bugs in the kernel, etc).
To right this wrong I've set myself a simple goal, produce a proper CM13 device tree, Marshmallow proprietary repository and finally, clean up the device tree mess that Cyanogen Inc & CM produced for the Z1.
I also throw in a kernel fix or two every once in a while.
As a side-product of this, you guys will (obviously) reap the benefits of this endeavour of mine, namely a properly working CM13 build for the Z1 as well as several other (maybe even more functional) ROMs that will have the opportunity to base their work on mine.
Working Stuff
Dual-SIM
Phone Calls
Phone Call Recording (2-way and unlocked)
Text Messaging
Mobile Data
Sensors
WLAN
EAP-SIM
Bluetooth
Camera (please use Micro OpenGapps, other Gapps sometimes break the camera)
4K Video Recording
1080p Front-Facing-Camera Recording
60FPS Slow-Motion Recording (720p & 1080p only)
GPS
USB / USB-OTG
Doze mode
Double-Tap to Wake
Fingerprint Reader
Capacitive Home Button (Keycodes: 249 = Right Slide, 254 = Left Slide, 158 = Tap, mapped in fpc1020tp.kl)
Tethering
Fixed Headphone Button Voltage Tables (this fixes headphone buttons, like that of the Xiaomi Pistons)
Most (if not all) OS-related stuff
Credits
Steve Kondik (cyanogen) for the bacon device tree & proprietaries (I've used some of these as bring-up reference)
Team CyanogenMod for... well, CyanogenMod
TheCrazyLex for general bring-up advice
JoaoPaulo for his CAF 1.1.3 / Chroma 6.0 kernel and TWRP port
Myself (Coldbird) for the actual bring-up and general bugfixing
Donations
Should you wish to support this (or other projects of mine), please consider donating a few bucks to me via PayPal.
Alternatively, if you like the general idea of bringing proper Android support to badly supported devices (mostly China-Phones), please consider becoming a patron to my "Bring CyanogenMod to China-Phones" movement over at Patreon by pledging a few dollars every month to move me closer to the goal of doing this for a living instead of only squeezing in a few hours every week next to my regular work.
Every support, no matter how tiny, is appreciated.
Donators
Here's a list of all the kind people that have donated to this project in one way or another.
I thank these people for the trust and support they have shown to this project and honor them by listing each and every one of them here.
Dominik Hopf 20€
Jan Hildebrandt 10€
Henk-Jan Zilverberg 10€
Andrew Carmicheal 10£
N J Grayson 10€
MKKLR21 10€
Paolo Hamam 10€
Andreas Körner 10€
Joern Feldhausen 10€
Sergio Avram 10€
Mauro Longano 10€
Jonathan 10€
Javi 10€
tndb 10$
Max Plotnikov 10$
Max 10$
EggZenBeanz 5£
Kai Hellmeier 5€
Moritz Fey 5€
David Mesegar 5€
Sergei Razladin 5€
Manuel Vögel 5€
Wido van der Gaag 5€
fr4nkr0c 5€
Анатолий Чистяков 5$
Kamil Respondek 2€
Downloads
Pre-Requisites
JoaoPaulo's TWRP Recovery (required for flashing)
Marshmallow Firmware, Sensors & Bootloader (required to fix sensor and boot issues with some devices)
Builds
CyanogenMod 13 Builds
Changelogs
Local Manifest (for developers)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="MrColdbird/proprietary_vendor_zuk" path="vendor/zuk" remote="github" revision="cm-13.0" />
<project name="MrColdbird/android_device_zuk_ham" path="device/zuk/ham" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0" />
<project name="ChromaKernel/cKernel" path="kernel/cyanogen/msm8974" remote="github" revision="cm-13.0" />
</manifest>
XDA:DevDB Information
[ROM][6.0.1] Unofficial CyanogenMod 13.0 Nightlies (4K, USB-OTG, OTA, etc), ROM for the Lenovo Zuk Z1
Contributors
MrColdbird, JoaoPaulo
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-12-24
Last Updated 2016-03-02
Wow! Nice work mate
Where to download?
hfutxqd said:
Where to download?
Click to expand...
Click to collapse
Are you read the op?
"Downloads aren't up yet due to the rather low quality of the build (at the moment)."
Why make you Thread whene you dont have a working build? Please read the xda rules and delete this thread for now.
Gesendet von meinem Z1 mit Tapatalk
hfutxqd said:
Where to download?
Click to expand...
Click to collapse
I will post a link once I deem the release stable enough for public testing (after WiFi and RIL is working).
I will work more on it tomorrow and, for those that feel adventurous, I will also post the local manifest required to build it.
MrColdbird said:
Introduction
I've moved from my OPO to the Z1 and was simply disturbed with the lack of development this device receives, including how Cyanogen Inc & CM treats it like the ugly duckling in the family.
This might not have been received as such by the public, but should you ever give the CM code (device tree, kernel, etc) a look you will know what I mean.
To right this wrong I've set myself a simple goal, produce a proper CM13 device tree, Marshmallow proprietary repository and finally, clean up the device tree mess that Cyanogen Inc & CM produced for the Z1.
As a side-product of this, you guys will (obviously) reap the benefits of this endeavour of mine, namely a working CM13 build for the Z1.
Downloads aren't up yet due to the rather low quality of the build (at the moment), however, once I've fixed both WLAN & RIL, I will provide unofficial nightlies via my own little building bot so that you guys won't be missing out on any CM13 updates from now on.
Screenshots
Broken Stuff (at the moment)
RIL / Data
GPS
Most likely a lot more...
Changelog
25.12.2015
Added prebuilt kernel + modules
Fixed WLAN
Donations
Should you wish to donate / buy me a beer / raise my working morale, feel free to send a few bucks via PayPal to [email protected].
Who knows, maybe my next grocery shopping trip can be paid by donation money? That would be marvelous.
XDA:DevDB Information
UNOFFICIAL CM13, ROM for the Lenovo Zuk Z1
Contributors
MrColdbird
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Alpha
Created 2015-12-24
Last Updated 2015-12-24
Click to expand...
Click to collapse
First of all thank you very much for endorsing this great project. I also wonder why such a good device with CM out of the box hasn't received better support from the community, at the end of the day OnePlus was nobody when the One was released and despite it was very hard to get it, it did see a good support from the beginning.
Second and foremost, as you probably have the skills, why don't you start porting AICP, Carbon, BlissPop or your favourite ROM to the Z1?
Thank you again!!
Because I think a working CM13 tree will benefit people more than yet another 5.1 ROM.
MrColdbird said:
Because I think a working CM13 tree will benefit people more than yet another 5.1 ROM.
Click to expand...
Click to collapse
I understand what you mean but official CM13 support will come, while ROMs are not available yet despite official 12.1 is out...
I think most ROM devs only develop official ROMs if they get the device, at least, carbon ROM when asked for support for my old mi2.
Others offer support but without owning the device, so you can't expect best support.
The thing is lots of devices who are not supported by CM have got 6.0 before supported devices and that make me feel like second division costumer.
Enviado desde mi Z1 mediante Tapatalk
Fixed SIM-Card detection a minute ago, along with phone calls (those two kinda go hand-in-hand).
Next up on the todo list: Mobile Data.
Wish me luck. All changes to the device tree for self-builders can be found on my github "MrColdbird".
Hello, is thé CAMERA2 API implémentée un CM13 ?
frk22 said:
Hello, is thé CAMERA2 API implémentée un CM13 ?
Click to expand...
Click to collapse
The HAL is there for sure but I got no idea whether all the functions work yet.
In general I'm more concerned about getting mobile data working right now.
Great start
Could you push the source code to Github.com?
hfutxqd said:
Could you push the source code to Github.com?
Click to expand...
Click to collapse
It is on github.
Amazing. Thank u very much for this amazing project. Finally we got someone working in cm13! I hope Cyanogenmod and CyanogenOS start working soon...
Enviado desde mi Z1 mediante Tapatalk
PD. If u need any betatesters just ask for it, we will be happy ti help u.
It's good to see some developer has interested to do some marshmallow ROM with ZUK Z1. Thank you very much @MrColdbird really appreciate your hard work.
MrColdbird said:
Introduction
I've moved from my OPO to the Z1 and was simply disturbed with the lack of development this device receives, including how Cyanogen Inc & CM treats it like the ugly duckling in the family.
This might not have been received as such by the public, but should you ever give the CM code (device tree, kernel, etc) a look you will know what I mean.
To right this wrong I've set myself a simple goal, produce a proper CM13 device tree, Marshmallow proprietary repository and finally, clean up the device tree mess that Cyanogen Inc & CM produced for the Z1.
As a side-product of this, you guys will (obviously) reap the benefits of this endeavour of mine, namely a working CM13 build for the Z1.
Screenshots
Broken Stuff (at the moment)
Mobile Data
GPS
Most likely a lot more...
Changelog
26.12.2015
Fixed SIM Card Detection
Fixed Phone Calls
25.12.2015
Added prebuilt kernel + modules
Fixed WLAN
Fixed RIL
Donations
Should you wish to donate / buy me a beer / raise my working morale, feel free to send a few bucks via PayPal to [email protected].
Who knows, maybe my next grocery shopping trip can be paid by donation money? That would be marvelous
Thanks MrColdbird
Click to expand...
Click to collapse
Thank you for your effort!
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), 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.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-F
Bluetooth
Camera ( Videos And Photos )
Video Playback
Audio ( Record and Playback )
IR
Double Tap Wake
Sensors
Hardware acceleration and OpenGL rendering
Flash
SD cards
Touchscreen/multi-touch
LED
GPS
What's not working :
Use VOL UP + VOL DOWN + POWER button to enter recovery mode
Enforcing SELinux (Use prebuilt kernel U.u)
VolTe (NO ETAS)
You tell me!
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash the latest build and GApps
Reboot
Downloads :
Last Build: https://carlosarriagacm.github.io/
Google Apps: http://opengapps.org/
Credits :
Ze00 - https://github.com/ze00 (for the device and vendor)
noiver - https://github.com/noiver (for the device and vendor)
LineageOS Team
Klozz
Me
My manifest used:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- device tree -->
<project path="device/xiaomi/rolex" name="Redmi4A/android_device_xiaomi_rolex" remote="github" revision="cm-13.0" />
<project path="device/qcom/common" name="LineageOS/android_device_qcom_common" remote="github" revision="cm-13.0" />
<!-- vendor -->
<project path="vendor/xiaomi/rolex" name="Redmi4A/android_vendor_xiaomi_rolex" remote="github" revision="cm-13.0" />
</manifest>
Click to expand...
Click to collapse
SCREENSHOTS
Great, thanks
Move your thread to https://forum.xda-developers.com/t/xiaomi-redmi-4a
Great ROM. Thank you very much.
May I know why lineage-13.0-20170725-UNOFFICIAL-rolex was removed from androidfilehost? Any issues in that rom released on 25th?
New build is up!
Changelog:
* Fixed Double tap wake
* Fixed IR
* Fixed GPS
* Set Correct partitions
* Fixe's all bugs
Not working¡
* Video Playback (Only videos recorded with the device)
* VolTE (not supported in my country sorry)
DOWNLOAD IN THE OP
Wow, thank you very much.
Yeay!
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
Good work!
Hey Carlos! Tried the rom.Absolutely butter.Sorry if I'm being a big itch but is there any chance you could somehow make a VoLTE patch or something?Reply appreciated.
Sorry again for being an itch
It's just that can't use the phone without VoLTE
eternal1404 said:
Hey Carlos! Tried the rom.Absolutely butter.Sorry if I'm being a big itch but is there any chance you could somehow make a VoLTE patch or something?Reply appreciated.
Sorry again for being an itch
It's just that can't use the phone without VoLTE
Click to expand...
Click to collapse
For VoLTE we need the kernel source.
BryanByteZ said:
For VoLTE we need the kernel source.
Click to expand...
Click to collapse
Hi Bryan ✌ i love you kernel for falcon, please send pm in telegram: @carlosarriagacm
Carlos Arriaga said:
Hi Bryan ✌ i love you kernel for falcon, please send pm in telegram: @carlosarriagacm
Click to expand...
Click to collapse
Hey man everything fine? I hope so. About telegram I am without (carrier problems) but you can pm here, I try to login at least once a day. BTW really good work in this ROM.
A HUUUGE THANKS for you to fix those GPS issue, and also to make the native dt2w working!
Also, video playback looks fine on mine, played a few downloaded videos and nothing weird happened (those are .mp4)
Expecting all
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
https://chat.whatsapp.com/GpIMzaI7w6Y7wVHxQczcGF
Come join
Anyone else facing signal issues? On MiUi I used to get 4 bars consistently.... but with this ROM... hardly getting 2 bars? Any issue?
[FIX] Low Mic volume/gain issue
I'm going to share a fix for low mic volume/gain issue. The Redmi 4A is suffering from bad mic issues, not during a phone call, but in other apps e.g. voice recorder (or videos recorded with de device, if the not working feature will be fixed in the future). It's not a hardware issue but software issue:
Root is required.
Navigate to the root directory of the phone:
Root/system/etc/
Then look for a file named "audio_platform_info.xml" with text editor of your choice .
Now go to the bottom of the file you will see </acdb_ids> , you need to add the below line before/above that </acdb_ids>
Click and add this line:
<device name ="SND_DEVICE_IN_VOICE_DMIC" acdb_id = "100"/>
Now just save the file.
Reboot the device now.
Source: en.miui.com/thread-628652-1-1.html
New build is up guys!
CHANGELOG:
Sync source Lineage
All bugs fixe´s
Download In the OP
Carlos Arriaga said:
New build is up guys!
CHANGELOG:
Sync source Lineage
All bugs fixe´s
Download In the OP
Click to expand...
Click to collapse
gr8 job. btw why dont we have seperate xda forum?
tschall said:
Source: en.miui.com/thread-628652-1-1.html
Click to expand...
Click to collapse
Thanks, ill try this. :good:
Carlos Arriaga said:
New build is up guys!
Download In the OP
Click to expand...
Click to collapse
Incredible update. :good:
I can't express my gratefulness with words.
I don't know what magic you guys are doing but this ROM runs more smoothly than the official ROM :laugh: and I now understand why they are not releasing the kernel for this phone because everyone will switch to LineageOS.
defy_owner said:
gr8 job. btw why dont we have seperate xda forum?
Click to expand...
Click to collapse
We do have a separate forum for Redmi 4A.
New fix: Solving the problem with the quality of sound recording in video/voice rec.
-root required
1. open file:
/system/etc/audio_platform_info.xml
Under <acdb_ids> add this:
<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="1"/>
<device name="SND_DEVICE_IN_HANDSET_STEREO_DMIC" acdb_id="1"/>
2. open file:
/system/etc/mixer_paths_qrd_sku2.xml
search for:
<path name="handset-mic">
<path name="adc1" />
There are two lines with DEC1 / DEC2 - delete them and replace it with:
<ctl name="DEC1 Volume" value="96" />
<ctl name="DEC2 Volume" value="96" />
3. Restart phone
Source: 4pda.ru/forum/index.php?showtopic=774539&st=1180#entry56251135
message # 1200
(via google translator)
{
"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"
}
About Lineage OS:
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is 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 the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
Warning:
Don't flash any other Bootstack since the newest N Bootstack is already included into the ROM. This ROM may not work on devices that have not installed the N Bootloader and Modem.
Bugs:
Fingerprint reader (U-Touch works tho)
Video recording is bugging but half broken working
SELinux=permissive
Maybe more?!
Instructions:
1. Download the zip
2. Bootloader needs to be unlocked
3. Perform a backup of your current ROM (optionally)
4. Wipe system,data and cache (optionally) [Needed if coming from another rom; always good to avoid bugs]
5. Install LineageOS 15
6. Install GApps (optionally) [Recommended -> Open GApps (arm) (8.0)]
7. Reboot
What is CAF?
codeaurora.org
Code Aurora Forum, a Linux Foundation Collaborative Project, is a consortium of companies with projects serving the mobile wireless industry. The projects provide the tested code needed to bring innovative, performance optimized, open source based products to market and also serves as a staging area for code that is submitted to upstream projects such as the kernel and Android. Code Aurora Forum welcomes the participation of projects for multiple architectures. QuIC, as one of the members of Code Aurora Forum, provides support for Qualcomm hardware via the code it contributes to Code Aurora Forum. Code Aurora Forum also mirrors key upstream projects for use by the community.
Sources, Changes, & Wiki:
Source | Changes | Zuk Z1 Wiki | Lineage OS
Download:
Lineage Unofficial Builds
local_manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="OrdenKrieger/android_device_zuk_ham" path="device/zuk/ham" remote="github" />
<project name="OrdenKrieger/proprietary_vendor_zuk" path="vendor/zuk" remote="github" />
<project name="OrdenKrieger/android_kernel_cyanogen_msm8974" path="kernel/cyanogen/msm8974" remote="github" />
</manifest>
source repopick-ham.md:
Code:
### # Load envsetup.sh
source ./build/envsetup.sh;
### # Recovery updates
repopick 186687;
repopick 187332 187374;
repopick 187155;
### # Apps updates
repopick 188389 188518-188526;
repopick 188527-188529;
### # Legacy ADB
repopick -t oreo-adb-usb-legacy;
### # System core updates
repopick 187146;
### # UI updates
repopick 193830;
# Topic: LineageOS Lights
repopick -Q 'status:open+topic:oreo-lights';
### # Topic: LineageOS Features
repopick 191921 187592;
repopick -Q 'status:open+topic:oreo-powermenu';
repopick 193249 193258 191905;
repopick 193025 191736;
repopick -Q 'status:open+topic:oreo-tiles';
repopick 193544 193770;
### # Qcom flags
repopick 192352;
### # Keymaster
repopick 186044-186049;
XDA:DevDB Information
Unofficial LineageOS 15.0, ROM for the Lenovo Zuk Z1
Contributors
OrdenKrieger
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2017-11-20
Last Updated 2017-11-19
Here we go. This took me some days. Feel free to help me out by donating to my >PayPal< to keep this work up. Aynways hope everyone enjoys this ROM. :good:
Reserved
You were the first to bring nougat for ham and you again proved it that u are the first to bring Oreo for ham. Always the best and Thanks mate for the work everything working fine but there are some bugs
1.FP isn't working in this build even though it is showing in my settings when I try to set FP it doesn't do anything it just shows
Note :My FP is working .
2. Some settings icons are missing in settings
3. Minor bugs like some google apps like google plus isn't working though it is personal preference of using apps
Hope these will be fixed.
Thanks a lot for bringing new life to ham.
Great work bro. Finally Ham got Oreo
Great bro, again you made it , thanks
Amazing work bro. Now I can build Resurrection Remix too. All credit goes to you. Hats off!
Thanks man
Sent from my Pixel XL using XDA Labs
thank u so much man..atleast now our device can breathe for one more year...will test it and say what are the bugs associated
Thank u soo much...amazing work
I was previously on crdroid 3.8, flashed without gapps.Just tested in multirom :-
Super fluid, feels like nexus and Very fast to launch system apps and stable also.
All sort of wifi/hotspot/data works , bt too.
Camera can take pics and videos, but videos are very laggy when played.
Footej camera works alright for everything
FP doesn't work here, but utouch works, though it's a lineage.
Thanks dev.
great work again, thanks man for making it possible us to use this phone for one more year or even further
Thanks man.... You're amazing
Sharma_Ji said:
Just tested in multirom :-
Very fast to launch system apps and stable also.
All sort of wifi/hotspot/data works , bt too.
Camera can take pics and videos, but videos are very laggy when played.
FP doesn't work here, but utouch works, though it's a lineage.
Thanks dev.
Click to expand...
Click to collapse
Is it too early to ask battery life and sot ...and any major bugs ...what about connectivity and call quality?
---------- Post added at 09:00 AM ---------- Previous post was at 08:58 AM ----------
ankurpandeyvns said:
Amazing work bro. Now I can build Resurrection Remix too. All credit goes to you. Hats off!
Click to expand...
Click to collapse
Waiting for it..
Fingers crossed
Sharma_Ji said:
Just tested in multirom :-
Very fast to launch system apps and stable also.
All sort of wifi/hotspot/data works , bt too.
Camera can take pics and videos, but videos are very laggy when played.
FP doesn't work here, but utouch works, though it's a lineage.
Thanks dev.
Click to expand...
Click to collapse
can u tell me how to flash this rom.. am not able to boot it..it gets stuck at set up..
Sarthak jain01 said:
Is it too early to ask battery life and sot ...and any major bugs ...what about connectivity and call quality
Click to expand...
Click to collapse
I called only customer care and it worked fine.:laugh:
I will test more when i get free from lab, engineering bro
ankurpandeyvns said:
Amazing work bro. Now I can build Resurrection Remix too. All credit goes to you. Hats off!
Click to expand...
Click to collapse
But u don't own a zuk right ?
xdaakhil said:
can u tell me how to flash this rom.. am not able to boot it..it gets stuck at set up..
Click to expand...
Click to collapse
I tried in multirom, the ROM's always skip setup when you install them in multirom, so don't know
sriram prakhya said:
But u don't own a zuk right
Click to expand...
Click to collapse
But now the device tree is available. ??
{
"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 .
{
"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"
}
Code:
#include <std/disclaimer.h>
/*
* I'm 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 the products you find here before flashing it!
* YOU are choosing to make these modifications, do not point your finger at me for messing up your device.
* Your warranty will be void if you tamper with any part of your device / software.
*/
LineageOS (LOS) is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project (AOSP) with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (GApps). 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 Gerrit Code Review. If you want to report an issue please do so on GitLab and include a logcat if possible.
Status
This Project is EOL, please use official instead.
Known issues
USB Tethering / Android Auto not working
OTA Update not working (might change in the future)
Instructions
TBD
Migration instructions
If you are coming from Official LineageOS 16.0 you need to clean flash (wipe everything incl. data) or migrate the signature keys before flashing:
Backup your data (I recommend Titanium Backup)
Boot Recovery
Nandroid backup
Flash migrate-official-to-beneter.zip (s. Google Drive)
Flash lineage-16.0-*-UNOFFICIAL-beneter-tissot.zip (s. Google Drive)
If you are coming from anything else please do a clean flash (wipe everything incl. data).
Downloads
Unofficial Build: Google Drive, There will always be checksums and detached signatures signed by my key "38E50B61" (s. below).
I encourage the community to host mirrors with the same filename. If you download from them, be sure to verify the PGP signature.
Recovery: TWRP
Google Apps: Open GApps (I am not using any GApps but microG by NanoDroid, if you would like to use GApps please flash the nano image for arm64 and install additional Apps from PlayStore)
Root: Magisk
Signature verification
TBD
Code:
gpg: Good signature from "Stefan Benter <[email protected]>"
Primary key fingerprint: [B]E545 73C1 5218 8816 E83C 3A0F DCAC EF53 38E5 0B61[/B]
Subkey fingerprint: 1DE2 E0FE 948E EAAB B446 D398 A4D6 CD34 239A B40D
Sources
LineageOS: https://github.com/LineageOS/android
Common device tree: https://github.com/LineageOS/android_device_xiaomi_msm8953-common
Device tree: https://github.com/LineageOS/android_device_xiaomi_tissot
Kernel: https://github.com/LineageOS/android_kernel_xiaomi_msm8953
Proprietary Vendor: https://gitlab.com/the-muppets/proprietary_vendor_xiaomi/-/tree/lineage-16.0
Build Guide
Code:
cat android/lineage/.repo/local_manifests/roomservice.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_xiaomi_tissot" path="device/xiaomi/tissot" remote="github" />
<project name="LineageOS/android_device_xiaomi_msm8953-common" path="device/xiaomi/msm8953-common" remote="github" />
<project name="LineageOS/android_kernel_xiaomi_msm8953" path="kernel/xiaomi/msm8953" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<remote name="gitlab" fetch="https://gitlab.com" />
<project name="The-Muppets/proprietary_vendor_xiaomi" path="vendor/xiaomi" remote="gitlab"/>
</manifest>
Credit
Special thanks to flex1911 and abhishek987.
Thanks to the whole LineageOS Team, its contributors and all the testers.
Donations
Please consider donating to the LineageOS Project.
Please consider donating some blood, registering as a bone marrow donor and becoming an organ donor.
XDA:DevDB Information
[ROM][9.x][UNOFFICIAL] LineageOS 16.0 Xiaomi Mi A1 [tissot][EOL], ROM for the Xiaomi Mi A1
Contributors
Beneter, flex1911, abhishek987, LineageOS Team, its contributors and testers
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Abandoned
Stable Release Date: 2020-08-20
Created 2020-06-14
Last Updated 2020-10-01
Downloads
This Project is EOL, please use official instead.
Restore LineageOS official keys: migrate-beneter-to-official.zip | Checksum | Signature
Last version: lineage-16.0-20200820-UNOFFICIAL-beneter-tissot.zip | Checksum | Signature | Security Patchlevel: 2020-08-05
Migration script: migrate-official-to-beneter.zip | Checksum | Signature
Older Versions:
lineage-16.0-20200715-UNOFFICIAL-beneter-tissot.zip | Checksum | Signature | Security Patchlevel: 2020-07-05
lineage-16.0-20200613-UNOFFICIAL-beneter-tissot.zip | Checksum | Signature | Security Patchlevel: 2020-06-05
lineage-16.0-20200501-UNOFFICIAL-beneter-tissot.zip | Checksum | Signature | Security Patchlevel: 2020-04-05
Backlog
Add migration script to restore official keys
Improve build scripts and publish them
EOL and therefore no longer planned
Fix build issues (instead of using the workaround)
Fork tissot tree
Fix USB Tethering / Android Auto
Update firmware
Compare Proprietary Vendor files with original Xiaomi build
Improve documentation (flashing guides, signature verification), @everyone: you can help!
Webseed a torrent mirror
Create a restricted signature spoofing build for microG
Ask @abhinavagrd_1129 how I can help to make 17.1 go official
Become a part time official maintainer
In case this won't work, provide unofficial OTA updates
Update kernel
Great work. Why don't you submit it to official?? Even if you don't have time or dont want to bring it up to 17.1, at least the automatic builds of los16 would be up. The ROM was rock stable and the only bug was android auto broken. Pleae do consider this humble request.
Enviado do meu Mi A1 através do Tapatalk
taurelio said:
Why don't you submit it to official?
Click to expand...
Click to collapse
I was asking them what would be needed to be accepted as a maintainer, they told me to fix the USB tethering issue and port to 17.1. I am not saying, that I will never do so, but I do not want to promise anything as of now.
Nice, long live the code!!!
Sent from my Mi A1 using Tapatalk
I look forward to you fixing the USB Tethering.
Beneter said:
I was asking them what would be needed to be accepted as a maintainer, they told me to fix the USB tethering issue and port to 17.1. I am not saying, that I will never do so, but I do not want to promise anything as of now.
Click to expand...
Click to collapse
Take your time but we would love to see mi a1 on the official roster of lineage 17.1. The final decision is ours. Whatever you are going to give to the community we will appreciate.
Enviado do meu Mi A1 através do Tapatalk
@Beneter thanks for starting this once again.
Can official LineageOS su be used instead of Magisk?
Baile said:
Can official LineageOS su be used instead of Magisk?
Click to expand...
Click to collapse
Probably yes, but I did not try.
@Beneter You say you use nanodroid. Does that mean your ROM supports signature spoofing out of the box?
USB tethering
I looked at the difference between LineageOS for Tissot and Mido.
Mido has "TARGET_KERNEL_VERSION := 3.18" set in BoardConfig.mk but Tissot doesn't. Maybe the USB will work if "TARGET_KERNEL_VERSION := 4.9" is set in the same file for Tissot? I don't have good enough PC or Internet to try and build, but maybe that would be a solution?
Thanks for reviving this rom!
Just wondering, is the AudioFX problem going to be fixed? It stops processing the audio after several minutes of phone usage.
I use Viper4Android atm because AudioFX is sucks in several Pie roms, including LOS 16. It worked well in LOS 17.1 though.
thank God. thank u. great work
i was on last los16 official everything good but from last week google play services downloads official rom ota packages and consume my 1.5-2gb data and if i disable PlayServices data with AFWall i'm unable to use YouTube. i haven't understand why PlayServices download official ota on custom Roms this happens to me on AEX Rom many times if rom on latest patch then everything fine
you've done brilliant job.
one request please make a mirror like androidfilehost.com i'm unable to download it from GDrive everytime it stops after downloading 200-300mb and then failed and doesn't support resume
xander2m said:
@Beneter You say you use nanodroid. Does that mean your ROM supports signature spoofing out of the box?
Click to expand...
Click to collapse
No, this is 100 % vanilla LineageOS as of now. I am pretty satisfied by the NanoDroid Patcher.
I would be able to provide a second build with signature spoofing enabled (in restricted mode), but this would cause a small amount of additional effort.
@everyone: Small poll - If you are interested in an additional signature spoof build (only really needed for MicroG) press thanks on this post. I will probably implement it if we reach five people.
JakobSWE said:
I looked at the difference between LineageOS for Tissot and Mido.
Mido has "TARGET_KERNEL_VERSION := 3.18" set in BoardConfig.mk but Tissot doesn't. Maybe the USB will work if "TARGET_KERNEL_VERSION := 4.9" is set in the same file for Tissot?
Click to expand...
Click to collapse
Wow, thanks for your support! I will definitely look into this soon, but I have to be sure that there are no unintended side effects.
As I was never using USB Tethering nor Android Auto I am not sure how to test it
dellinn said:
Just wondering, is the AudioFX problem going to be fixed? It stops processing the audio after several minutes of phone usage.
Click to expand...
Click to collapse
Hmm... that sounds a lot like https://gitlab.com/LineageOS/issues/android/-/issues/1628. If you can please add your experience there as a comment and try to include a logcat. As of now I think this might be device independent. Because this seems to be fixed in 17.1 I will not look into it, sorry.
ranjodhricky said:
one request please make a mirror like androidfilehost.com i'm unable to download it from GDrive everytime it stops after downloading 200-300mb and then failed and doesn't support resume
Click to expand...
Click to collapse
Huh, that sounds really annoying.
I was looking for the best hosting provider before and a lot recommended GDrive and discouraged the usage of AFH. I do not really want to maintain a mirror by myself, except maybe I will start to webseed a torrent.
@everyone: As far as you do not change the files itself (including filename), please feel free to host a mirror and post it here.
In case you are downloading from a mirror you should definitely verify the signature.