[ROM] [UNOFFICIAL][LP 5.1.1] CarbonROM (Z00A) - Updated August 9, 2016
{
"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"
}
Another build, compiled from source. But before I get too far...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Now that that's out of the way, this is a build of CarbonROM, using the device tree, kernel and advice from @jrior001 and @crpalmer. The current build is based off the latest CyanogenMod commits (and upstream AOSP) available at the time..
NOTICE:
Final build coming.
As work with Nougat begins, I will need to switch over to the MM bootloader. I won't be going back (downgrading) to check builds. For OctOS, as that is MM anyway, I can begin special builds (reliant on the MM bootloader) once I become established. For Carbon LP, it means the end of the road.
The September Android Security Bulletin should filter down to LP in about a week. Once that is done, I will crank out the final build, test, and post. Device-identity-wise, the only difference between the upcoming build and the one previous is the fix to the "off-path TCP" exploit. The ASB will have other fixes, but to the ROM instead (which is why I prefer to wait for the ASB).
Thank you for all the support. Cheers.
SCREENSHOTS:
One tab over
WHAT WORKS:
Powers on
Phone calls and texts
Mobile data (later builds)
Torch
Charges
MTP
Play Store
WHAT DOES NOT WORK:
GPS works, but does not seem to lock on out-of-the-box. Download your country's gps.conf and replace.
Doubtful NFC will work, as it does not look like that functionality is built into CarbonROM (missing nfc_enhanced.mk).
A random reboot was detected, at which point mobile data was lost. Toggle airplane mode to restore data.
As this ROM shares the same device tree as CM, this will share the same flaws. Otherwise, please tell me.
DOWNLOAD:
Mirror (AndroidFileHost)
GAPPS:
OpenGApps -or-
[AOSP] [X86] [Gapps] [5.1.X] [Zenfone Gapps]
INSTRUCTIONS:
Download ROM above, and a GApps package
Save/push files to your (External) SD card (preferably in the root folder where you can find it later)
Reboot into recovery ("adb reboot recovery")
Nandroid/Back up device (optional, but highly recommended)
Wipe cache and data/factory reset (unless updating from previous CarbonROM version)
Install ROM and GApps
Wipe Dalvik cache
Reboot
Enjoy!
CREDITS:
jrior001
crpalmer
deadman96385
CyanogenMod
CarbonDev (incl. Christian Oder)
Niropa
rirozizo
NSLUG
Did I miss anything? I appreciate the feedback, and any thanks as well!
XDA:DevDB Information
[ROM] [UNOFFICIAL][LP 5.1.1] CarbonROM (Z00A), ROM for the Asus ZenFone 2
Contributors
joel.maxuel
Source Code: https://github.com/carbon-z00a
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-08-07
Last Updated 2016-09-10
Other Info...
For those following along....
Project GitHub: https://github.com/carbon-z00a (complete fork of CarbonROM LP with ZF2 device projects)
LOCAL MANIFEST:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="cr-z00a"
fetch="https://github.com/carbon-z00a"
revision="lp5.1.1" />
<remote name="cm-z00a"
fetch="https://github.com/carbon-z00a"
revision="cm-12.1" />
<remote name="muppet"
fetch="https://github.com/TheMuppets"
revision="cm-12.1" />
<remote name="cyanogenmod"
fetch="https://github.com/CyanogenMod"
revision="cm-12.1" />
<!-- CM-ZENFONE2 DEVICE PROJECTS -->
<project name="android_device_asus_Z00A" path="device/asus/Z00A" remote="cr-z00a" />
<project name="android_device_asus_mofd-common" path="device/asus/mofd-common" remote="cm-z00a" />
<project name="android_kernel_asus_moorefield" path="kernel/asus/moorefield" remote="cm-z00a" />
<project name="proprietary_vendor_asus" path="vendor/asus" remote="muppet" />
</manifest>
CHERRY PICK(S):
Code:
None.
Make a new folder for and then initialize the build tree:
Code:
mkdir carbon
cd carbon
repo init -u https://github.com/carbon-z00a/android.git -b lp5.1.1
Copy your Z00A local manifest to ".repo/local_manifests/" (you may need to create the local manifests folder first), and then sync everything:
Code:
cp ../Z00A.xml .repo/local_manifests/
repo sync -f
Complete all the normal steps at this point.
CHANGE LOG:
Besides the project git hub...
CyanogenMod upstream
ZF2-Related Commits
Quick-Charging UI
AOSP upstream
Holy cow, I'm tempted to test this but I will wait for official release '-'
Yay...... Even more ROMS
SenpaiCham said:
Holy cow, I'm tempted to test this but I will wait for official release '-'
Click to expand...
Click to collapse
Official release may be a problem, as you would never get one of those from me - I am not affiliated with CarbonROM, I just like building their stuff.
For it to be official, one of their team members will have to own the device and take in the build themselves - in other words - do a lot more than my kanging (all the "work" for this project is in my second post and the commits in my github - all work I borrowed from somewhere else) - which is why I give credit where it's due.
Awesome work buddy
CM Theme Engine included ?
AL_IRAQI said:
Awesome work buddy
CM Theme Engine included ?
Click to expand...
Click to collapse
I think so - I remember seeing a Themes icon in the app drawer...
And thanks!
Sent from my ASUS_Z00AD
fast charge no work...use back 2.1v charge ok no problem,sorry for my bad English
I ran carbon for almost the entire time I had a Note 2. Fantastic Rom! Thanks for all the work in bringing it to the ZF2
pandan80 said:
fast charge no work...use back 2.1v charge ok no problem,sorry for my bad English
Click to expand...
Click to collapse
Unfortunately I don't have a fast charger to check (as I have the 2GB model), but can you try fast charging when powered off?
I think that was the recent progress with this ROMs older brother (CyanogenMod).
Sent from my ASUS_Z00AD
joel.maxuel said:
Unfortunately I don't have a fast charger to check (as I have the 2GB model), but can you try fast charging when powered off?
I think that was the recent progress with this ROMs older brother (CyanogenMod).
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Fast charging worked for me. I regular charged it and using the round battery indicator the phone charged like 3 % in 5 mins. The battery indicator read the %.
I used the fast charger and when plugged in the battery % changed to "?" while charging. After about 10 minutes I unplugged the charger and it had increased like 20%.
I like the ROM so far but I can't get data working. Sms and calls work but no data. Tried reentering the APN but no luck. Reflashing didn't fix it either. Any ideas?
rivethead23 said:
I like the ROM so far but I can't get data working. Sms and calls work but no data. Tried reentering the APN but no luck. Reflashing didn't fix it either. Any ideas?
Click to expand...
Click to collapse
I will play with it tomorrow to see if I have the same problem, and see what I can dig up. Good task for a rainy Sunday.
EDIT:
Looked at it tonight
Interestingly enough, it picks up all the APN's automatically. Stock never did that. But no mobile data. Could be that I used the CAF version of the hardware_ril project (only because the standard version stalled the device on boot). Most likely, it has t do with Carbon working on their rebase - I built before hearing that they finished that (I have problems accessing their website so I thought maybe they bypassed their G+ page to place it on the news section of their site).
As a result of the current situation, I am unable to try a newer build right now.
Sent from my ASUS_Z00AD
Appreciate the work I hope you can get this ROM working Carbon was fantastic in the past.
Added to index, thanks for your work!
Sorry if this is a stupid question. But for us noobs, can you explain how this is different than the nightly rom?
oijjio said:
Sorry if this is a stupid question. But for us noobs, can you explain how this is different than the nightly rom?
Click to expand...
Click to collapse
Historically (at least with KitKat), CarbonROM was more feature-rich than CyanogenMod (at least, I found).
These days, it's had to say. CarbonROM bases itself off of CM and SlimROMs (and probably others) and the feature set is probably similar. I haven't tried CM 12.1 yet, so I cannot do a real comparison. But since Carbon is still getting their feet on the ground for this version, my bet is things are very similar (the options are just found in different locations).
Sorry, I cannot be more specific. These are features I enabled that seem pretty standard, the two that I think stand out are "App Circle Bar" and "AppBar" (those are two ways of accessing apps without going to home screen or app drawer - just pull from the left or right).
I featured the former in attached.
August 9th Build ...
... but still no mobile data
I did get something different when I cleaned flashed though - see attachment. I didn't get this before, and made me hopeful. Too bad it didn't make any difference in the end.
This version seemed to be stubborn at first. Can dirty flash (as far as I can tell - I did and no problems), but if you clean flash, you will have to power cycle (as in, don't soft reboot) after the first full boot to get service back.
Also, I took a logcat (of enabling data services), I could not find any "E/"'s relating to SIM or anything related to mobile data. So that was a dead end.
CHANGE LOG:
Upstream pull request into local project (android_bootable_recovery)
Some commits to the device tree and vendor info that may have been included in previous build
Unknown upstream changes
rivethead23 said:
Appreciate the work I hope you can get this ROM working Carbon was fantastic in the past.
Click to expand...
Click to collapse
I thought of something, and it was a dead end for me, but can you try downgrading your connection (I forget what the option is called, but it is on the parent page to the APN's), from LTE to 3G? Then reboot (power cycle, do not soft reboot) and see if you got connection.
I am unable to do this as my carrier does 4G only (LTE and fake-4G).
It's a long shot, and it means a slower connection if it does work, but if it does work, it may be a half-decent kludge for now...
That was one of the things I tried to get it to work. I did the following things (might help you eliminate some stuff):
Chose 3G/2G as my connection.
Removed and reinserted the SIM card with phone on (I got message like the one you got but it didn't work)
Removed and Manually put in APN information. (I am on T-Mobile in the USA BTW)
Turned off Phone removed SIM. Booted Phone with no SIM. Inserted SIM.
Copied the APN file (at /etc) from SlimROM (which data works on) and after flashing used TWRP's file manager to put it in the same location before the first boot of a clean Carbon.
To answer another person Carbon ROM has more options than CM, Slim, or PA for the Zenphone 2. Also on my previous phone (Note 2) CarbonRom was rock solid stable fast and good on battery life.
I think I know what the problem is.
android_hardware_ril has two branches: 12.1 and 12.1-caf. I originally pulled the project into my github, patched 12.1 branch, and added the project into my local manifests with the upstream removal included.
That build died at the splashscreen. So then I patched the 12.1-caf branch and changed the local manifest to use that branch instead. It booted, but you know what happened then.
I looked at the master manifest, and it calls on both at the same time, renaming the latter to hardware/ril-caf. Worse, my local manifest, because it removes the upstream ril project, really that should be plural because it attacked both, and I only put one back.
So, local manifest has been altered, synced, and building. Next morning I should have some indication on how it went. Maybe this time tomorrow I will have build three for the week - with working mobile data - uploaded!
Sent from my MeMO Pad 8"
UPDATE:
Guess what I found 3:00 in the morning...see attached clip.
Updated ROM is uploading right now.
CHANGE LOG:
Alteration to local manifest in include both hardware_ril projects
Some commits to android_device_asus_mofd-common and android_hardware_intel_img_hwcomposer (Aug 9th and 10th)
Usual upstream changes
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"
}
DO NOT REPORT BUGS UNLESS YOU HAVE DONE A FULL WIPE, INSTALLED THE GAPPS PROVIDED IN THE 2ND POST, AND ARE RUNNING STOCK KERNEL WITHOUT STUPID MODS OR YOUR BUG REPORT WILL BE IGNORED PERIOD.
These are UNOFFICIAL/DEVELOPER builds based of CM-12.1 for klte (GSM), kltespr, klteusc, kltedv, and kltevzw devices and by NO means this is my ROM. I am just compiling from
CM Source and 100% credits goes to TeamDouche, and all other coders who contributed to CyanogenMod.
For which devices, should work with all klte versions that are qualcomm
Included in the Unified GSM build
kltexx, kltelra, kltetmo, kltecan, klteatt, klteub, klteacg, kltedcm, klte
Individual CDMA builds kltespr, klteusc, kltevzw
Individual GSM builds kltedv
If your device isn't listed in the "individual" lists then flash the generic "klte" build
Click to expand...
Click to collapse
Code:
[B]IMPORTANT[/B]
* Do NOT expect daily builds. I'll build when I'm free.
* Do NOT ask for support for flashing in this thread.
* Do NOT use this unofficial build and ask for support at the official threads.
* Do NOT be rude.
* Respect all users
* If I see a NOOB question and I don't feel like replying, I WONT.
Built from CM source
Service
Text
Data
Call
Audio
WiFi
Google Now
Bluetooth
GPS
MMS
Video playback
Audio playback
Internal/External SDcard mounting
Camera
Video recording
IR Blaster
NFC
?????????
Do NOT use superwipes
DO NOT dirty flash over CM-12
Wipe data, cache, and dalvik cache
*** ((but do not report bugs if you didn't full wipe))
Flash ROM
Flash GAPPS (in 2nd post) (No other gapps packages are officially supported!)
Reboot
???
Profit
To enable Developer Options and Performance go to Settings, About Phone and repeatedly press Build Number.
If you use ADB read this: PSA by CM
If you use reboot to recovery read this: PSA by CM
Regarding new Superuser: PSA by CM
Read the FAQ thread here before posting any questions in this thread: FAQ
And any and all users in this thread who contirbuted or will contribute to making this ROM as stable as possible
Esa Laukkanen aka elelinux
Cyanogen Inc & Team-Kang
Garwynn XDA
MrTrip
Thescorpion420
DevVorteX
albinoman887
ktoonsez
so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means
Note: The name on the Paypal account may say Patricia, this is because it's a family Paypal account.
Thanks and happy flashing!
DOWNLOAD LINK + CHANGELOG in 2nd post
XDA:DevDB Information
CyanogenMod 12.1 | Android 5.1 Lollipop, ROM for the Samsung Galaxy S 5
Contributors
albinoman887
Source Code: https://github.com/Team-Hydra
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
April 28
* Android 5.1.1
* Any and all upstream updates
** NOTE: I won't be doing anymore "releases" from this point on i'm going to just have a bot build nightlies. As CM starts supporting cm-12.1 nightlies for different variants (like klte and kltespr) i will drop them and only compile the remaining ones since there is no point in having two nightly builds that are identical
April 16
** Happy Birthday to my sister Kayla **
* Fixed MMS sending and receiving issues
* A good amount of stability updates from upstream
* android 5.1 r5
April 9
* Any and all upstream changes at time of compile
* fix for google messanger was refined and merged
* Mute and hold buttons now work in dialer
* Home button will not do anything unless the screen is fully awake
April 6
* Fixed NFC not working in last build
* Fixed recent apps key being active on lock screen
April 4
* Fixed lag with incoming and outgoing calls.
* Any and all upstream changes at time of compile.
Mar 31
* Blacklisting numbers is fixed
* Fixed picture messages from crashing google messager
* Any upstream changes at time of compile
Mar 30
* Fixed issue of package installer FCing at the end of manually installing an app
* A decent amount of updates/cleanup/small bug fixes by all the CM devs
* Synced with source as of 5PM PDT
* Updated gapps link to point to my web server instead of dev host
Mar 29
* android 5.1_r3
* Fixed Contacts app from FCing when selecting a contact (credits: DevorteX)
* Fixed Google Messanger from not working due to missing sql entry (credits: ktoonsez)
Mar 28
DO NOT dirty flash over CM-12
* initial build of cm-12.1/Android 5.1. THERE WILL BE BUGS so think before you post dumb stuff
* Most features work, SMS will FC unless you go to settings>privacy>blacklist and turn the blacklisting feature completely off. This will be fixed once the source is merged for it.
* Right now its just klte but i will be rolling out the other variants over the next 24 hrs or so so just check check back every few hours for your build.
Team Hydra Github (main): https://github.com/Team-Hydra
CyanogenMod Github: https://github.com/CyanogenMod
Due to resource limitations builds are released in a staggered fashion. If you find the newest build not available for your device it most likely means its compiling. Simply check back in 30-60 mins and it should be there
Latest Release: cm-12.1-20150428
G900I (kltedv) : Browse KLTEDV Build Archive
G900P (kltespr) : Browse KLTESPR Build Archive
G900R4 (klteusc) : Browse KLTEUSC Build Archive
G900V (kltevzw) : Browse KLTEVZW Build Archive
If your specific model isn't listed above and is a CDMA device it is not supported. Otherwise flash the unified GSM build below....
G900* Unified-GSM : cm-12.1-20150428-UNOFFICIAL-klte.zip | Browse KLTE Build Archive
----------------------------------------------------------------------------------------------------------------
GAPPS: : gapps-lpmr1-20150324-signed.zip
----------------------------------------------------------------------------------------------------------------
BUILD SERVER MIRROR : DOWNLOAD MIRROR
Reserved2
This might be a dumb question, but is it necessary to clean flash from your cm12 or must I clean flash to cm12.1?
Death Reality said:
This might be a dumb question, but is it necessary to clean flash from your cm12 or must I clean flash to cm12.1?
Click to expand...
Click to collapse
RE read the first post. it explictly says you have to do a full wipe. (unless you want issues)
Death Reality said:
This might be a dumb question, but is it necessary to clean flash from your cm12 or must I clean flash to cm12.1?
Click to expand...
Click to collapse
The OP says to clean flash.
other variants are building....
albinoman887 said:
RE read the first post. it explictly says you have to do a full wipe. (unless you want issues)
Click to expand...
Click to collapse
Opps my bad, gonna clean flash it on my 900f.
Is this work on k3gxx ? G900H
Sent from my SM-G900H using XDA Free mobile app
@albinoman887 awesome job,only 2 bugs i found the contact app fc when i choose a person,and the second1 its not a bug at all when i install and app from program installer its the instal button a little unresponsible and when instal completed program installer fc but the app is installed.
encountering the contact select bug here also
Death Reality said:
This might be a dumb question, but is it necessary to clean flash from your cm12 or must I clean flash to cm12.1?
Click to expand...
Click to collapse
Dude, you made my day! [emoji23]
After reading the first post, this is the very first post in this thread.. [emoji23] [emoji23]
downloading
thx man
macboy3000 said:
encountering the contact select bug here also
Click to expand...
Click to collapse
I haven't flashed this yet, (I'm waiting on the kltespr build), but the contacts fc issue COULD be related to the Facebook app. It's a known issue on 5.0 TW ROMs. If that's the case, it's not the ROM, it's the app. I've not come across a fix for it yet...
vizionary357 said:
I haven't flashed this yet, (I'm waiting on the kltespr build), but the contacts fc issue COULD be related to the Facebook app. It's a known issue on 5.0 TW ROMs. If that's the case, it's not the ROM, it's the app. I've not come across a fix for it yet...
Click to expand...
Click to collapse
I don't have facebook installed though
@albinoman887, thanks very much man. the rom's running smooth so far. incallui seems fixed finally as was running cm12.1-20150327. havent run into the contacts issue yet, i don't use the facebook app and i see what you mean. dialer has a bit of lag when making a call. messaging seems fine. keyboard in messaging has been fixed, phew. battery life was better on cm12.1-20150327 because after 10hrs phone used about 10% with little to no use and today on cm12.1-20150328 it's used about 6% in about half hour
i think i'll use this as my daily driver. i can live with the bugs, my bedroom has more, haha. we have had to sacrifice much of the functionality of the phone because we are rebels and we want progress, that's how i see myself anyway, i eat apples and break windows, lol.
i'm running stock cm12.1-20150328,
no mods,
few apps from playstore,
minimal gapps 5.1 from vinman's thread, i think,
recovery is twrp 2.8.5, on
sm-g900f
i fully wiped as in factory reset -> format data -> wipe davlik, system, data, internal storage, cache -> install. not run into issues except when i accidentally wiped my efs folder (took a month of stressing, nearly crying coz i couldn't update, searching, searching and searching some more).
Battery life and performance is pretty okay, thanks for the great work Albinoman
Great great great build! Only strange thing is that Google Messenger doesn't work properly.
I know its a preview/alpha Release and its works great.
But FYI: sync all contacts via Google and every contacts crash.
Greets maik
maikinho10 said:
I know its a preview/alpha Release and its works great.
But FYI: sync all contacts via Google and every contacts crash.
Greets maik
Click to expand...
Click to collapse
my contacts are crashing but not all of them. i'm just trying to figure out why. when i tried the rom first the contact i used didnt crash and the same contact isnt crashing and many others. at the moment i'll just say its 50/50 on which contacts are crashing and which are not.
{
"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 is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
{
"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>
/*
* 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. 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.
This thread is for Unofficial LineageOS 14.1 builds for lt02ltespr (SM-T217S). The following will not be supported here:
Custom kernels
Mods
Xposed
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Install the Google Apps addon package (Optional)
Reboot
Official Sprint Build
Older builds
4/13/17 Sprint Build
4/10/17 Sprint Build
4/8/17 Sprint Build
Addon su
su binary is not included in the ROM, you have to flash it manually after
addon su (choose arm)
Google Apps:
Mind The gapps 7.1.2
or
Open Gapps
Kernel
android_kernel_samsung_msm8930-common
My local manifest:
local_manifest
@aytex (He made all of the banners on this post)
@arco68 (For his work on the Galaxy S4 Mini)
@DarkFrenzy (I used his work as a reference to get some of the device specific fixes)
XDA:DevDB Information
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 - SM-T217S, ROM for the Samsung Galaxy Tab 3 7.0
Contributors
deadman96385, flashalot
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2017-04-09
Last Updated 2017-04-08
You tell me
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/details?id=com.tortel.syslog
Changelog:
4/13/17
Fixed the camera Thanks @DarkFrenzy
Removed unused drm blobs
Updated the time_daemon from shamu
4/10/17
Fixed glitchy power off animation Thanks @DarkFrenzy
Removed button backlight settings (They are unsupported)
Lowered the first boot time by enabling dexpreopt (The zip is a bit bigger but the old boot time was just unacceptable in my eyes)
Enabled some core system files to stay in ram so things should be a bit smoother.
Fixed adb not working unless you had selected mtp as the usb type
4/8/17
Initial release
I have redone the device trees from scratch based off of the galaxy s4 mini trees. @DarkFrenzy did the same thing awhile ago but he did not keep the history so it was useless to me. I also wanted to redo it because it lets me understand it better. My end goal is for it to become official but for that i have to fix the camera. But i have already upstreamed the kernel commits into the LineageOS msm8930-common kernel.
Thanks for still supporting our T217S. I'll give it shot and report.
deadman96385 said:
I have redone the device trees from scratch based off of the galaxy s4 mini trees. @DarkFrenzy did the same thing awhile ago but he did not keep the history so it was useless to me. I also wanted to redo it because it lets me understand it better. My end goal is for it to become official but for that i have to fix the camera. But i have already upstreamed the kernel commits into the LineageOS msm8930-common kernel.
Click to expand...
Click to collapse
Thanks for the Support for this device.
The camera is working fine in my RR build which I built with latest changes from Serrano tree which has some libc fix for camera.
For screen bug you have to set animate to true in device Samsung qcom repo like this https://github.com/FaArIsH/android_...mmit/51f24a5eed4203356c6669614f4dcbe979d74cc4
Yes its better to start from scratch then using my trees I m very lazy to use github that's y I don't use it the best way.
And also its best to give credits to @arco68 instead of me.
Sent from my SM-T217S using Tapatalk
DarkFrenzy said:
Thanks for the Support for this device.
The camera is working fine in my RR build which I built with latest changes from Serrano tree which has some libc fix for camera.
For screen bug you have to set animate to true in device Samsung qcom repo like this https://github.com/FaArIsH/android_...mmit/51f24a5eed4203356c6669614f4dcbe979d74cc4
Yes its better to start from scratch then using my trees I m very lazy to use github that's y I don't use it the best way.
And also its best to give credits to @arco68 instead of me.
Sent from my SM-T217S using Tapatalk
Click to expand...
Click to collapse
My trees are based on the latest serrano tree's i am not sure why the camera does not work. Thanks for the suggestion on the screen bug the next build will have it i merged in the samsung qcom repo.
New build in OP
Changelog:
Fixed glitchy power off animation Thanks @DarkFrenzy
Removed button backlight settings (They are unsupported)
Lowered the first boot time by enabling dexpreopt (The zip is a bit bigger but the old boot time was just unacceptable in my eyes)
Enabled some core system files to stay in ram so things should be a bit smoother.
Fixed adb not working unless you had selected mtp as the usb type
Thank you!! I'll be watching to see how this pans out.
New build in OP
4/13/17 build
Fixed the camera Thanks @DarkFrenzy
Removed unused drm blobs
Updated the time_daemon from shamu
I spoke too soon, when I wake it up from sleep the backlight is off.
New update in OP
This unoffical thread will now be for test builds that i deem stable so the community can test them before i merge the changes into the "stable" lineage builds.
Changelog:
Removed more unused drm blobs
Fixed backlight issues (Reverted back to the original liblights)
Update prima wlan firmware (This should fix 5ghz wifi let me know though i do not have one)
I am having a problem that everytime I try to install is comes up with error 7 and doesnt do anything in twrp.
Update:
Looks like I needed older version of twrp. It flashed waiting on bootup
Another problem, when doing the setup at first boot up I select new device and it crashes the wizard. I cant get past the wizard at all.
Azrael.arach said:
Another problem, when doing the setup at first boot up I select new device and it crashes the wizard. I cant get past the wizard at all.
Click to expand...
Click to collapse
Use the gapps from this post rather than OpenGapps.
Hello! Is there a way to port this over to SM-T210(R) and if so, could anyone give me resources and tips to help this project?
Thanks!
TrendingTech said:
Hello! Is there a way to port this over to SM-T210(R) and if so, could anyone give me resources and tips to help this project?
Thanks!
Click to expand...
Click to collapse
No sadly the other variants of this tablet use a different cpu/gpu so a direct port is not possible
Is it safe to flash the wifionly.zip file onto this image so I can remove the annoying Sprint messages (I have no intention of ever using the mobile functionality)?
zerbey said:
Is it safe to flash the wifionly.zip file onto this image so I can remove the annoying Sprint messages (I have no intention of ever using the mobile functionality)?
Click to expand...
Click to collapse
No. That is for RR 5.8.2 only. You can edit u r build prop and set .... tell u later don't remember ....
Sent from my ASUS_T00J using Tapatalk
DarkFrenzy said:
No. That is for RR 5.8.2 only. You can edit u r build prop and set .... tell u later don't remember ....
Sent from my ASUS_T00J using Tapatalk
Click to expand...
Click to collapse
Thanks, for now I'll just keep it in Airplane mode with only WiFi enabled.
Sent from my ONEPLUS A3000 using Tapatalk
DarkFrenzy said:
No. That is for RR 5.8.2 only. You can edit u r build prop and set .... tell u later don't remember ....
Sent from my ASUS_T00J using Tapatalk
Click to expand...
Click to collapse
I would like to know this buildprop setting. Thanks!
LineageOS 14.1 (Nougat) unofficial builds for the Droid Bionic
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* 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 any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
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 our Gerrit Code Review.
These are WIP builds of porting LineageOS 14.1 to the Droid Bionic (and also other devices using the same device/motorola/omap4-common-infrastructure). They probably won't work, so don't expect too much. Use on your own risk!
Builds:
Current official builds:
https://download.lineageos.org/targa (Droid Bionic)
(When migrating from Lineage unofficial, flash this first (manually mount /data in TWRP before flashing and unmount it afterwards) and then directly flash the new image without rebooting)
Su addon for official builds: [url]http://droid.cs.fau.de/lineage-14.1/addonsu/[/url] (The official addon doesn't currently install on Omap4)
Manual beta builds:
http://droid.cs.fau.de/lineage-14.1/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2017-06-10:
Hotspot fixed
Security updates
CM base updated
Last build before enabling official builds
2017-05-15:
Security updates
CM base updated
2017-04-11:
Fixed mobile data on Verizon
2017-04-05:
DRM playback fixed
2017-04-04:
Camcorder working, thanks to @Android-Andi (thumbnail picture is still wrong, but recorded video seems fine). This probably also fixed other media-related issues.
CM base updated
2016-11-27:
CM base updated
2016-11-13:
SELinux is enforcing
PackageInstaller works on ext3-based userdata again
2016-11-05:
First build
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data
WiFi
GPS
Camera
Video recording
Reboot to recovery
Playback of DRM-protected content
What's not working:
Probably most everything else, including, but not limited to:
HDMI
Data encryption (investigating, needs new unreleased safestrap)
Gapps:
OpenGApps
If you install Gapps after the ROM has been booted for the first time you either need to wipe data or manually delete /data/system/users/0/runtime-permissions.xml and reboot. Without this Gapps will crash constantly. This is due to a new permissions-system introduced in Marshmallow.
Installation:
You need a recovery supporting SELinux
A version of Safestrap (3.75) which supports SELinux can be found here: [url]https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75[/URL]
A newer version of safestrap which will format userdata as ext4 will be released shortly. You can also just reformat userdata to ext4 in the old Safestrap for now.
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
These versions (both unofficial and official) automatically switch to GSM/UMTS without installing additional patches.
Source / Repositories:
maserati device-support: https://github.com/LineageOS/android_device_motorola_targa/tree/cm-14.1
omap4-common device-support: https://github.com/LineageOS/android_device_motorola_omap4-common/tree/cm-14.1
omap4-common kernel: https://github.com/LineageOS/android_kernel_motorola_omap4-common/tree/cm-14.1
local manifest to build cm-13 for the Motorola Omap4 devices: http://droid.cs.fau.de/lineage-14.1/local_manifest.xml
XDA:DevDB Information
LineageOS 14.1 for Motorola Droid Bionic, ROM for the Motorola Droid Bionic
Contributors
stargo, Hashcode, joojoobee666, Dhacker29
Source Code: [url]https://github.com/CyanogenMod[/URL]
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-06-10
Created 2016-11-13
Last Updated 2017-06-23
Resized screenshot running official 20170707 nightly:
{
"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"
}
I've been using Lineage 14.1 on my Bionic since early May and have been using my Bionic as my daily-driver smartphone with Lineage since the end of June.
The only minor bug I'm finding, and I'm not sure if this is an omap4 device issue or if this is generally how it is on LineageOS no matter what, but the cell carrier isn't showing up as Verizon on mine.
instead, it shows up as "USA-480" pointing to the MNC and possibly not decoding it properly? APN listing is proper. data/phone/4G-LTE all work flawlessly so I'm under the impression this is just a bug someplace, however Data Usage from the status bar pull-down does say "No Service" no matter what.
Other than this and the memory leak which I believe to have been fixed now in the 0707 nightly, I haven't noticed anything that would disrupt usage.
Current Root add-on from the LineageOS Site at https://mirrorbits.lineageos.org/su/addonsu-14.1-arm-signed.zip DOES install on omap4 properly, contrary to the information above.
install via Safestrap TWRP normally.
My recommendation to anyone using this ROM on their Bionic is to make sure you have at least a 32GB MicroSD card installed for storage as onboard storage is slightly limited with safestrap ROM slot partitions the way they are, and if you haven't acquired one already, get one of the third-party 4000mAh extended battery packs with the extended cover. this adds bulk but also makes the phone easier to hold in the hand, aside from some extra juice to make the most of your Nougat-running Bionic for longer.
A bug I've noticed with in the 20170728 ROM and before, if I leave my phone on and use it normally for about a week, it gets to the point that saved images from apps like Discord or pictures taken through either the normal Camera app or OpenCamera are no longer seen in the filesystem until the phone has been rebooted.
Likewise, a bug since the end of May or thereabouts for me has been images in the camera folders (be it OpenCamera or the regular Camera app) tend to show up as 0kb files when accessing the phone in MTP transfer mode. it makes it hard for me as I then have to boot into Safestrap to get pictures off my phone in any reasonable amount of time or quantity.
I've moved on but cannot believe there are ROMs still for bionic
DarkPhazon said:
I've moved on but cannot believe there are ROMs still for bionic
Click to expand...
Click to collapse
Me too. I've moved on as well many years ago. I really miss my droid bionic. I had it rooted, safestrapped and with all the best roms at the time. I didnt' go pass Ice Cream Sandwich. But when I I moved on to Note 3 I didnt look back. I just un rooted my bionic and moved it over to Jelly bean 4.12. But I'm happy to see as well, that there some users still on there and Roms still coming out.
Crossposting this from the Razr/MAXX thread since this is vital information that will save users on Verizon a lot of headaches:
Sudosftw said:
Something I noticed I'm passing along for the sake of the thread, if anyone on Verizon puts their phone in CDMA Auto (PRL) mode and not LTE/CDMA Auto (PRL) mode in the phone testing menu, the data connection immediately becomes a LOT more stable. You're stuck on 3G for data, but the upside is that the data connection no longer cuts out as it moves from 3G/4G/1X/etc. depending on coverage. 3G/1X switching is immediate and works perfectly, but 3G/4G switching seems to do something terrible that makes the connection unstable and causes the "No Service" deal.
4G mode still shows USA-480 instead of Verizon Wireless as the ERI, and that still to this day a year later confuses me. with 3G/1X it ALWAYS shows as Verizon Wireless and connection information shows correct.
I'm going to be crossposting this information in the Bionic and Droid 4 threads as well to help since this is definitely a platform-wide issue. I popped my sim card into my Droid 4 and got the same results.
Click to expand...
Click to collapse
Support has ended.
LineageOS no longer officially supports this device.
You are now officially on your own.
You can find the final builds here: http://droid.cs.fau.de/Official_Lineage_Builds/
or here (MEGA Mirror)
These directories include the ROM files, addonsu package for 14.1, and the weather provider APK if needed.
I'm expecting this information to hit the OP post very soon.
It was a good run. These phones lasted many more years than they were intended to in the wild, and with Verizon killing 3G support for non-VoLTE devices later this year, they will become useless in the United States on their network. They are likely already useless on most others. Their time is up. I suggest anyone at all still holding on with one of these as a daily driver to consider your upgrades very very soon.
Goodbye Moto.
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: