Related
*** This project is now abandoned in favor of the LineageOS variant ***
This is a port of Cyanogenmod 14.1 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. Cyanogenmod needs no introduction, it is one of the most popular aftermarket ROM distributions around.
5.1.1 is the best that you can get from samsung right now and it is not known if they plan to do any upgrades. I have absolutely no idea why samsung chose to stay with the outdated 5.1.1 mid 2016 when we already got 7.1 coming out. This custom rom is probably the best you can get if you want an upgrade from Lollipop. Performance on the latest build is also better, you be the judge.
As this is the first CM-14.1 release, I don't recommend you use this as a daily driver, but it should be good enough for some. Make sure you read the pending issues below and decide if this is acceptable to you before you flash this rom. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on Cyanogenmod 14.1 sources which is based on Nougat 7.1.
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Update Dec 3, 2016
===============
Fixed GPS, Wifi Hotspot, Graphics issues, Calls, Camera,sdcard is now marked as adoptable.
Works:
- Wifi/SMS
- Audio
- Graphics with glitches (minor screen tearing, blank screen showing up on overlays)
- GPS
- Wifi Hotspot
- Incoming/Outgoing Calls
- MTP
Does not work:
- Bluetooth
- Camera
- LTE (Due to APN issues)
- Battery Meter not updating
Bugs/Known Issues
* Problems recording video
Other Notes:
- selinux permissive
Most of the issues are fixable, I just need more time and encouragement
SM-T280 Users: Unfortunately this rom would probably not work on it since the SM-T285 and SM-T280 have different kernels and slightly different hardware. I don't have access to this device so it would be hard for me to port it over. However I believe there are a lot of similiarities in the device tree that can be shared. If a dev with the SM-T280 is interested I can probably help.
Download
========
Remember flashing an unofficial ROM on your samsung device will probably void your warranty, Samsung representatives will probably not be able to help you as they are still stuck at 5.1.1 land as of now and have no idea how to handle a SM-T285 that is running 7.1.
As always flash this at your own risk. Make sure you have a copy of the stock ROM so that you have something to fall back to, which is highly the case when using an experimental rom.
See DevDB download section.
BUILD12032016
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
There have been reports that recent versions of open gapps don't work properly, it is advised to use older versions instead (e.g. open_gapps-arm-6.0-nano-20161109.zip)
Installation Instructions
==================
Perform a backup of all of your important files. This ROM is experimental and I will not be responsible for your loss of data.
Download the zip file and extract the tar.
Use Odin/Heimdall to flash the tar file to your device. If you are coming from stock oranother rom make sure you wipe first using TWRP. Coming from a previous version of OMNIRom for SM-T285 may not require a wipe, however please perform a wipe if you encounter problems.
Root and customization
===================
This ROM is a purely based on source and is not rooted out of the box. However you can easily root it by using TWRP to install the latest version of SuperSU.
If you want to customize this ROM and repackage it you may use this guide as a reference.
XDA:DevDB Information
CM-14.1 Samsung Galaxy Tab A 7.0 LTE (SM-T285), ROM for the Samsung Galaxy Tab A series
Contributors
jedld
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2016-12-03
Last Updated 2017-01-31
Nice job!!!
Great job! The ROM is impressively fluid, and I particularly love the way it renders fine text, which I appreciate because I prefer DPIs of 140 to 160. Unfortunately, just like in the early iterations of OmniROM 6.0, the tablet will not connect to the internet over cellular networks no matter how much I tinker with APNs. It's a great build, nevertheless, and I look forward to future releases.
Thank you !! Will give it a try.
posting here too (as did on omni - realized this is the cm 14.1 board)...
"briefly tried the cm14.1....much better very fast response-on the omni the pull down was an issue (would also ask me to format the sd card)
noticed here too the signal tends to drop in and out (wonder if it is some power saving going on-it goes to full strength during a call)...speakerphone also does not work here but must say this is better than the omni even though data does not work"
keyboard much better here too
on both cm14.1 and the omni, the dialer tends to be have some lag when pressing the numbers (do it too fast and can get many errors)-minor thing understand this is an alpha and the omni is a beta
thanks
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
mazmorbid said:
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
Click to expand...
Click to collapse
needs some xml changes that needs to be compiled into the framework for that I believe. Though there are more critical bugs I need to fix with this 7.1 rom.
I wish I could help in some way, appreciate your work.
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
khanhpt said:
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
Click to expand...
Click to collapse
Try using an older gapps package like from october, recent versions seem to have issues.
jedld said:
Try using an older gapps package like from october, recent versions seem to have issues.
Click to expand...
Click to collapse
Thank Jedld, i has tried 27th,october version and it WORKS, thank.
I used the version as recommended in the Omni ROM, which was from the 9th of November, no problems with the app store or downloading apps either.
Any closer to another release ?
Nougat will take a while unfortunately
jedld said:
Nougat will take a while unfortunately
Click to expand...
Click to collapse
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
mac231us said:
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
Click to expand...
Click to collapse
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
jedld said:
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
Click to expand...
Click to collapse
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
mac231us said:
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
Click to expand...
Click to collapse
Those patches didn't help unfortunately Though I've fixed network type selection in CM-14.1 already, unfortunately data connection still won't come online due to errors related to APNs. Seeing as this was working perfectly in CM-13 this could be a CM-14 or Nougat related change, it will take a while to figure out what that is. As for bluetooth I was able to get it to turn on, however it is still unable to detect/pair to any device, this is also something that was working in CM-13.
any hope on porting this to t280?
klemen241 said:
any hope on porting this to t280?
Click to expand...
Click to collapse
I don't have the T280 so I wouldn't know. There are devs that are trying or have tried to work on it, not sure about their progress.
Hello, I should be buying a Swift 2 Plus soon, and as a complete noob, I don't know what the death of Cyanogen is going to do to my device. Obviously it won't instantly brick it, but how am I gonna get future Android updates without installing a custom rom?
have a sexy christmas
Please, read my post here, and the (unconfirmed) Wileyfox's response to Cyanogen move here. It should be enough to clear your doubts
linuxct said:
Please, read my post here, and the (unconfirmed) Wileyfox's response to Cyanogen move here. It should be enough to clear your doubts
Click to expand...
Click to collapse
One thing relating more to the custom ROM area. So some of the CM team (not COS) are rebranding as lineage OS right. And they are continuing off the codebase of CM however we don't have a build of CM so how will and developer , from lineage or anywhere else, build a custom ROM without code from CM or AOSP. Unless Cyanogen Inc release the source code for our phone which I'm not sure they will. (Sorry if this is a noob question)
person123321 said:
One thing relating more to the custom ROM area. So some of the CM team (not COS) are rebranding as lineage OS right. And they are continuing off the codebase of CM however we don't have a build of CM so how will and developer , from lineage or anywhere else, build a custom ROM without code from CM or AOSP. Unless Cyanogen Inc release the source code for our phone which I'm not sure they will. (Sorry if this is a noob question)
Click to expand...
Click to collapse
You're absolutely correct. We can't start with the development with no sources. However, I don't think Cyanogen would do that at the moment, and, after seeing Wileyfox's response to Cyanogen moves, I think (and actually hope) they'll switch to an AOSP-based ROM with Android N 7.0 upgrade, and if that happens I'm really sure they'll have no problem on releasing the source code (remember Wileyfox devices tend to be quite developer-friendly). From that, we can work on bringing Lineage...
Heavily based on the WIP LineageOS port for the Moto E4 (Qualcomm) [perry] -- for more information about that, click here.
Known working:
Booting
Connecting to Sprint's 1xRTT network (2G data, voice, SMS)
Fingerprint sensor
WiFi
Broken:
Sound
Sprint 3G data and LTE (need to add in Sprint network blobs)
XDA:DevDB Information
LineageOS 14.1 for Moto E4 Plus (Qualcomm), ROM for the Moto E4 Plus
Contributors
ReimuHakurei, squid2, Alberto97
Source Code: https://github.com/ReimuHakurei/android_device_motorola_owens
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Alpha
Created 2017-10-31
Last Updated 2017-10-31
Uploaded another build that seems to get LTE on Sprint. All of the menus are still broken so you presumably need to be activated on stock before flashing.
Is there any way to make the fingerprint function to wake up / close screen to work with out requiring a pin/pattern/code to be active? That'd be an awesome feature
Installed on my XT1775 briefly and except for the sound this looks pretty good. I'm on AT&T and LTE worked fine, etc. I just can't live without sound as I need my phone for work teleconferences. I will *definitely* use this as soon as I can daily drive it!
I have tried (and failed) to get CDMA data properly working. Once someone gets CDMA/Sprint support working properly on one of the other devices in this family, it should be simple enough to port whatever the fix may be, but until that happens, this will likely remain as-is.
Since gsm seems to get LTE will this ROM still be worked on to get sound working? Even though I know CDMA users are out of luck for now. I have the standard e4 and want to buy a plus but I definitely need aosp ROMs.
Thanks for your work porting this. Actually shocked to not see more development considering how huge the battery is on the device.
fix-this! said:
Since gsm seems to get LTE will this ROM still be worked on to get sound working? Even though I know CDMA users are out of luck for now. I have the standard e4 and want to buy a plus but I definitely need aosp ROMs.
Thanks for your work porting this. Actually shocked to not see more development considering how huge the battery is on the device.
Click to expand...
Click to collapse
I need to repair my shattered Moto X Pure so I have a working phone to use while developing before I can do much more work here (ie: on fixing audio). This was mainly a proof-of-concept to make sure I was, in fact, able to get the thing to boot, before I spent too much work fixing other things.
For CDMA, I think the root of it is the new architecture Sprint is using in preparation for CDMA+VoLTE; I tried porting over files from the Moto X Pure's LineageOS port, but it uses older tech for CDMA internally. The Moto G5S has the same ISIMv2 SIM card on Sprint so should be similar software-side, and the Moto G5S will almost certainly have a pretty active community judging from past Moto G series phones. Moto X4 should be similar as well.
I am likely to be pretty busy for the next month or so, though, so probably won't have time to do any work on this until then.
so does someone plan to pick back up development on this? really surprised there isnt more devs on the plus model. much better build, camera, cpu and that big ?.
What exactly did you have to do to get this to work. I'm considering trying to port a few roms from perry over to owens, but if it's too hard, or just practically impossible I'm not going to bother.
Which version seems to have LTE working? I currently have no LTE just call(no sound) and txt lol
So I am attempting to build my first rom for the Moto e4 plus Qualcomm. I'm just following the build instructions on lineageos's website. I'm stuck now because there is not a device tree in the lineageos git. I see that the OP has a device tree on git and I also see that there is now a Moto kernel on git. I am unsure what the next step is? I'm unsure how to make the device tree part of my local git and also how to mix the new kernel posted from Moto. Any help and I will post what I create. Thanks.
@ReimuHakurei would you please attempt to fix sound for this custom ROM now that the kernel sources have been released. I've been looking forward to replacing the stock room on my phone for a while
FlagersXDA said:
@ReimuHakurei would you please attempt to fix sound for this custom ROM now that the kernel sources have been released. I've been looking forward to replacing the stock room on my phone for a while
Click to expand...
Click to collapse
Yes please! I really want to use this rom but I use my phone for listening to music all the time. Will some please fix the sound?
Bump, can someone please fix this?
Thank you for releasing this!
+1 for no sound or mic on xt1775
I tried Bluetooth and wired audio devices and sound/mic is not functioning for them either.
I am able to connect to the Verizon network with a their Sim through net 10, but only 3g (EvDo-rev.A, by choosing global auto) and not LTE after trying various modes in the 4636 menu. With the same Verizon Sim through net 10 my Nexus 5x h791 does connect to LTE .
Besides the issues above, this appears to be working well!
Also, if anyone can share complete stock partition images files (boot, recovery, and system partitions) for the xt1775, this would be appreciated, but I'm ok using my phone as is for now. I wish I had thought to make a complete backup by booting twrp through fastboot (fastboot boot recoverimagefilenamehere.img) and then making a backup first instead of flashing twrp before doing that. After I flashed twrp, instead of the Motorola bootloader unlocked screen, all I see is the white text "N/A" on a black background in the top left corner during bootup. Also, after I installed twrp I could no longer boot to the os until I installed this unofficial lineageos rom. I'm not sure if that is expected. Since I didn't make a backup of the system partition and boot before flashing twrp, I'm unable to restore the stock os. Lesson learned... immediately after making the mistake. I did make a backup of the boot and system partitions after flashing twrp before installing this unofficial lineageos rom(when I was already having the boot up issue), but when I restore them I have the same issue where the phone will not boot into the os. This is what I expected, at that point anyways.
Thanks again!
For Mediatek Variant
Sir,Any custom rom for Mediatek variant of this handset
fllannell said:
Also, if anyone can share complete stock partition images files (boot, recovery, and system partitions) for the xt1775, this would be appreciated, but I'm ok using my phone as is for now. I wish I had thought to make a complete backup by booting twrp through fastboot (fastboot boot recoverimagefilenamehere.img) and then making a backup first instead of flashing twrp before doing that.
Click to expand...
Click to collapse
I'm not sure if its the exact same variant, but @_maerk released stock images for the retail (snapdragon) e4 plus. Even if yours is carrier specific, as long as your bootloader is unlocked and you have the Qualcomm version you should still be good. I remember on my old Sprint Moto E from 2015 I could still flash the OS/Recovery/Boot images from the retail version, just not the modems or bootloader.
Update: I was able to restore to stock using the following link.
SCROLL TO POST # 10 for directions for Moto E4 Qualcomm (Owens) retail unlocked:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
Then I flashed Reiku's version of TWRP for the phone:
https://forum.xda-developers.com/moto-e4-plus/development/twrp-twrp-moto-e4-plus-qualcomm-t3697154
Then I installed this unofficial Lineage version:
[ROM][UNOFFICIAL][owens] LineageOS 14.1 for Moto E4 Plus (Qualcomm)
https://forum.xda-developers.com/mo...lineageos-14-1-moto-e4-plus-qualcomm-t3734197
Then I installed OpenGAPPs and AddonSu. The only hiccup I had through the process was that I got an ERROR Code: 64 when trying to install the ARM 64 version of openGapps in TWRP, so I used a non 64 version without issue.
Thanks to everyone for all of your efforts on these projects.
hi,
i have flashed my XT-1572 with LOS 15 unofficial version, but its not working properly sim slot not showing, network and lot of problem, now i m downgrading to LOS 14.1 but unable to flash, its made my cellphone piece of crap
please help...what to do
Tamesh1985 said:
hi, i have flashed my XT-1572 with LOS 15 unofficial version, but its not working properly sim slot not showing, network and lot of problem, now i m downgrading to LOS 14.1 but unable to flash, its made my cellphone piece of crap. please help...what to do
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3513299
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello everyone,
I've been using Yunique for almost 2 years now and very satisfied with the development got going for it.
Lineage OS is one of the best customs out there. But the official builds never support VoLTE out of the box. Can anyone tell me why they don't include that piece of software?? Most custom roms have VoLTE integration and also in Unofficial builds of LOS. Not that I'm complaining but I'm curious to know why.:silly:
https://sourceforge.net/projects/ro...-14.1-20180425-UNOFFICIAL-jalebi.zip/download
Lineage (volte) latest use it with casium 1.7
I too have a same problem. I tend to write a feedback to lineage os team even nothing works.
Is there any alternate way to get volte fix on official lineage os builds?
let me guess
official lineage-os support the old non-volte stock rom. yu sent the volte upgrade later by ota updates, I think volte in roms need these implantation in stock rom, this can be the reason, post reply if someone has more info