LineageOS 17.x Unofficial for Galaxy A3 2017
{
"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 10 (Quack), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void. Or not. Depends.
* It's probably expired anyways :D
*
* 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.
*/
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 Gerrit Code Review.
What's working?
Audio
Calls
Wifi
Hotspot
Mobile data
GPS
Bluetooth
Fingerprint
Camera (both photos and video)
NFC
Sensors
Vibration
Others I have forgot
What isn't working?
Echo present in calls for the other side (no fix currently found)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (possible to fix, didn't have time to debug yet)
Stretched preview in camera, photos are fine (fix has more downsides than upsides)
Supported variants
Galaxy A3 (2017). Dual SIM is also supported.
All variants should be working but only A320FL is well tested since all developers have it.
How to install
Make sure you have latest bootloader and modem before installing this.
Make sure you are using the latest OrangeFox build. (the older ones will fail)
Make sure you have flashed the repartition script.
Download the Lineage build, optionally GApps and Magisk.
In OrangeFox format data. (Menu > Manage Partitions > Data > Format Data)
In OrangeFox wipe everything except SD and OTG.
Flash LineageOS.
Optional: Flash GApps (rightafter).
Optional: Flash Magisk.
Reboot.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
Downloads
• ROM
get.mcfy.fr
Google Drive
• Recovery
OrangeFox
• GApps
OpenGApps (arm64): OpenGApps
BiTGApps (arm64): AFH
• Root
Magisk: GitHub
Credits
Huge thanks to:
@Astrako for all the hours spent on the device tree/kernel/vendor/hardware and making this possible.
@McFy for help along the way and letting me use his server as a mirror.
LineageOS Team
Anybody that reported bugs or helped test various stuff, without every one of you Android 10 would never get so stable here
XDA:DevDB Information
[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble], ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
MartinYTCZ
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest modem + BL recommended
Version Information
Status: Beta
Created 2020-02-22
Last Updated 2020-08-26
Telegram group
Join here!
Go also thank @Astrako for his work on the DT, kernel, ports, recoveries and many more
Changelogs
- 20200221
Initial build
- 20200403
March security patches
Many optimisations and smaller fixes
Rootdir updated from A6 2018 Q, along with some proprietary files
Graphics now r29, from A6 2018 Q
Way too much stuff to list here, thx @Astrako for the work
- 20200613
Fixed GPlay crashes
June security patch, and all other LineageOS source changes
SEPolicy Enforcing
Reworked shims
Now using new power HAL
Many smaller optimisations
- 20200713
July security patch and all other LineageOS source changes
Reworked overlays
ROM now passes SafetyNet out of the box
Defined location provider to *hopefully* fix location with MicroG
Updated OMX libs
Other smaller fixes and optimisations
- 20200825 20200830
August security patch and all other LineageOS source changes
Updated FP from coral's April patch to keep passing SafetyNet
Switched to proprietary audio HAL - fixed in-call echo
Other smaller fixes and optimisations
NOTE: Encryption is currently extremely broken and your device will not boot if you'll try and encrypt.
- 20210118
January security patch and all other LineageOS source changes
Other smaller fixes and optimisations
Reserved
Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)
banciii said:
Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)
Click to expand...
Click to collapse
I'm dumb for not testing this, I gotta look at home
Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.
yann29 said:
Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.
Click to expand...
Click to collapse
I am not the author of Lineage 16.0, I only use the same mirror
The maintainer of LineageOS 16.0 is @McFy.
If you have the problems with the camera, this sounds like an app using the camera when you try to use it and I haven't been able to reproduce the problem. Please check all your apps and report back.
Hope you like the ROM
Ok thanks. Another issue : I can't get split-screen working with any apps. And you?
Other issue : the echos in calls...but well-known issue on lineage. Hope you will find something...
That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?
starbright_ said:
That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?
Click to expand...
Click to collapse
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing
MartinYTCZ said:
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing
Click to expand...
Click to collapse
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.
starbright_ said:
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.
Click to expand...
Click to collapse
Yup, ROM is not spoofed out of the box, so your only hope is nanodroid patcher, which doesn't seem to work in Q :/
Also if you've already got Treble, you can flash this with the TWRP you are currently using
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I am building myself and running the latest at this time (using the crdroid device tree) and everything is running perfectly for me! (even with a few patches of my own like enabling dark mode in defaults app and a few command-line programs like rtl-sdr, no gapps (f-droid only)). Added screenshots to prove it indeed boots.
If I'm not mistaken this ROM uses the android_samsung_universal7870 device tree as it is on Gitlab?
Then the only few bugs I can talk about are the USB settings unable to be changed live while that worked on the outdated device tree from Github (screenshot can be provided), and the Camera, but I know that's already WIP.
(Sure there's echo in calls but... No one was successful at fixing this and even the crappiest patches I tried myself didn't work)
Thanks to all those who works on this device tree.
The provided Rom of the dedicated XDA thread run fine on my device but when building myself, I have the same problem : traped on bootanim.
Strange, I supose it's my buid env, my laptop is on Debian 10 and I did not make any mod on the standard base.
I will try with a VM and Ubuntu LTS as sugested by AOSP Project.
MartinYTCZ said:
LineageOS 17.x Unofficial for Galaxy A3 2017
How to install
Make sure you have latest bootloader and modem before installing this.
Created 2020-02-22
Last Updated 2020-02-22
Click to expand...
Click to collapse
Thank you for great work, can I ask from where can get latest modem and boot-loader without download whole firmware?
Hello,
Problems are solved ?
Echo present in calls for the other side (investigating)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (investigating)
Stretched preview in camera, photos are fine (probably unfixable)
And stay at home.
Best regards
Migrate doesn't detect it as an installed rom, any help?
pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I have pushed some changes to GitLab yesterday which fix this problem. You should be able to boot a new build just fine now :highfive:
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"
}
This ROM is Beta and not ready for daily use at the moment
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@RaymanFX
@CTXz
I used @RaymanFX's T815 image to base my cm 13.0 build on, which in turn is the base of cm-14.1 and this lineage-14.1.
Before you start
THIS ROM IS ONLY FOR THE SM-T810
Code:
*
* Your warranty will be voided !
*
* 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.
*
About the ROM
Current state of ROM : testing
Everything except what's reported below is working (or not yet reported as not working).
What is Fixed
In '20-09' build reboot to recovery triggers message 'Factory reset'. (wrong messagem not resetting)
Camera not working in selinux enforcing
Front facing camera unable to save image
Hardware codecs not working (fallback to software for mp3/flac works)
Limited wifi 5GHz support (channels above 100 give issues)
Video recording not working? (not tested on T810, reported not working on T815)
Mic not working (no input routing)
SDCard working again (broke after switch N blobs)
What is not working
Important
Bluetooth not working (broke with switch to N blobs, works on images before 23-04)
Fingerprint scanner not working
Minor
Bootanimation died with introduction Lineage animation
Instructions
How to install LineageOS 14.1
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy LineageOS 14.1
How to ROOT
As build-date 20-01-2017, root is by default not available. Install the correct root package from here. Install the arm root package after lineage. Then follow the steps below.
In LineageOS 14.1 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of LineageOS's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
14-05-2017 - Build SDCard fix, SD card wordk again. (BT still broken)
**********
24-04-2017 - Build with Nougat T815 (common) and T810 (device specific) blobs.
**********
23-04-2017 - Build with Nougat blobs.
- Broke external SDCard, BT
**********
16-04-2017 - Latest patches, including neat netflix patch.
**********
03-04-2017 - Netflix patch in self compiled build.
**********
12-03-2017 - Updated links here, uploaded build of yesterday (Patch level March).
**********
26-02-2017 - Build went Nightly (more Weekly).
**********
24-02-2017 - Removed rild correctly.
**********
17-02-2017 - Removed rild, not needed.
- Final test build before nightly.
**********
10-02-2017 - Several DRM fixes in common part. (Could fix netflix, can't test)
- Fingerprint services available (untested)
- Tablet encryption available (untested)
**********
29-01-2017 - Recompile with latest patches and manual update of bootanimation.
- Fixed compilation of bootanimation (latest build has one self-compiled)
**********
28-01-2017 - Mic fixed
**********
26-01-2017 - LineageOS new style, WITH_SU (builds after today will be without)
- No bootanimation. (so be patient, it'll boot)
**********
05-01-2017 - Latest patches and final rebrand.
**********
02-01-2017 - Sources patched so self-compiled dtb is used, so image boots... :D
- Latest gts2-common patches added.
- Product name rebranded to lineage.
**********
01-01-2017 - Complete image build with self-compiled dtb.
**********
29-12-2016 - First LineageOS recompile after rebrand is (mostly) finished.
- Latest patches.
**********
Downloads
All LineageOS 14.1 Nightly releases can be found here : https://download.lineageos.org/gts210wifi
Latest self compiled LineageOS 14.1 build : https://www.androidfilehost.com/?fid=529152257862726418
All self compiled LineageOS 14.1 releases can be found here : https://www.androidfilehost.com/?w=files&flid=138958
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, and already patching the common sources to lineage-14.1, without him this ROM would most likely not be possible!
All my sources can be found at github LineageOS -> gts2*
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
LineageOS 14.1 for Tab S2 9.7 wifi, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, RaymanFX, CTXz
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: LineageOS
Version Information
Status: Nightly
Created 2016-12-29
Last Updated 2017-05-15
You. Are. The. Man!
Sent from my ONEPLUS A3003 using Tapatalk
Wow that was fast
Running awesome BTW... Thanks!
Sent from my SM-T810 using Tapatalk
tzlot said:
Wow that was fast
Running awesome BTW... Thanks!
Click to expand...
Click to collapse
Could have posted a day sooner, but was messing with the dtb compile (@RaymanFX got it working, currently compiling to test).
I hope the solution workd for all Tab s2's with the exynos chipset. I think the T71x tabs have issues with the stock dtb/kernel combination. Would be nice to get those builds up and running again.
Might flash this tomorrow. Anyone try Netflix on it yet ?
Awesome stuff. Will give this a flash here in a bit after I do a Odin. Just for my infos :angel: Does this have similar tweaks to CM 14.1 did or still pretty barebones at this date. Either way it won't stop me from trying it, just curious.
maddog975 said:
Might flash this tomorrow. Anyone try Netflix on it yet ?
Click to expand...
Click to collapse
DroidIt! said:
Awesome stuff. Will give this a flash here in a bit after I do a Odin. Just for my infos :angel: Does this have similar tweaks to CM 14.1 did or still pretty barebones at this date. Either way it won't stop me from trying it, just curious.
Click to expand...
Click to collapse
It's a rebranded cm-14.1, so expect all issues cm-14.1 had to be acailable in this build as well, until we fixed them.
Just replaced the boot.img from a failed build of yesterday with a new one with a self compiled dtb made today. The change to build the dtb killed something else, so I need to hunt that new bug down. Will update OP with link to new file when the upload finishes.
T_I said:
It's a rebranded cm-14.1, so expect all issues cm-14.1 had to be acailable in this build as well, until we fixed them.
Just replaced the boot.img from a failed build of yesterday with a new one with a self compiled dtb made today. The change to build the dtb killed something else, so I need to hunt that new bug down. Will update OP with link to new file when the upload finishes.
Click to expand...
Click to collapse
Sounds cool...and thanks a ton for all the work you're doing on this...and Happy New Year!
maddog975 said:
Might flash this tomorrow. Anyone try Netflix on it yet ?
Click to expand...
Click to collapse
Netflix will cast fine if you have a chromecast but doesn't work locally yet. The video zoom issue is much improved - YouTube works great, prime video works, Facebook video works but still a bit buggy (videos sometimes play at half speed, sometimes need reloading to work fullscreen).
Sent from my SM-T810 using Tapatalk
NalNalas said:
You're the best! I'll totally donate to you when I get the chance.
Click to expand...
Click to collapse
Just did exactly that yesterday . Work like this needs tangible support.
Sent from my ONEPLUS A3003 using Tapatalk
Thanks for the support.
Just compiled a complete image with the new boot.img generation (incl. compiled dtb instead of stock). Updated OP. Image not yet tested, flashing as I type..
T_I said:
Thanks for the support.
Just compiled a complete image with the new boot.img generation (incl. compiled dtb instead of stock). Updated OP. Image not yet tested, flashing as I type..
Click to expand...
Click to collapse
Mine is stuck on the boot screen.
Edit: I flashed the boot.img file from the 12/31 build with Odin and the 01/01 build booted fine.
Check, stuck on my tab s2 as well. Will build a new image tomorrow.
Sent from my SM-T810 running lineage-14.1
Build 01/02 boots just fine
Did a recompile, added latest patches of @RaymanFX on the gts2-common tree and rebranded the product name to lineage. (missed that one) Updated op with link. (and tested, it boots )
Feels a tad faster on the screen as well.
Sounds great that something is happening for the Tab S2 However i have a T815 (LTE model), any chance it will be supported somewhere down the line? (with or without LTE support, as i rarely use it)
Epedemic said:
Sounds great that something is happening for the Tab S2 However i have a T815 (LTE model), any chance it will be supported somewhere down the line? (with or without LTE support, as i rarely use it)
Click to expand...
Click to collapse
@RaymanFX is building the T815 sources and to be honest, doing most of the work. I mostly check of his patches don't break the T810 build. I don't know where he uploads his images.
Speaking of which, when he was debugging the T815 to locate the missing hardware decode support, he found, after a clean install, that they were used. I've compiled today and I'm now rebuilding my device, to see if graphincs have improved. When someone with netflix could test if it works after a clean flash, that would be nice.
OP updated with link to todays build.
Did a factory reset, fresh install - Netflix still can't play.
01-05 19:37:02.502 E/BufferQueueProducer(2616): [SurfaceView - com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity] cancelBuffer: BufferQueue has no connected producer
Thanks for the efforts anyway.
Drat, still no-go...
Sent from my SM-T810 running lineage-14.1
NalNalas said:
Youtube is having a problem where when you set the video to 1080p, after a minute or so the video zooms in awkwardly. It can be easily replicated.
Click to expand...
Click to collapse
This is a very well-known bug, affecting all AOSP-based 7.1.1 ROMs. The problem has to do with auto quality detection. If YouTube, and pretty much all web-based video, allowed for the resolution to be manually and statically set, this wouldn't be a problem.
LineageOS 16.0 Unofficial for Samsung Galaxy A3 (2015)
Supported variants:
SM-A300FU
DISCLAIMER
Code:
#include
/*
* Your warranty is now void.
* The ROM is under developement and have some bugs.
* We are 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 us for messing up your device, we will laugh at you. By flashing this ROM, you accept this disclaimer.
*/
LineageOS 16.0-20191129
Kernel 3.10.108
CAF LA.BR.1.2.9.1_rb1.5
Magisk compatible
MicroG ready
NFC disabled
Keymaster disabled
Thx to @vl_w
This TWRP recovery uses Lineage partition layout that differs from other recoveries.
Do not mix up efs/modem/apnhlos... backups with other releases.
All ROMs/Recoveries are compiled with latest LOS16 sources/toolchain.
BUGS:
No Sound (WIP - needs proper ASOC driver)
Probably the same as 15.1
Click to expand...
Click to collapse
{
"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 16 for Galaxy A3 (2015)
Uploading my files elsewhere is not appreciated, if you need to upload my files, just use the links provided here. Thanks.
ROM 16.0 -> DOWNLOAD
TWRP 3.3.1 -> DOWNLOAD
Credits:
@vl_w
Sources:
https://github.com/Galaxy-MSM8916
Version Information:
ROM Status: Beta
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Any Bootloader and Modem.
Based On: LineageOS 16.0
Created: 2019-11-29
Last Updated: 2019-11-29
Hi !
Works well for now :good:
Thanks to @DualJoe
@DualJoe
The rom works well but there is no sound.
What setting can I activate to fix this?
Thanks
carlos974 said:
@DualJoe
The rom works well but there is no sound.
What setting can I activate to fix this?
Thanks
Click to expand...
Click to collapse
Sound only works with headphones, yet.
carlos974 said:
Hi !
Works well for now :good:
Thanks to @DualJoe
Click to expand...
Click to collapse
Hi @carlos974! How did you manage it? On my A300FU there is still no Sound without headphones. Thumbnails is the same as yours.
Sorry, that was a temporal error! This request ist irrelevant!
The function of the speaker icon on the phone is meant to be to let other people participate in the conversation or to work while speaking (for example ). But if i tap on it, i cannot here anything anymore. The sound is not redirected to the speaker. Consequently I can only hear the conversation partner, if do not tap and keep the phone on my ear.
The driver for the speaker/amplifier is missing so it's not working at all atm. I will fix it asap.
But good to know that the phone function is otherwise working properly. Thanks for reporting.
OEM unlock required?
Hello! I'm just about to flash my Dad's A3FU with Lineageos 16 (which I use on my own phone), but something is unclear to me: there is no OEM unlock option in the dev menu. Does it means that I should not worry about it and I can simply flash anything I want (with heimdall, manually compiled because Debian's precompiled version seems to have a bug that prevents it from connecting to the phone)?
Thanks a lot!
Mathias
PS: by the way, any news on the sound routing issue for the speaker phone?
My A3FU hasn't got a OEM-unlock option, too (maybe it is like this in general). Never mind, just confirm "USB-Debugging". That's enough! (At least it was with me like that).
Make sure you've downloaded the OS from the link above!
I had no OEM unlock option either and just flashed LOS without problems. That's the only thing i can tell about this.
Regarding the sound problem: The Samsung sound driver implementation is horribly outdated and doesn't work properly anymore (just affects the external speaker on the backside). The userspace part is closed source and there seems to be some kind of race condition or timing problem. What people have done on other devices with same hardware is they patched the 'mute' function (or something similar) in the closed source HAL blobs so the speaker is always on. That leads to several side effects like the speaker is always-on as well when calling and similar. It's a dirty hack and unfortunately the only thing we have currently. I do not really like that. Instead i'm going to overhaul the kernel driver. I have the new codec driver running already. The next part is to glue it all together and bring it to userspace.
bavay said:
Hello! I'm just about to flash my Dad's A3FU with Lineageos 16 (which I use on my own phone), but something is unclear to me: there is no OEM unlock option in the dev menu. Does it means that I should not worry about it and I can simply flash anything I want (with heimdall, manually compiled because Debian's precompiled version seems to have a bug that prevents it from connecting to the phone)?
Thanks a lot!
Mathias
PS: by the way, any news on the sound routing issue for the speaker phone?
Click to expand...
Click to collapse
A3FU doesn't have locked bootloader at all.. so no OEM unlock option needed :laugh:
DualJoe said:
I had no OEM unlock option either and just flashed LOS without problems. That's the only thing i can tell about this.
Click to expand...
Click to collapse
Jesus, even OP doesn't know that... wasted..
Good luck :laugh:
P.S.: but it will trigger knox count (aka warranty from 2015 ) - useless these days
Great!
So, for me too the rom works great so far. But I have one more question: I've seen that SE-Linux is not enabled. Is it because this is a development rom and you need more permissions debug information, is it because of some other issues or is it related to a LineageOs misconfiguration (such as this issue)? Or in short, can I just revert the kernel boot parameter to get it to "enforced" and it would work?
Thanks a lot,
Mathias
You cannot enforce SELinux because your kernel is build with permissive policy.
bavay said:
So, for me too the rom works great so far. But I have one more question: I've seen that SE-Linux is not enabled. Is it because this is a development rom and you need more permissions debug information, is it because of some other issues or is it related to a LineageOs misconfiguration (such as this issue)? Or in short, can I just revert the kernel boot parameter to get it to "enforced" and it would work?
Thanks a lot,
Mathias
Click to expand...
Click to collapse
$ sudo setenforce 1
Hi!
Thank you for the ROM! am just flashing so i cannot refer to it.
May I ask when can we expect sound support and whether we get nfc?
Thanks again
It's not working. Needs help.
Hi. I've used TWRP 3.X and LineageOS 16.X before in my SGA300FULTE before. But other roms or recoveries didn't work. Only 2 TWRP 3.X and the LineageOS 16.X by @vl_w strangely seemed to work so I used them as daily driver. But these 2 became old and I needed new latest updated Roms and Recoveries. So I searched for new ones but found none. I'm glad when I found your this post a few days ago. Your TWRP 3.3.X is working somehow but the LineageOS 16.X isn't working. When I flash it from the Recovery and I reboot my device [ To remind you I always do full clean flash with wipe dalvik, cache, data, system and sometimes even internal storage ] it flashes and reboots and shows the Samsung stock Boot Logo/Splash Screen and the LineageOS also boots till the LineageOS boot animation. And it bootloops [ Either it keeps booting and showing boot animation forever or the screen gets dimmed with the boot animation completely freezed with the boot animation stopped ].
I was waiting for this latest TWRP 3.X and LineageOS 16.X. But It's very bad and sad thing that they're not working in my device . :crying: I thought I'd use them like before as daily driver. But I'm disappointed now because of this. I wish it'd work. And I wish this device SGA300FULTE had more developers working with more things and also make it Project Treble supported. I'm also trying to experiment with this to make it Project Treble supported. I'm eagerly waiting for your reply. I hope you can assist me with this. Thanks.
Alex Mahdi Ghost Infinity said:
Hi. I've used TWRP 3.X and LineageOS 16.X before in my SGA300FULTE before. But other roms or recoveries didn't work. Only 2 TWRP 3.X and the LineageOS 16.X by @vl_w strangely seemed to work so I used them as daily driver. But these 2 became old and I needed new latest updated Roms and Recoveries. So I searched for new ones but found none. I'm glad when I found your this post a few days ago. Your TWRP 3.3.X is working somehow but the LineageOS 16.X isn't working. When I flash it from the Recovery and I reboot my device [ To remind you I always do full clean flash with wipe dalvik, cache, data, system and sometimes even internal storage ] it flashes and reboots and shows the Samsung stock Boot Logo/Splash Screen and the LineageOS also boots till the LineageOS boot animation. And it bootloops [ Either it keeps booting and showing boot animation forever or the screen gets dimmed with the boot animation completely freezed with the boot animation stopped ].
I was waiting for this latest TWRP 3.X and LineageOS 16.X. But It's very bad and sad thing that they're not working in my device . :crying: I thought I'd use them like before as daily driver. But I'm disappointed now because of this. I wish it'd work. And I wish this device SGA300FULTE had more developers working with more things and also make it Project Treble supported. I'm also trying to experiment with this to make it Project Treble supported. I'm eagerly waiting for your reply. I hope you can assist me with this. Thanks.
Click to expand...
Click to collapse
Alright, let's go in parts:
1) It is very likely that this build is as old as those published by @vl_w, it would not be much of being surprised the problems that this ROM brings.
2) No one, not even the one who published this ROM, has done any further research on GitHub (where development is done for the MSM8916) on what happened to development for Android 9.
3) There are already Pie builds made for some phones like Grand Prime (as expected [additional note] the weak or no development for fortuna3g or serranove) with changelogs in late 2018 or mid 2019, I don't remember exactly, Still, it was not wrong to consult at least here with some of the developers for such phones on topics related to driver compatibility mainly, as long as libraries and other components are tested in order to see if work something or not.
4) At least with a33g it is impossible to have a generic image because there is no way to create a partition from which it is required to make it work. An average developer for this model simply won't want to work on it since, equally whether or not there's a chance to have a dedicated partition, Creating such a ROM is said to be very difficult.
5) It is highly unlikely that we will have a sufficiently new Android Pie ROM available, much less for the A300FU (which in theory among all models is the one that receives the most support), the most probable but not totally certain reason (due to some mistake) is that the published changes on LineageOS are not available on the final ROM, i.e The battery icon setting.
6) There is no one capable or willing to try again the construction of a ROM (for each version of the A3, of course) with the latest updates from each repository for, In addition to discarding the theory of the old versions, to advance a little more in the mediocre development that there is, even being reporting every moment to GitHub.
7) It is believed (as I did) that a much easier way is to port a ROM ... with Brotli it is an impossible mission, with that I summarize everything.
@DualJoe
Can we expect an update that fixes sound issue? It's basically the only thing that makes this ROM unusable, it would be great if you could manage to get around it.
At the moment there's nothing i can do. There are too many open questions regarding the manual kernel driver implementation and the alternative method (how ppl did it in the past) with proprietary blobs and newer CAF drivers is unreliable on LOS16. It works properly on one boot and on the next it's gone.
DualJoe said:
At the moment there's nothing i can do. There are too many open questions regarding the manual kernel driver implementation and the alternative method (how ppl did it in the past) with proprietary blobs and newer CAF drivers is unreliable on LOS16. It works properly on one boot and on the next it's gone.
Click to expand...
Click to collapse
Hi,
Thank you for the information !
Maybe try to build android 10
Have a nice day
{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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 me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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:
Everything (if it's not true - tell me)
Features:
4.4 EAS kernel with generater energy model
QS panel 3x3, 3x2 when there is not enough space on the screen (TODO: Make a magisk module to change the QS panel)
Fixed traffic indicator location
Removed black QS status bar background
Oldcam blobs
Instructions:
Reboot to Recovery (Prefer OrangeFox)
Format data, wipe cache, dalvik
Flash fresh firmware (optionally)
Reboot to recovery again
Flash the LineageOS build and any other addons you want (for example, Magisk)
Reboot to the system
Downloads:
ROM: here
Firmware: here. All firmwares for lavender are supported (Prefer latest Global Stable)
NanoDroid with MicroG: here. MicroG will work without the need to patch the system, signature spoofing already exists, but only for MicroG! Flash via Magisk recommended.
NikGApps: here
XDADevDB Information
LineageOS, ROM for the Xiaomi Redmi Note 7
Contributors: ElXreno
Source Code: https://github.com/LineageOS
Device Source: https://github.com/ElXreno/android_device_xiaomi_lavender
Kernel Source: https://github.com/ElXreno/android_kernel_xiaomi_sdm660
ROM OS Version: Android 11
ROM Kernel: Linux 4.4
Based On: AOSP
Version Information
Status: Stable
Telegram links: Support chat && Channel
Created 2021-02-01
Last Updated 2021-02-14
LineageOS 18.1 MicroG
Release date: 31/01/'21
Changelog:
Initial build
Traffic indicator moved to the right side
Removed black QS status bar background
Something else
Notes:
MicroG not included (but signature spoofing available, only for MicroG!). Use NanoDroid package if you want.
4.4 EAS with another energy model
Oldcam blobs
IORap enabled
QS 3x3
Download: SourceForge | MEGA
The rom goes very fast, the only thing that is really annoying is that when making or receiving calls the call interface does not appear, is there any way to solve this problem?
WOLFLIFEX said:
The rom goes very fast, the only thing that is really annoying is that when making or receiving calls the call interface does not appear, is there any way to solve this problem?
Click to expand...
Click to collapse
* I am not responsible for what may happen to your device, it is simply a solution that worked for me *
I found a solution for this problem the problem was in the NikGApps the shortest solution is:
1
Flash the rom first then reboot
2
Boot up, set the device normally and turn it off
3
Start recovey and flash NikGApps ( preferably the latest Canary version:
https://sourceforge.net/projects/nikgapps/files/Canary-Releases/NikGapps-R/03-Feb-2021/ )
4
Reboot.
LineageOS 18.1 MicroG
Release date: 14/02/'21
Changelog:
IORap selinux denials fixed
AOSP Surfaceflinger used
Fluence recording enabled
Other changes
Notes:
MicroG not included (but signature spoofing available, only for MicroG!). Use NanoDroid package if you want.
4.4 EAS with another energy model
Oldcam blobs
IORap enabled
QS panel 3x3, 3x2 when there is not enough space on the screen
Thanks:
@VerpaPhallus & @projectfluid for his device tree & kernel
Download: MEGA | IPFS
I'm currently using official 17.1 lineage OS can i dirty flash this ROM to change to 18.1 Lineage OS and is it stable for daily driver? Thanks in Advance
Babloo1989 said:
I'm currently using official 17.1 lineage OS can i dirty flash this ROM to change to 18.1 Lineage OS and is it stable for daily driver? Thanks in Advance
Click to expand...
Click to collapse
I recommend you to make a clean install, but you can try dirty. As for stability: almost everything is stable, but I would not recommend it if stability is critical.
ElXreno said:
What's working:
Everything (if it's not true - tell me)
Click to expand...
Click to collapse
So, everyone writes that even if the ROM has easily discoverable bugs, BUT, how stable is this ROM? I'm trying to find a good one for a daily driver that won't let me down in an emergency but so far it seems that all the ones I've seen are either a beta or have obvious bugs even though they're called "official" The only one I would potentially end up on is MIUI.
Can it be used as daily Driver?
Netflix and other apps thar block rooted phones are working fine?
Hi, I was using LOS 17.1 for MicroG without any issues but recently upgraded to LOS18.1 for MicroG (downloaded from lineage.microg.org and verified the download). Everything works well except for the camera. Out of the box camera app freezes frequently and then I tried Open Camera and a another camera app. Open Camera is a bit stable but still freezes regularly. Problem is worse when the camera app is being called by other apps.
I note that this has been reported in LOS forum but wondering whether there is a quick work around for this problem.
Many thanks.
evil-google said:
Hi, I was using LOS 17.1 for MicroG without any issues but recently upgraded to LOS18.1 for MicroG (downloaded from lineage.microg.org and verified the download). Everything works well except for the camera. Out of the box camera app freezes frequently and then I tried Open Camera and a another camera app. Open Camera is a bit stable but still freezes regularly. Problem is worse when the camera app is being called by other apps.
I note that this has been reported in LOS forum but wondering whether there is a quick work around for this problem.
Many thanks.
Click to expand...
Click to collapse
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.
Walden0 said:
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.
Click to expand...
Click to collapse
Thanks very much for the response. From what you are saying, I feel it may be easier to just downgrade to LOS17.1 which I was using before? I guess the other option I have is to wait for the next update to see whether the issue will be fixed in that release.
Thanks for your suggestion and clarification.
evil-google said:
Thanks very much for the response. From what you are saying, I feel it may be easier to just downgrade to LOS17.1 which I was using before? I guess the other option I have is to wait for the next update to see whether the issue will be fixed in that release.
Thanks for your suggestion and clarification.
Click to expand...
Click to collapse
i am also using los Q because i find it the most stable one. I m using loscam patch in Q as well for better video quality although.
And the camera issue wont get fixed until and unless someone takes over the development of los. currently it has no maintainer and tge builds we get are automated with los source side changes, not device side changes.
Walden0 said:
Hi, actually this is the wrong thread to post it.
But your solution is to replace new cam blobs with oldcam blobs and flash a kernel that is made for oldcam blobs.
I am attaching the oldcam blobs file for los that can be flashed through recovery. But note that you must change the kernel afterwards that supports oldcam. Otherwise camera will not work at all.
Click to expand...
Click to collapse
@Walden0, I thought I might give your suggestion a try before downgrading to 17.1 version. Can you please clarify the following?
1. To add the old camera blob, I could install this zip via Yellowfox Recovery?
2. How can I find out which kernel will support this oldcam blob?
Many thanks.
I have never heard of yellowfox recovery but if its based on twrp then most likely it should be able to flash the zip. (maybe you mean orangefox, if yes then you can flash)
The kernel should have "oldcam" or "old" in its name.
Walden0 said:
I have never heard of yellowfox recovery
Click to expand...
Click to collapse
Just being color blind!!...of course, it is Orange Fox Recovery!!
Interestingly, after I did my post, I just opened Settings->Apps->Camera and pressed 'force stop'. Then I started Open Camera which is what I normally use and so far it appears to be behaving OK. I tried a few still shots and one or two short videos - no freezing as yet but it is too early to know. I will keep testing over the next couple of days and see how it goes.
Thanks for your prompt response.
Just to report that the work around by disabling the Camera app so far have fixed the problem.
Any one who has the same problem may want to try out the following steps;
1. Go to Settings->Apps->Camera->Force Stop
2. Then use an installed app such as Open Camera
Note this is not a permanent solution but a work around and this has to be done each time the phone is rebooted.
EDIT: updated to 6 Dec 21 version and the camera behaves even worse than with the initial install! The above fix does not work anymore although it worked most of the time with the November update.
This ROM was abandoned, pitty, much more polished than official https://forum.xda-developers.com/t/...8-1-for-redmi-note-7-lavender.4381893/page-10.
But both suffer from the same issue: no Mass Storage Gadget so that UMS can work to make memory as USB drive.
LineageOS is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
Do not lock your bootloader with this installed. You must be 100% stock, I'd suggest on both slots, in order to re-lock your bootloader.
Code:
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Unofficial LineageOS Builds
Essential PH-1 (mata): GitHub Release Page (link was changed to 2021.03.12 Build)
Google Apps
Google Apps are not included in this build. At this time I do not plan to release gapps included builds. Users who require this will have to build or flash gapps their own.
Source
Device | Kernel | Proprietary blobs
Here's a local_manifest for those who want to build at home.
Known Issues
Wi-Fi WPA3 Network Connection (Connection to WPA2 Wi-Fi still works.)
Essential Camera App (Need to install Google apps.)
Release Signature (Signed with test-key. You can sign using your release-keys.)
Prerequisites
Unlocked bootloader
February 2020 Release | QQ1A.200105.032
Fastboot and ADB set up
Installation
Make sure you meet the prerequisites before continuing!
Using Fastboot
1, Flash February 2020 Stock Firmware (Run flashall.bat)
2, Flash LineageOS images (fastboot flash ***_a ***.img)
3, Erase userdata (fastboot -w)
(Reboot to Recovery and install Gapps)
Using TWRP
1, Install TWRP image
2, Reboot to TWRP (Power + Volume UP)
3, Start ADB sideload
(If your phone doesn't work touch panel, connect to PC using USB-C cable and enter this command in terminal.)
adb shell twrp sideload
4, Install LineageOS ZIP via sideload (adb sideload ***.zip)
5, Erase userdata
(Install Magisk and Gapps imitate steps 3 and 4)
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Contributors
conochy (github.com)
(I don't speak English as my main language, so sometimes the sentences are strange or I can't understand comments correctly.)
Source Code: https://github.com/LineageOS
Screenshots
{
"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"
}
Version Information
Status: Beta
ROM OS Version: Android 11, LineageOS 18.1
ROM Kernel: Linux 4.x
Based On: LineageOS
Security Patch 2020-03
Released Date: 2021-03-12
Created 2021-03-11
Last Updated 2021-03-12
Cool, Thanks man.
Ok, First issue using the "lineage-18.1-mata-magisk.img"
dememted1 said:
Ok, First issue using the "lineage-18.1-mata-magisk.img"
Click to expand...
Click to collapse
I noticed that I was building with the WITH_SU=true option.
I'm currently creating a build that doesn't have LineageOS SU.
If you're in a hurry, you can use LineageOS su removal (arm64) Version 16.0 to solve this problem.
(In my environment, I was able to solve it by using this.)
Thank you!
I have just released a new version.
The conflict Magisk SU and LineageOS SU has been resolved.
New version : GitHub Release Page (2021.03.12 Build)
Old version : GitHub Release Page (2021.03.11 Build)
(The link in the first post has been changed to a new one.)
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
I have just released a new version.
The conflict Magisk SU and LineageOS SU has been resolved.
New version : GitHub Release Page (2021.03.12 Build)
Old version : GitHub Release Page (2021.03.11 Build)
(The link in the first post has been changed to a new one.)
Click to expand...
Click to collapse
Ace thanks. Great work.
Thanks for this ROM.
What GApps are you using? I normally use NikGapps, but it fails to install...
MuddyDog said:
Thanks for this ROM.
What GApps are you using? I normally use NikGapps, but it fails to install...
Click to expand...
Click to collapse
I'm using NikGApps.
But in this LineageOS build, the NikGApps installer doesn't work, so I created a GApps Magisk module instead.
NikGapps Core, Basic Magisk Module installers, and a module that removes LineageOS apps whose functions overlap with Basic.
*It is used personally, I do not guarantee complete operation.
GitHub Module Download Page
Also, the official NikGApps installer has files to install in [Installer-File].zip/AppSet/[AppName]/[AppName].dat.br
If you extract [AppName].dat.br with 7-zip etc. and copy the files in it to the corresponding location of /system with a file manager, you can install it manually without using the Magisk module or the official installer.
Example: __etc__permissions -> Copy the files in that folder to /system/etc/permissions/
Example2: ___priv-app___PrebuiltGmsCore -> Copy the files in that folder to /system/priv-app/PrebuiltGmsCore/
If you want to use Google Setup Wizard, you need to format /data after manual installation.
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
I'm using NikGApps.
But in this LineageOS build, the NikGApps installer doesn't work, so I created a GApps Magisk module instead.
NikGapps Core, Basic Magisk Module installers, and a module that removes LineageOS apps whose functions overlap with Basic.
*It is used personally, I do not guarantee complete operation.
GitHub Module Download Page
Also, the official NikGApps installer has files to install in [Installer-File].zip/AppSet/[AppName]/[AppName].dat.br
If you extract [AppName].dat.br with 7-zip etc. and copy the files in it to the corresponding location of /system with a file manager, you can install it manually without using the Magisk module or the official installer.
Example: __etc__permissions -> Copy the files in that folder to /system/etc/permissions/
Example2: ___priv-app___PrebuiltGmsCore -> Copy the files in that folder to /system/priv-app/PrebuiltGmsCore/
If you want to use Google Setup Wizard, you need to format /data after manual installation.
Click to expand...
Click to collapse
Excellent, thanks again.
Are you planning to maintain this ROM through to Official Release?... or is it a personal project?
Either way, your work is greatly appreciated.
MuddyDog said:
Excellent, thanks again.
Are you planning to maintain this ROM through to Official Release?... or is it a personal project?
Either way, your work is greatly appreciated.
Click to expand...
Click to collapse
Sorry, I have no plans to continue building LineageOS 18.1 until official distribution begins.
The reason is that my Essential Phone was physically broken today.
(Please be assured that this LineageOS 18.1 Build is not the cause)
Therefore, I will not build for this model until we get it second hand again.
(If I build in the future, I'll post it in this thread to let you know.)
(However, considering the official build start time of LineageOS 17.1 last year, I think that the LineageOS 18.1 build will be officially distributed around next month.)
Thanks for this rom; enjoying trying it out.
Does VoLTE work properly on this ROM?
Hi,
For those who can't wait.
I've followed the instructions from
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡(https://github.com/conochy/LineageOS/tree/mata-18.1.)
You can download the files here :
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
And how do you like it? Any mejor bugs?
It's my daily driver since March 12, but I don't use Magisk and Gapps.
I was on ArrowOS before. They seems on par, at least for my usage
Build Updated.
Download Link
This is final my unofficial build of LineageOS 18.1 for mata.
My Essential Phone was physically broken, this build was not tested on my phone.
Official LineageOS 18.1 was released in 2021.04.02.
I recommend you to install official build.
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
Build Updated.
Download Link
This is final my unofficial build of LineageOS 18.1 for mata.
My Essential Phone was physically broken, this build was not tested on my phone.
Official LineageOS 18.1 was released in 2021.04.02.
I recommend you to install official build.
Click to expand...
Click to collapse
Thank you for all the hard work. I really appreciate that.
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
Build Updated.
Download Link
This is final my unofficial build of LineageOS 18.1 for mata.
My Essential Phone was physically broken, this build was not tested on my phone.
Official LineageOS 18.1 was released in 2021.04.02.
I recommend you to install official build.
Click to expand...
Click to collapse
Hey i'm having an issue where my cellular radio keeps connecting and disconnecting rapidly. Anything I can try to fix this? I've tried both your latest build and the official build.
Edit: Ive now observed the behavior after a fresh install. It only starts to happen after the device has been restarted. It will operate fine up until that point.
Edit 2: When I roll back to recovery lineage-17.1-20210329-recovery-mata.img and lineage-17.1-20210329-nightly-mata-signed.zip everything seems to work fine. So the issue must be in the latest builds.
Chirtan said:
Hey i'm having an issue where my cellular radio keeps connecting and disconnecting rapidly. Anything I can try to fix this? I've tried both your latest build and the official build.
Edit: Ive now observed the behavior after a fresh install. It only starts to happen after the device has been restarted. It will operate fine up until that point.
Edit 2: When I roll back to recovery lineage-17.1-20210329-recovery-mata.img and lineage-17.1-20210329-nightly-mata-signed.zip everything seems to work fine. So the issue must be in the latest builds.
Click to expand...
Click to collapse
On my phone, there was no particular problem with the connection of the cellular line (Japan, NTT docomo).
LineageOS 18.1 has some network bugs, such as Wi-Fi (WPA3), which I think are related as well. However, I think it will be fixed in the near future.
The official update for 2021.04.05 fixes some networks and APN, so give it a try.
｡･ﾟ･ヾ(｡•﹏•｡)ﾉﾞ･ﾟ･｡ said:
On my phone, there was no particular problem with the connection of the cellular line (Japan, NTT docomo).
LineageOS 18.1 has some network bugs, such as Wi-Fi (WPA3), which I think are related as well. However, I think it will be fixed in the near future.
The official update for 2021.04.05 fixes some networks and APN, so give it a try.
Click to expand...
Click to collapse
Installed the latest update still getting mostly the same symptoms. LTE network connecting and disconnecting rapidly still. Only difference is the device will no longer crash haha. I connect via Koodo mobile in Canada in case anyone else is having a similar issue.
I have a second essential phone I'm going to test this out on.
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.
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.
Click to expand...
Click to collapse
3rd PARTY ADDONS/MODS
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
HOW TO INSTALL LINEAGEOS
- Upgrade to latest available official firmware
- Upgrade to latest available TWRP
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal/external sdcard.
- Unlock bootloader and install TWRP.
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- RECOMMENDED: Do a factory reset! No support if you didn't!
- Flash LineageOS.
- Optional: Install the Google Apps addon package.
- Reboot
HOW TO UPDATE LINEAGEOS
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal/external sdcard.
- Flash LineageOS.
- Update the Google Apps addon package if it is installed on your current LineageOS version.
- Reboot
WHAT WORKS:
Wifi
Bluetooth
Audio
Camera
LED
USB
Encryption
Hall sensor
DT2W (disabled by default in settings)
Fingerprint
Selinux Enforcing
BROKEN:
GPS (working for some users, read page 5 and 6)
SIM card (help needed as I have the wifi-only-tablet)
Bluetooth aptx (reported by user, unconfirmed)
Wireless display (reported by user, unconfirmed)
DOWNLOADS
LineageOS 18.1: GitHub
TWRP: XDA Thread
DEVELOPER RESOURCES
GitHub
MANY THANKS TO THE CONTRIBUTORS
@Coffeinflash
Changelog moved to GitHub.
Spoiler: Old changelog
2021-08-07
August security patch
Minor UI changes
2021-06-27
SELinux Enforcing
Support fingerprint authentication in apps
Build kernel with clang compiler
Adjust kernel (add Wireguard VPN, drop zcache and legacy filesystems, etc.)
2021-06-15
Upstream changes (including June security patch)
Fingerprint sensor bring up
Rebase kernel on kuntao
2021-05-11
Camera is working now (many thanks to @Coffeinflash for fixing it)
May security patch
Applied a patch to fix the random shutdowns
2021-04-30
Initial release
Thank you @LumenReaper for this build!
I can confirm fingerprint is not working, but this is no bigger issue to me.
Flashed Magisk and changed fingerprint two times. But safetynet is still failing - no idea. My sim card is also not detected.
I use the tablet for youtube and yatse mostly. Youtube Vanced workes fine and my Bose headphones are also connected and working.
Looking forward to this ROM thank you.
Coffeinflash said:
Thank you @LumenReaper for this build!
I can confirm fingerprint is not working, but this is no bigger issue to me.
Flashed Magisk and changed fingerprint two times. But safetynet is still failing - no idea. My sim card is also not detected.
I use the tablet for youtube and yatse mostly. Youtube Vanced workes fine and my Bose headphones are also connected and working.
Click to expand...
Click to collapse
Thanks for installing. Glad to hear you're getting along with the current feature set. I should have mentioned that my tablet has WiFi only. Feel free to send me a log if you want, but I expect it will be difficult to fix it without the device itself.
Personally, I have not had any problems with failing safetynet. In which situation does it cause you problems?
Will continue with the fingerprint scanner as soon as I have time again.
PureMAD4 said:
Looking forward to this ROM thank you.
Click to expand...
Click to collapse
You' re welcome.
First I want to thank @LumenReaper for the efforts to keeping our tablets up to date.
Is this ROM stable enough to use it daily or can I better wait?
Personally, I have not had any problems with failing safetynet. In which situation does it cause you problems?
Click to expand...
Click to collapse
I do not see any issues with failing safetynet so far. It was working in 17.1 so I just wondered about the error after changing the fingerprint of the device by the help of magisk.
I will try to build the rom on my own with your sources - hopefully I can help with the non working SIM card.
Is this ROM stable enough to use it daily or can I better wait?
Click to expand...
Click to collapse
If you need a SIM card , fingerprint or camera then you need to wait. For normal multimedia usage I call it stable enough.
That won't matter for me, I'll flash the ROM and patiently wait until those work on the new ROM.
Coffeinflash said:
I will try to build the rom on my own with your sources - hopefully I can help with the non working SIM card.
Click to expand...
Click to collapse
Sounds great. Let me know if you run into any issues with building.
Do you think this wll also work for the TB-X705F, the successor model?
I've installed this ROM but one thing I noticed is that the internal storage and the contents in it aren't visible at all on MiXplorer Silver (The file manager I use)
It isn't visible at the default file manager too so I rolled back to Lineage OS 17.1
I would appreciate if this is fixed @LumenReaper
Googole said:
I've installed this ROM but one thing I noticed is that the internal storage and the contents in it aren't visible at all on MiXplorer Silver (The file manager I use)
It isn't visible at the default file manager too so I rolled back to Lineage OS 17.1
I would appreciate if this is fixed @LumenReaper
Click to expand...
Click to collapse
I cannot confirm this problem. The default files app shows me the internal storage and an SD card with content. If I would have had such a serious problem, I would not have published the rom yet.
Have you done a clean flash? Have you tried the format data option in TWRP?
flouli said:
Do you think this wll also work for the TB-X705F, the successor model?
Click to expand...
Click to collapse
I don't know, do you use the TWRP of this series?
No, I dirty flashed it.
I use TWRP for TB-X704F.
I'll also try a clean flash.
LumenReaper said:
I don't know, do you use the TWRP of this series?
Click to expand...
Click to collapse
There is a separate TWRP for the tb-x705f series - any chance that this will work with your ROM?
flouli said:
There is a separate TWRP for the tb-x705f series - any chance that this will work with your ROM?
Click to expand...
Click to collapse
I have not found a link to the code in that thread, but I expect the rom not to work when you need a different TWRP.
Great work Lumenreaper! (now I need to find the courage to install it on the only operational tablet that I own )
I did manage to build it myself using Docker & the docker lineeage-ci-cd image (see https://github.com/lineageos4microg/docker-lineage-cicd )
Hello,
LumenReaper!
Thanx for your work, sir!
Tell me, please - Lineage OS 18.1 made on Android 11.0?
There is no word about it in first topic of this thread.
If Yes, where can i find Google Apps package for it?
Asking , because at https://opengapps.org/ there is nothing for Android 11
Thank you
Installing now
will try BiTGApps
BiTGApps
Custom Google Apps Project
bitgapps.github.io
Installed with a little error after every booting
{
"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"
}