Related
The NookieDevs are pleased to announce the CyanogenMod 10.1.3.2 stable release for the Nook Color!
As the "stable" label suggests, all major features of the hardware work and the release should be suitable for day-to-day use on your Nook Color. As the "stable" label also suggests, updates (if any) will be primarily to fix bugs -- new features and big changes should not be expected.
Highlights: (mostly not news if you've been keeping up with CM10/10.1/10.2 nightlies)
Linux kernel 3.0.8, plus hardware support from TI OmapZoom's android-omap3-3.0 branch and board support forward-ported from BN kernel releases.
All of the features of CyanogenMod 10.1, based on Android 4.2.2.
Full 2D and 3D graphics acceleration using the GPU.
Unofficial Bluetooth support, including support for a wider variety of BT peripherals than in previous releases. (The Nook Color lacks a proper Bluetooth antenna, so range will be somewhat limited.)
10.1.3: significantly improved graphics performance and improved battery life over previous CM10.1 releases.
10.1.3: various bug fixes, including fixes for Bluetooth tethering, Adobe Flash Player, and a nasty hardware bug affecting the internal storage of some Nook Colors.
10.1.3.1: fix for a security bug reported upstream which potentially allows an attacker to obtain local root (see the dev thread for details). Thanks to Nico Golde and Fabian Yamaguchi for reporting, Ivaylo Dimitrov and Pavel Machek for working on a fix, and dhiru1602 for reporting a bug in that fix.
10.1.3.2: fix crash when opening "About tablet" in Settings. Thanks to CM's Ricardo Cerqueira for the fix and the rebuild.
Known issues:
Current releases of Netflix do not work with CM10.1 -- version 1.8.1 is the last version known to work. If you want/need a newer release of Netflix, look into the Xposed mod, which provides a workaround for Netflix -- pastordl has done a nice writeup of the process here.
The CyanogenMod Updater app may crash when checking for new updates. Deleting /sdcard/cmupdater and/or clearing the app's data may help.
Download:
https://download.cyanogenmod.org/get/jenkins/51847/cm-10.1.3.2-encore.zip
Code:
MD5: 72d6978a754d5637f28f3c031367781a
SHA1: 316da5997232bb641240c2378fdaa634ce5d50eb
SHA256: b9391d37418322b1960db8edd2a738a44ac2ea12cdeb02a80628c6f95efaa67f
Source code:
https://github.com/CyanogenMod/android_device_bn_encore/tree/cm-10.1.3 (device-specific source)
https://github.com/CyanogenMod/android_kernel_bn_encore/tree/cm-10.1.3 (kernel)
https://github.com/CyanogenMod/android/tree/cm-10.1.3 (manifest for the rest of the CyanogenMod source)
Build instructions (discussion of build issues belongs in the development thread)
This release is the product of much effort by many people over a considerable period: many thanks to fattire, keyodi, eyeballer, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor, dhiru1602 and many more. Thanks are also due to the CyanogenMod project, upon which we are building, and Texas Instruments, which provides excellent support for its embedded platforms to the open-source hacking community. (TI's exit from the consumer electronics SOC market is a loss for all of us.)
XDA:DevDB Information
CyanogenMod 10.1 Stable, a ROM for the Barnes & Noble Nook Color
Contributors
steven676, keyodi, fattire, The CyanogenMod Project, NookieDevs, many others (see post)
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 10.1.3.2
Stable Release Date: 2013-12-18
Created 2013-09-05
Last Updated 2013-12-19
Reserved
Google Apps; other CyanogenMod builds
Google Apps
http://goo.im/gapps
As of 2013/10/09, the latest release for CM10.1 is 20130812, but please check the linked page for updates.
Please make sure that you have the correct Google Apps flashed before reporting problems involving the Google Apps (Play Store, Google Keyboard, etc.).
Other CyanogenMod builds
This is the thread for CM10.1 stable releases. There are other official CyanogenMod builds for Nook Color available:
CM11 nightly builds -- these experimental builds, based on Android 4.4, contain the latest changes to CyanogenMod and to hardware support for the Nook Color. As the name suggests, new builds are made and posted (roughly) every day; these builds are fully automatic, with no testing done before posting.
CM10.2 stable releases -- while the state of the Nook Color-specific hardware support should be nearly identical to that of CM10.1, you may find this Android 4.3-based release more (or less!) stable than this Android 4.2-based one.
Archived nightly builds for CM10.2, CM10.1, and CM10. You may find the last CM10 nightly (20130421) faster than the later releases, particularly during playback of HD 720p video.
Please check that your questions are in the appropriate thread. (If you're interested, there's lots of past discussion in those threads, as well as the development thread.)
Frequently Asked Questions and Troubleshooting
The soft keyboard keeps crashing!
The Play Store is acting up!
Did you flash the correct Google Apps?
What happened to the "Developer options" and "Performance" screens in Settings?
They're hidden by default now in CM10.1 and later. To show them, go into "About tablet" and tap the build number (for CM10.1 stable releases, JDQ39) seven times.
How do I get the Honeycomb/ICS tablet UI?
You want to use the Auto-Patcher to modify your ROM for the tablet UI. (Don't forget to thank Caldair for maintaining the Tablet UI mod, and mateorod and the rest of the Auto-Patcher developers for building that tool.)
I'm having a problem with my Nook Color running CM10.1.
That's not a question
Okay, I'm having a problem with my Nook Color running CM10.1 -- is there something I can do to troubleshoot?
Glad you asked! Please check the following:
Does the problem occur with a clean install of CM10.1? This means wiping /data and not restoring a Nandroid backup afterwards. Don't restore system apps and/or their data in Titanium Backup either (user apps/data are okay).
Are you overclocking? If so, does the problem occur when you set the maximum clock speed to 1000 MHz or below? To be clear, we are not interested at this point in bug reports of any kind that happen if you have the maximum CPU speed set above 1000 MHz. If you're experiencing system crashes or "sleep of death" (SOD), you may also wish to try capping the CPU clock speed to 800 MHz (but if this helps, please report your problem here and fill out the hardware survey).
Do you have any patches, custom kernels, or other tweaks applied? If you do, does the problem occur without those applied? (We're not necessarily going to ignore bug reports from patched or tweaked systems outright, but it can make our job harder, and we do need to know what changes you have applied to judge whether or not the change might be relevant to your problem.)
I'm having no luck with the suggestions above. What information should I include with my bug report?
When reporting a problem, please include the following information if at all possible:
Full description of the problem -- "it crashes" doesn't count. How do you trigger the problem (or does it occur by itself)? What exactly happens when the problem occurs? How often does it happen?
For problems with apps or specific pieces of the system software: we'll almost certainly ask for a logcat of the event, so you'll save everyone some time by including it.
For problems involving system freezes, crashes, or SOD: if you can connect to the tablet via adb while it's "unresponsive", please provide dmesg and logcat output from that time. If you cannot, try power-cycling it while it's still plugged into USB, and provide dmesg output from immediately after the reboot, plus the contents of /proc/last_kmsg if that file exists (let us know if it doesn't).
For unexpected reboots: provide the contents of /proc/last_kmsg from after the reboot.
Edit: Used these instructions for installing 10.1 on a SDCard.
http://forum.xda-developers.com/showthread.php?t=1941858
Great thanks!
Sent from my NookColor using Tapatalk 4 Beta
Congrats and thanks again Steven and the other NookieDevs, this is running very well, at least on my NC, somehow seems a little more responsive/smoother (especially when background apps/downloads are running - new WiFi tweak?) than the recent nightlies/RC's. Great job, but, there is a new nightly calling, or I've sort of been wanting to try Mateorod's AOSP, besides, my schedule is beginning to settle back down enough that I will probably try to increase my "Android Ninja" experience, so I probably won't be stable long. Keep up the great work, glad to hear that you will still be tweaking it.
Question, are your latest WiFi and/or Graphics tweaks merged yet?
NC crashing hard with clean CM10.1 install
Hi,
great to see CM10.1 on NC. I have just made a clean install on my Nook and generally impressed. Unfortunately my Nook started crashing hard, something that I never experienced before It seems to be correlated with Gallery application, I can reproduce crash only after I open Gallery and then return to home page. Here is what happens:
open Gallery, look at one or few pictures
go back to Home
wait a bit, one minute or so, maybe go to other app or settings
screen goes blank, navigation buttons and status bar are still visible but display area gets dark
no response to touch or nook button
after ~30 seconds Nook reboots
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
I ran CM7.2 on the same device for quite some time and had no troubles with that. CM10.1 install is from final, wiped both data and cache, no google apps installed yet, no other apps restored, virgin clean :angel: No overclocking, and no other settings changed, no patches.
Thanks,
Andy
andy1001 said:
Hi,
great to see CM10.1 on NC. I have just made a clean install on my Nook and generally impressed. Unfortunately my Nook started crashing hard, something that I never experienced before It seems to be correlated with Gallery application, I can reproduce crash only after I open Gallery and then return to home page. Here is what happens:
open Gallery, look at one of few pictures
go back to Home
wait a bit, one minute or so, maybe go to other app or settings
screen goes blank, navigation buttons and status bar are still visible but display area gets dark
no response to touch or nook button
after ~30 seconds Nook reboots
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
I ran CM7.2 on the same device for quite some time and had no troubles with that. CM10.1 install is from final, wiped both data and cache, no google apps installed yet, no other apps restored, virgin clean :angel: No overclocking, and no other settings changed, no patches.
Thanks,
Andy
Click to expand...
Click to collapse
I can confirm this - I have been experiencing this for a long time now but since nobody else mentioned it I thought it could be just me (although I was doing clean installs). So this problem really exists.
I cannot reproduce this, but I flash the Picassa compatible gallery app - gapps-jb-picasa-20121011-signed.zip - after GAPPS
andy1001 said:
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
Click to expand...
Click to collapse
Mmm, that's pretty spectacular -- the system basically runs out of memory and the kernel goes nuts killing things to try to keep the system alive. It looks like the 720p video codec is eating the memory, and I believe we tracked that one down to the same root cause as the Flash issues. Can you try a CM10.1 nightly from June 25 or later (EDIT: or flash the patch in the next post on top of your existing CM10.1 install) and see if the problem still happens? (That reminds me, I promised to respin the binary patch for CM10.1 stable ... I should really do that when I get a minute.)
Patch for 720p codec issues (Flash, video thumbnailing)
As promised, here's the patch fixing Flash, video thumbnailing in the Gallery app, and potentially other 720p video codec issues for the CM10.1 stable release series. (The previous one I posted works as well, but is missing a couple of other potentially useful bugfixes in libstagefright.)
Usage: flash the attached ZIP file over your CM10.1 build from recovery. CM10 users: do not flash this -- use the patch in this post instead. Note that if you're on the CM10.1 nightlies, this patch was merged and should be included in builds starting from June 25.
(Source code: https://github.com/CyanogenMod/android_frameworks_av/tree/cm-10.1.0/media/libstagefright with https://github.com/CyanogenMod/android_frameworks_av/commit/c58721cbdcbfc46f550954a1c258d9b0529e4d81 applied on top.)
steven676 said:
As promised, here's the patch fixing Flash, video thumbnailing in the Gallery app, and potentially other 720p video codec for the CM10.1.0 stable release. (The previous one I posted works as well, but is missing a couple of other potentially useful bugfixes in libstagefright.)
Usage: flash the attached ZIP file over your CM10.1 build from recovery. CM10 users: do not flash this -- use the patch in this post instead. Note that if you're on the CM10.1 nightlies, this patch was merged and should be included in builds starting from June 25.
(Source code: https://github.com/CyanogenMod/android_frameworks_av/tree/cm-10.1.0/media/libstagefright with https://github.com/CyanogenMod/android_frameworks_av/commit/c58721cbdcbfc46f550954a1c258d9b0529e4d81 applied on top.)
Click to expand...
Click to collapse
It is really a damn shame we got that merged just after 10.1 Final was sent to the servers.
steven676 said:
Mmm, that's pretty spectacular -- the system basically runs out of memory and the kernel goes nuts killing things to try to keep the system alive. It looks like the 720p video codec is eating the memory, and I believe we tracked that one down to the same root cause as the Flash issues. Can you try a CM10.1 nightly from June 25 or later (EDIT: or flash the patch in the next post on top of your existing CM10.1 install) and see if the problem still happens? (That reminds me, I promised to respin the binary patch for CM10.1 stable ... I should really do that when I get a minute.)
Click to expand...
Click to collapse
I have tested both cm-10.1-20130627-NIGHTLY-encore.zip and final CM10.1 with your patch libstagefright-omxcodec-patch-for-cm-10.1.0-encore.zip, they both seems to be working OK, I could not make them crash in the same way as unpatched CM10.1 does :victory: Thanks a lot for the fix, much obliged!
Andy
Still having issues with the nook color.
Check the dmesg file for Cm10.1 stable.
Thanks for the patches <steven> Seems to help.
My stable is still holding up good on my NC.
mhzrus said:
Still having issues with the nook color.
Check the dmesg file for Cm10.1 stable.
Click to expand...
Click to collapse
This is what I encounter with Nook Color CM 10.1.2 stable version.
CMUpdater cannot download new Nightly!!!
Battery went flat no indicator.
Wifi issues, network error! For Nothing!
Touch Screen still having issues. The left hand side and right hand side of the screen cannot response to any touches! (About 2 inches thick!)
I come to know that there is issues with Nook Color Touch screen.
http://forum.xda-developers.com/showthread.php?t=1385896
CM10.1.2
A quick heads-up: CM10.1.2 was released last week (check the links in the first post), including important security fixes. (The Flash fix didn't go in and looks unlikely to go into the 10.1 stable series at this point -- you'll have to continue flashing the patch above for now.)
cm-10.1.2-encore stable vs nightly - Patch for 720p codec issues?
steven676 said:
A quick heads-up: CM10.1.2 was released last week (check the links in the first post), including important security fixes. (The Flash fix didn't go in and looks unlikely to go into the 10.1 stable series at this point -- you'll have to continue flashing the patch above for now.)
Click to expand...
Click to collapse
Thanks for that info steven676; so that patch will work for cm-10.1.2-encore stable?
What's the easiest way to tell if the patch is or isn't working on my NC?
Lastly, is it necessary or included with any of latests cm-10.1.2-encore nightlies?
:good:
eltrkbrd said:
Thanks for that info steven676; so that patch will work for cm-10.1.2-encore stable?
Click to expand...
Click to collapse
Yes, it'll work for CM 10.1.2 stable (or any other CM10.1 release).
eltrkbrd said:
What's the easiest way to tell if the patch is or isn't working on my NC?
Click to expand...
Click to collapse
Install Flash, enable plugins in the browser, then open Flash Player Settings -- if the bug is still present, the page will lock up and you'll eventually be prompted to kill the tab.
eltrkbrd said:
Lastly, is it necessary or included with any of latests cm-10.1.2-encore nightlies?
Click to expand...
Click to collapse
As noted in the post with the patch, the fix should be included in CM10.1 nightlies starting with the June 25 build.
[Q&A] [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam
Q&A for [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Just registerd to say thank you for 5.0 android!
Only yours build is working awesome! NFC, camera, battery life is exelect! I'm very glad. One problem is that i can't put some widgets on desktop... it crashes and reappearing without my widget.
Why you didn't update your thread, and what is differences in your build(for exmpl. the 2th of December and the 9-th)?
nikudim said:
Just registerd to say thank you for 5.0 android!
Only yours build is working awesome! NFC, camera, battery life is exelect! I'm very glad. One problem is that i can't put some widgets on desktop... it crashes and reappearing without my widget.
Why you didn't update your thread, and what is differences in your build(for exmpl. the 2th of December and the 9-th)?
Click to expand...
Click to collapse
I haven't gotten to the point with cm-12.0 where I'm comfortable "advertising" it yet. Once I get it building with linaro, and get init.d scripts and some other goodies working I'll do a new thread. As it stands, it's very much the same as brothaedhung's with some extra kernel kangs and some device tree tweaks.
As far as widgets go, I'm not sure as I haven't seen that issue. Could you describe the issue with some more detail, and get a logcat if possible?
Thanks for the kind words though
ronasimi said:
I haven't gotten to the point with cm-12.0 where I'm comfortable "advertising" it yet. Once I get it building with linaro, and get init.d scripts and some other goodies working I'll do a new thread. As it stands, it's very much the same as brothaedhung's with some extra kernel kangs and some device tree tweaks.
As far as widgets go, I'm not sure as I haven't seen that issue. Could you describe the issue with some more detail, and get a logcat if possible?
Thanks for the kind words though
Click to expand...
Click to collapse
Oh, you won't believe I just disable "Don't keep activities" and it works now!!!:laugh:
The problem was when i tried to put Clock for expl. the launcher crashes and appearing again without my widget. Now, i've put my widgets and turn on "Don't keep activities". Perfect! I could not spot any problems, yet!!! Good luck with developing, and thanks again!
ronasimi said:
02/03/2015 - Sorry guys, I've been slacking off on updating this post. All current builds are using my KK kernel brought up for LP, with stock frequencies instead of low_cpuclocks. I'll be posting a new build later this morning. As far as I know, this is the only CM build still using mako sources
Click to expand...
Click to collapse
Noticed this over here after looking in the Canadian section (which has most certainly be dead for a while). Great to see you're still active on this. Just want to make sure before trying this that there's nothing else required to move from KK to LP (assuming not since its on a KK kernel still). Any particular recovery recommended and/or version? I'm on a Bell E973 using PAC 4.4.4-RC2, TWRP 2.6.3.1.
Edit: Decided to update recovery to 2.8.4 from brothaedhung after doing some lurking around. Flashed 02/03 and full stock PA gapps. Everything butter so far. Cheers!
@ronasimi : Latest build is working fine, in call screen is also normal, just sensors not working some times,,
thanks..
Click to expand...
Click to collapse
I have the same issue in your latest CM12. Proximity and brightness don`t work at all. I use jb e970 modem. Don`t flash hybrid radio because I`m in Russia. Also there isn`t any frequence low than 300 Mhz...
And I try your build of CM11: 20141111. There are a lot of bugs:
1. In profiles doesn`t work ring mode "normal". It doesn`t swith to it after another modes (vibrate and mute).
2. Don`t work "Double tap to sleep"
3. In perfomance dont`t work setting minimal and maximum frequency - after rebooting they are turned to default.
I have e970 will it work with this rom?
dro3 said:
I have e970 will it work with this rom?
Click to expand...
Click to collapse
It works. You should give a try to the CM12.1 version. :good::good::good:
ryupunk said:
It works. You should give a try to the CM12.1 version. :good::good::good:
Click to expand...
Click to collapse
I have tried it but my phone gets signal lost many times
"ap watchdog bark detected"
Help!
Since i flashed 12.1 rom, this message with green screen appears frequently!
5.1.1 CM12.1 Unofficial, Watchdog Kenel Panics (green screens)
long post, so if you want the meat of the story scroll down!
hi guys, i'm an avid user of the e970 and i found this marvelous forum to be one of the most useful resources ever. freegee, lgnpst for when i bricked my phone, cm11, cm12, solid geeb kernel, validus, and now cm12.1 unofficial; it's all there. i'm certainly enjoying the experience that this device paired with this community has to offer.
first i'd like to thank the developers, and i'm seriously appreciating the active development on 12.1. i just finished using validus and while it was a much more solid experience than the short-lived cm12, android 5.0 was still killing me in terms of battery life. 5.1 certainly fixed that up though.
i want to second a few observations that are being made, which are the green-screen happenings. i want to mention something in particular though:
when i first flashed 12.1 unofficial i didn't have the recommended gapps at the time, so i flashed the minimal gapps for 5.0 (just to get wheels rolling per se). sure enough, it was a crazy experience. com.google.<insert service name here> was crashing repeatedly, often causing loss of functionality or green-screens. in a day i'd get anywhere between 4 and 7 green-screens (this was for three days, i'm talking about the 4/21 release). i re-wiped and formatted /system and re-installed 4/21 cm12.1, along with the recommended gapps this time.
NOW i'm having far fewer crashes, far fewer slow-downs and stutters; overall a much more lean experience. i also want to especially thank the developer for one thing: THANK YOU, for giving me back HSPA+ speeds on my att jb radio. validus and cm12 for some reason wouldn't give me HSPA speeds, just slow HSPA speeds that would take forever to peak at 200, 250 K/s (averaging around 70 to 140 K/s). now i can enjoy speeds up to 900 K/s (i'll run a speed test when a more stable release comes out)
so, is it gapps or a kernel issue? newer gapps reduced a lot of problems (though that's a given). also i'd like to point out another error: wi-fi. the mac address keeps changing upon reboot, namely the last three hex values. the first three are always 00:11:22. this wouldn't bother a lot of everyday users, but my workplaces utilizes mac filtering (only way around it is to use the battery-intensive 3g option instead, and i have terrible 3g reception at work where i sit; OUTSIDE my office, i get great reception, but it's bloody hot here x.x)
in any event, if someone could help me out or give me some advice that'd be great.
to summarize:
5.0 gapps + cm12.1 = lots of watchdog events
5.1 gapps + cm12.1 = a lot LESS watchdog events, still happening though
wi-fi mac address gets randomly generated at reboot
phone doesn't get detected by the computer on usb unless you leave it plugged in and do a soft reboot (advanced reboot option; common in most cm12.x instances with default kernels; solid geeb was better, and cm11 was flawless pretty much)
using built-in kernel
att jb radio
clockworksmod touch recovery, the last one (6.0.1.8 i think? it's the last one on their website)
4 gig micro sd card is in the slot, if that makes a difference
one more note: i'm having far fewer crashes on this new install maybe because there are only google related apps (other than whatsapp which i installed right away). future planned apps to be installed:
adobe acrobat
battlenet authenticator
es file explorer
facebook messenger
titanium backup
mx player
aedict japanese dictionary
busybox
greenify
orpheus music player
qr code reader
skype
supersu
terminal emulator
any increase in instability henceforth i'll let you know. also for anyone NOT having greenscreens on the e970, do you have whatsapp? if NO, interesting. if YES, still interesting, but please what version? mine's not the latest (yet)
blitz9826
so this is new:
after reaching 100% battery level on charge, the phone used to cool down. ever since switching to this rom, the battery DOESN'T cool down, it stays warm/hot. i know for a fact it's not a charger issue since i'm charging it with the same usb port as i have been in hte past (and every other phone for that matter on the same port)
any ideas?
blitz9826
sensors
Sensors isnt working. 28.04 build.
Will you fix it?
Icons are blurry?
Hey. Loving this ROM so far. Only problem is that the icons are blurry (not HD as usual). I wiped the cache and delvik cache but it's the same problem. Anyone know how to fix this? Thanks.
ronasimi, i am waiting, that you will read this. Please try to fix sensors in your unofficial 12.1 builds. I really want use your rom, but sensors is not working.
I have e970 with mako z30f bootloader, and latest twrp.
Auto rotation
The auto rotation is not working. Only staying in portrait. Can anyone help?
Mobile Data to Wifi Switching
@ronasimi
first of all thanks for the Great rom im using from almost a month with no issues at all.
Just a little question about wifi. Wifi did not connect automatically when my phone is locked. I've to wake it then WiFi connects immediately.
same is when im using mobile data and saved WiFi is in range. but phone will connect it,until i wake the device.
please help me out on this.
[SOLVED] Problems rooting 12.1 E971
Edit: For anyone else facing this issue, flashing the beta version of SuperSU from a custom recovery works.
On a previous 12.0 build I was able to get root just fine, but after clean flashing the latest 12.1 build no method seems to work. I've tried flashing the latest SuperSU update zip from TWRP, using adb to push su and busybox, and using the built in root in developer options.
Flashing the zip and using adb result in SuperSU saying there is no binary installed, and with the root in developer options it never pops up something asking for permission.
Has anyone gotten root on the latest 12.1? Thanks in advance.
Cm 12.1 Bluetooth Issue on E971
Thanks for the great rom. Works great except one minor. Bluetooth connection on and off consistently.
I have cm-12.1-20150521-UNOFFICIAL-geeb.zip rom installed.
Thanks!
Thank you for your hard work on the ROM.
On an E971 with a clean flash, as others above have reported, the sensors/auto rotation are not working.
Another request would be to add repo specifics on your description of the ROM at the start of the thread. You link to your github account where the repos are stored but there are many of them, some with similar names. I am interested in reproducing your build process and possibly contributing some changes, but I am not sure which specific device, vendor and kernel repos you are using to generate the build. Would love to get rotation sorted out and keep development going on this solid 5.1 option for a still capable device.
Still kind of suprised that CM isn't doing 12.1 builds for E973/E971 but it seems they have dropped a large number of phones with the move to 5.0/5.1 and angered a lot of people.
Thanks!
*** 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.
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance
Hello,
As the thread where I originally announced this was locked for reasons apparently unrelated to my build, and the links removed, I'm creating a new thread to keep the community aware of these builds.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
The build for the Asus Zenpad 8.0 Z380K[N]L (aka P024) is at https://lineageos.disavowed.jp/p024/. This appears to work on both the Z380KL (as reported in the locked thread) and my Z380KNL. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Edit: per moderator request, I need to provide a link to the source repository used to generate these builds to comply with XDA's interpretation of the GPL. It is the stock LineageOS repository, located at git://github.com/LineageOS/android.git. TheMuppets binary repository was used for the vendor blobs; it is at https://github.com/TheMuppets/
Hi, I have been using your build and updated my device weekly! it' s still good and awesome. (I also use your build for my nexus7)
if you find Oreo, Pie version! please let everyone know. Thank you.
Thank's keep update bro.
Hi, I don't see your weekly build for 22 Nov 2019.
Are there any issues ?
Nice update thanks friends l.
Yeap yesterday i reported, and TS promised to update.
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Question about Unofficial rom for Asus ZenPad 8.0 z380knl
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
poka_dan said:
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
Click to expand...
Click to collapse
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
As soon as I find out MTP is working I will flash the rom
wileyc said:
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
Click to expand...
Click to collapse
Gift was my pleasure
The info is most usefull. Thank you for that.
I am currently running my ZenPad 8.0 z380knl on Asus stock rom but ardently looking to upgrade to android 7.1.2 for security reasons as well as other reasons.
I was investigating if everything is working on the new rom. Also upgrade procedure from stock rom to lineage os and from lineage os 14.1 to latest 14.1 lineage os. Thankfully you cleared all that up. Thanks so much !
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
BTW, I haven't seen your new buld since last week.Will there be no update ?
Is everything working with this ROM?
Can i get confirmation from someone who is actively using it..
MTP and everything else working?
pokadan said:
Gift was my pleasure
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
Click to expand...
Click to collapse
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
androidlover2019 said:
BTW, I haven't seen your new buld since last week.Will there be no update ?
Click to expand...
Click to collapse
There should be an update (or two!) today. The build rooster hung about midway through last week's build for deb, and was actually still running after seven days. I killed off the deb build process and it's progressing to the other devices, although much slower than it should be. I'll troubleshoot this after the regularly scheduled build completes late tonight.
(I'm using Arch Linux on this build machine, and it seems that something in the filesystem layer in kernel > 5.4.10 doesn't like operating under sustained heavy load)
I saw your new build today and have installed it. Thank you
However, The latest security patch has not been applied yet. Hope it will come in next build.
Thank you so much for maintaining the device.
Thank you wileyc !
wileyc said:
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
Click to expand...
Click to collapse
I have put the latest available rom lineage-14.1-20200202-UNOFFICIAL-P024.zip on my device and works flawlessly!
Million thanks
I have installed the newest one (built on 08 Feb)
the Android security patch was updated to Jan 2020! Thank you very much.
I am worried how long you will keep sharing your build weekly.
Hope next 2 years Thanks again.
I have also installed the latest. Thanks so much!
Thankyou for the update :good:
What about selinux?