[UNOFFICIAL][OMS][ROM] LineageOS for Galaxy Tab E [SM-T560NU]

[UNOFFICIAL][OMS][ROM] LineageOS for Galaxy Tab E [SM-T560NU] - Miscellaneous Android Development

Code:
** Disclaimer
I am not responsible if flashing this ROM bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
ROM Information
ROM Target Device: Samsung Galaxy Tab E [SM-T560NU ]
ROM Status: Stable
ROM OS: LineageOS 14.1
Project GitHub Repositories: https://github.com/Galaxy-MSM8916
Project Gerrit Review site: https://review.msm8916.com/
Bug reports: https://bugs.msm8916.com/
Telegram Channel (for ROM build/completion notifications): https://telegram.me/GrandPrimeTWFZ
Telegram Group (for Q&A): https://telegram.me/joinchat/AJrZvz_pGY7Pvfis9kzMwA
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-T560NU[/B] - [COLOR="DarkSlateBlue"][B]gtelwifiue[/B][/COLOR]
Click to expand...
Click to collapse
Download
All Jenkins builds are testing builds, and as such, are likely to be extremely unstable or
unusable.
Code:
[B]All builds:[/B] [url]https://download.msm8916.com/[/url]
[B]Jenkins Builds Builds:[/B] [url]https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_Tab_E/[/url]
[B]TWRP Builds:[/B] [url]https://jenkins.msm8916.com/job/TWRP_Builds/[/url]
[B]GApps:[/B] [url]http://opengapps.org/?arch=arm&variant=micro&api=7.1[/url]
[B]RSS:[/B] [url]https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_Tab_E/rssLatest[/url]
Click to expand...
Click to collapse
Instructions
If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).
You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.
Click to expand...
Click to collapse
Installation via recovery (TWRP/LineageOS Recovery)
* Download a recent .zip file from the links above for your device.
* Reboot into recovery mode [Press Power+Volume Up+Home].
* Wipe your data and cache partition (equivalent to doing a Factory Reset)
if you are coming from a stock ROM.
* Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a device, click Install on TWRP on your phone and locate the zip file in the phone, or:
* Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter sideload mode.
Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:
adb sideload name_of_zip.zip
to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.
* Download and flash GApps in the same way.
Click to expand...
Click to collapse
How to provide logcats
Under Windows:
Code:
[B]* Install samsung device drivers and then
the adb utils from here:[/B]
[url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]
[b]* Then enable developer mode, connect your phone to usb,
and from [B]cmd[/B] paste this command:[/b]
[I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your desktop.[/b]
Under Linux:
Code:
[b]* Install the adb utils from your distribution's
package manager and execute the command:[/b]
[I]adb logcat > ~/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your home directory.[/b]
* Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.
* If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:
Code:
adb connect [ip address here]
And then the adb logcat command for windows.
Click to expand...
Click to collapse
Features
Code:
* OMS/Substratum theming support.
* The usual LineageOS features.
* All builds support over-the-air updates.
FAQ
Q: Are you taking device requests?
A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.
Q: But I don't have that kind of money! What else?
A: Alternatively, if you're skilled with Linux and adb, and have an unsupported device, if you're willing to work with me as a tester, that works as well.
Q: Are you accepting feature requests?
A: Unless you're willing to implement it yourself, no.
Q: Can you make XXX ROM as well as LOS?
A: Unless more people donate, no. I simply don't have the time to maintain more than LOS nor money to hold that many ROMs on my already (tiny) struggling server.
Q: Can I throw money at you?
A: Most certainly. Donations are always welcome.
Click to expand...
Click to collapse
You want to help?
We need hardware power to get the builds done.
If you want to help us go faster, send a PM to @kentone or
@vince2678. Your computer will act as a client for our jenkins server.
In a perfect world, that would be all, but unfortunately no. We need money to keep the server running and keep bringing these ROMs.
As always, logcat any problem you find.
Click to expand...
Click to collapse
XDA:DevDB Information
[UNOFFICIAL][OMS][ROM] LineageOS for Galaxy Tab E [SM-T560NU], ROM for the Android General
Contributors
vince2678, deadman96385, minz1
Source Code: https://github.com/Galaxy-MSM8916
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2017-06-08
Created 2017-02-03
Last Updated 2018-06-24

Reserved
Changelog
NOTE: gtesqltespr (SM-T377P) builds have been disabled until someone steps up for testing to resolve the issue in recent builds.
For more detailed changelog information, see the changelog on the download or jenkins servers for each specific build.
Code:
[B][U]29/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Added KeyDisabler. For devices with touch keys controlled separately
from the touch screen, this means that the virtual Nav Bar
can be enabled in the Settings. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using a kernel driver for disabling touch devices
when the screen is off instead of a user service for that. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated kernel to the latest upstream AOSP and
CAF tags. There should be a noticeable performance boost. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using OSS GPS code instead of prebuilt libs.
Location applications should be getting and reporting
satellite fix information properly. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Disabled cpusets support, which was slowing
down the system performance. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The auto time zone feature should now be working
proper, (that is, without resetting the time zone
to 0000 UTC).[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Data should be working fully on all devices. [/B]
Code:
[B][U]08/06/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Video recording should now be working [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The "message not sent" bug in text messaging
app(s) should be gone. [/B]
Code:
[B][U]01/06/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and prima (wifi)
driver to the latest caf branch LA.BR.1.2.9_rb1.18[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The reboots caused by errors in the
prima kernel driver should be gone.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built-into the kernel again.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] The sleep issue should be fixed in the latest build.
This was due to the failure to set a critical kernel
variable at boot because the kernel init system was
not interpreting a boot command line variable correctly.[/B]
* [B][[COLOR="Red"]FEATURE[/COLOR]][/B][B] OMS/Substratum support is now built into the
ROM.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS is enabled in-kernel, so F2FS filesystem
mounting and formatting should be working fully.[/B]
Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is being built as a module for now,
transitioning to a new kernel somehow broke the ability
to build it into the kernel binary.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Builds now use sdcardfs from Google. This should
result in faster file operations on the sdcard overall
compared to using FUSE as an overlay.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Both cameras should now be working [/B]
Code:
[B][U]01/04/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] LineageOS updater can reboot to recovery properly.[/B]
Code:
[B][U]11/03/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Switched binary blob base from
T377PSPT2BPJ1 (6.0.1) to T377PVPU1AOJ5 (5.1.1)[/B]
Code:
[B][U]16/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Decreased minimal scaling freq. to 200Mhz.
The previous scaling frequency minimum of 800Mhz was pretty high,
and could quickly cook your phone and kill power on mobile devices.
Lowering to 200Mhz should significantly extend batery life
on the stock scheduler. [/B]
[B][U]12/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.9_rb1.11 ] [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated kernel source [ to LA.BR.1.2.9_rb1.11 ] [/B]
[B][U]06/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Changed to a new kernel source [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Refactored device trees [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Monthly security fixes from Google [/B]
There are a lot more minor tweaks and fixes. I don't have the time to constantly be updating this; I expect you'll read the
changelogs anyways since I take my time to write the commit messages in detail.
Code:
[B][U]29/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Switched to LineageOS sources. [/B]
[B][U]20/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Made some substantial changes to our build
infrastructure, which should make my life substantially easier
and using Jenkins and all a more pleasant experience. [/B]
[B][U]17/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Reboot bug should be fixed [/B]
[COLOR="RoyalBlue"][B]gtesqltespr[/B][/COLOR]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Wifi should be working (build >= 4) [/B]
Code:
[B][U]16/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.7_rb1.7 ] [/B]
Code:
[B][U]15/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Started builds for SM-T377P [/B]
* [B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added KSM and ZRAM. These have to be enabled manually by
setting "ro.config.ksm" and "ro.config.zram" in the build.prop to true. [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Set maximum cpu frequency to 1209Mhz [/B]
[COLOR="RoyalBlue"][B]gtelwifiue[/B][/COLOR]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Rear camera is working [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] LiveDisplay feature is working [/B]
Code:
[B][U]11/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Switched binary blob base from
T560NUUEU1BPI3 (6.0.1) to T560NUUEU1AOK1 (5.1.1)[/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Audio and wifi now work proper. [/B]
Code:
[B][U]08/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Created forum thread [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] First build completed. [/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] None [/B]

nice work! maybe this would work on the t377p

That good ... there is the possibility of cooking something for the T560: C

I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3

I'm aware of the bug. For now, you'll have to flash the latest CyanogenModRecovery to update the device until twrp works proper.

I'm hoping you might know what I need to do here, but I installed a theme recently and it worked fine. But I ended up having to redo my tablet for a different reason, and ever since then whenever I try to use the same theme my system UI fails.

Finally custom rom for our device. :good: Can we hope to see CM13 on T560 also?

ElsaReyes said:
I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3
Click to expand...
Click to collapse
You can try the recoveries below, fully tested and working.
https://forum.xda-developers.com/showthread.php?t=3302935

gapps
hey guys does this require gapps?

You can install Gapps after flashing the rom, Yes.

im wondering if anyone knows the device name for the t377p, to edit in the updater script to try flashing this on a sm-t377p?

42o247 said:
im wondering if anyone knows the device name for the t377p, to edit in the updater script to try flashing this on a sm-t377p?
Click to expand...
Click to collapse
wont work needs another kernel

parrotgeek1 said:
wont work needs another kernel
Click to expand...
Click to collapse
cool cool. good to know.

ElsaReyes said:
I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3
Click to expand...
Click to collapse
The reboot issue for recovery is now fixed.

i got my t377p to boot all the way to the cm head logo by deleting the first line in the updater script and clean flashing the zip.
clean flash
restore boot partition from stock mm rom
boot
hangs at cm boot logo
ive begun reading how to make a custom kernel and the sources are available for the t377p. so if i dont get too frustrated i can try to compile one to make this rom work with my device

42o247 said:
i got my t377p to boot all the way to the cm head logo by deleting the first line in the updater script and clean flashing the zip.
clean flash
restore boot partition from stock mm rom
boot
hangs at cm boot logo
ive begun reading how to make a custom kernel and the sources are available for the t377p. so if i dont get too frustrated i can try to compile one to make this rom work with my device
Click to expand...
Click to collapse
A lot of things would not work, for example, the touchscreen. As similar as devices may seem there will still be hardware differences between variants and I don't recommend cross flashing.

Just flashed the 1/15 build and everything went well. I'm in the process of setting my Sm-t560nu up. I will report back after I'm finished. Thanks a lot for this Rom.

vince2678 said:
The reboot issue for recovery is now fixed.
Click to expand...
Click to collapse
Awesome. Thank you for all your work on this. Downloading the build now. :3
And just to keep you updated, it might not be in the newest build but I tried playing some of the videos I have saved on my sd card last night, and while the audio moves along just fine, the video plays all choppy and slow.

Hello, i'm glad to see a rom for TAB E, great work, but if you have time pls do something for T560, many users will be happy to see a CM on theyr tablets imcluding me, thanks allot for any answers
Sent from my SM-G935F using XDA-Developers Legacy app

Related

[TF700T][ROM][5.0][OFFICIAL] CyanogenMod 12.0

*** DON'T FLASH THIS IF YOU ARE NOT COMFORTABLE WITH DATA LOSS, INSTABILITY, RABID DOGS EATING YOUR CAT, OR SPACE ALIENS STARING AT YOU IN THE MIDDLE OF THE NIGHT! ***
*** If you like this post and can't donate to the cause, then hit thanks! ***
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 if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Credits:
Steve Kondik and the amazing CM team
See here for more contributors
And the many testers and contributors not listed above, including: chrmhoffmann, thunderger, jaybob413, Everett Coleman, Pretoriano80, untermensch, Richard Huynh and others I probably forgot
*** This is a development thread.
For questions and troubleshooting refer to this thread ***
*** Backup your data before continuing! ***
What works:
Audio
Hardware Acceleration
WiFi
GPS
Bluetooth
Touchscreen
HDMI
Microphone
USB host
Dock
Cameras
Encryption
Accelerometer
Gyroscope
Compass
Known issues:
Performance quicksetting tile isn't implemented yet (but is available through sys.cpu.mode property)
Dock battery indicator tile isn't implemented yet (but hardware works)
cm-recovery doesn't work (even boots)
lock key button in keyboard doesn't wake up the device
Netflix has issues after pausing, rewinding or fast forwarding. (libomxplayer.so) It's an ASUS issue at this point. (FIXED? Please confirm, I'm not seeing these issues anymore)
Screenrecording is broken, codecs issue (OMX doesn't support virtual displays, we only have 4.2 blobs, will not be fixed, unless Asus releases KitKat for our devices)
You tell us...
*** Backup your data before continuing! ***
Instructions (README, A LOT!!!!!!):
Make sure your device is unlocked. Grab the unlock utility here, under Others -> Utilities
(If you're on stock 4.2.x, skip this step) Install the 10.6.1.14.4 or greater bootloader for your variant, see here for more information.
Download Clockwork Recovery 6.5.0.1 here
Download GAPPS
Place the cm-12-YYYYMMDD-EXPERIMENTAL-JRUESGA-tf700t.zip (you can grab it from downloads section) and gapps-lp-YYYYMMDD-signed.zip (search in internet for a valid package) on your sdcard of your slate
Reboot to the bootloader: Power off slate, then: Power + Volume -. Hit Volume - until you hit the USB symbol, then hit Volume +.
Flash Clockwork Recovery
^^ BACKUP YOUR DATA!
Next, Wipe Data Factory Reset (ONLY NECESSARY IF COMING FROM ASUS stock ROM or something other than CM11.0!!!)
Then 'install zip from sdcard', 'choose zip from internal sdcard', then install the cm-12-YYYYMMDD-NIGHTLY-tf700t.zip.
Then install gapps-lp-YYYYMMDD-signed.zip.
Go back to the main menu and Reboot Now.
Upgrading builds:
Reboot to recovery
Install cm-12-YYYYMMDD-EXPERIMENTAL-JRUESGA-tf700t.zip
Reboot
or use built in cmupdater
If you run into issues outside the 'Known issues', please post a logcat.
You will need the adb binary on your computer (Windows, Mac or Linux):
Code:
adb logcat > logcat.txt
If are get a hard lock and have to reset, please pull the /proc/last_kmsg and post it after you are booted again.
Code:
adb pull /proc/last_kmsg
Please do not report on ANY known issues!!!
Help? Click here...
Donate to the devs:
dasunsrule32 - (Google Wallet - [email protected] or PayPal)
jruesga
Source(s), Gerrit and Changelog:
Source(s):
https://github.com/CyanogenMod/android_device_asus_tf700t/tree/cm-12.0
https://github.com/CyanogenMod/android_kernel_asus_tf700t/tree/cm-12.0
Gerrit ( Submitting patches/fixes ):
http://wiki.cyanogenmod.org/w/Doc:_using_gerrit ( When submitting a patch, please use this group vs adding myself and individual devs: Transformer Team )
Changelog:
http://www.cmxlog.com/12/tf700t/
XDA:DevDB Information
CyanogenMod TF700T CM-12.0, ROM for the Asus Transformer TF700
Contributors
jruesga, dasunsrule32
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Bootloader 10.6.1.14.4 or above
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-01-19
Last Updated 2015-01-28

Reserved

Reserved

cm-12-20150118-EXPERIMENTAL-JRUESGA-tf700t.zip
This is the first experimental image for TF700T CM12.0 (Lollipop) cm-12-20150118-EXPERIMENTAL-JRUESGA-tf700t.zip.
Please, be sure you backup your data before flash it. This are the MUST HAVE requirements (Downloads):
* 10.6.1.14.4 or greater bootloader
* Clockwork Recovery 6.5.0.1 (I didn't test TWRP)
* GAPPS 5.0 (Lollipop) - Search in internet for the proper ones
This is an experimental versión, so expect things not working.

Will test with TWRP 2.8.0.1.

Installed it successfully (dirty flashed over CM11)! No FC 'til now. Thank you for your hard work! :good:

Process.com.google.process.gapps has stopped error.
I use basketbuild gapps everything ran well before I installed gapps.

dracinn said:
Process.com.google.process.gapps has stopped error.
I use basketbuild gapps everything ran well before I installed gapps.
Click to expand...
Click to collapse
Please, try to post a logcat when reporting an error
Code:
adb logcat > logcat.txt
I'm using 20141109 from http://d-h.st/users/dhacker29/?fld_id=27426

jruesga said:
Please, try to post a logcat when reporting an error
Code:
adb logcat > logcat.txt
I'm using 20141109 from http://d-h.st/users/dhacker29/?fld_id=27426
Click to expand...
Click to collapse
My logcat.

dracinn said:
My logcat.
Click to expand...
Click to collapse
The basketbuild gapps are 20141109 (5.0) but the current version of android is 5.0.2 and the GoogleContactsSyncAdapter is crashing because doesn't find a resource. Try to upgradte to the latest published version of the dhackers99 gapps (http://d-h.st/users/dhacker29/?fld_id=27426)

jruesga said:
The basketbuild gapps are 20141109 (5.0) but the current version of android is 5.0.2 and the GoogleContactsSyncAdapter is crashing because doesn't find a resource. Try to upgradte to the latest published version of the dhackers99 gapps (http://d-h.st/users/dhacker29/?fld_id=27426)
Click to expand...
Click to collapse
Appears to be the same problem as far as I can tell. Will try clean install.

Lollipop using data=F2FS
Does anyone know if this can be used if data is formatted to F2FS?
Also does the kernel support it?

norm883 said:
Does anyone know if this can be used if data is formatted to F2FS?
Also does the kernel support it?
Click to expand...
Click to collapse
Not yet. I will consider to add it to in my TODO list.

F2FS
jruesga said:
Not yet. I will consider to add it to in my TODO list.
Click to expand...
Click to collapse
Thank you sounds great!

I use this version as my daily driver. The only big thing that i miss is the not working auto rotation. When can we expect a new (experimental) firmware?
Thank you!

My Public said:
I use this version as my daily driver. The only big thing that i miss is the not working auto rotation. When can we expect a new (experimental) firmware?
Thank you!
Click to expand...
Click to collapse
We have a fix for the rotation problem. I will leak a new flashable zip this weekend with some other fixes

Wrong thread... Sorry' 'bout that.
Added on edit:
FYI, the Q&A / Troubleshooting links to the CM11 thread rather than the CM12 specific thread.
This is the correct link:
http://forum.xda-developers.com/transformer-tf700/help/tf700t-cyanogenmod-12-t3006630

John Kotches said:
Wrong thread... Sorry' 'bout that.
Added on edit:
FYI, the Q&A / Troubleshooting links to the CM11 thread rather than the CM12 specific thread.
This is the correct link:
http://forum.xda-developers.com/transformer-tf700/help/tf700t-cyanogenmod-12-t3006630
Click to expand...
Click to collapse
I updated the link to Q&A thread. Thx

I find this helps a lot with the chrome problem. Try this !
http://www.techrepublic.com/article/pro-tip-speed-up-chrome-on-android-with-this-handy-hack/

cm-12-20150126-EXPERIMENTAL-JRUESGA-tf700t.zip
New experimental version is up in the downloads section http://forum.xda-developers.com/devdb/project/dl/?id=10822
Changelog:
* Fix auto-rotation
* Update wifi/bluetooth rfkill driver to bcm4330
* Added bluesleep support
* Updated media codecs (should improve netflix playback)
* Updated selinux policies
* Removed camera wrapper and forced camera api 1 (this should prevent errors with third party camera apps)
* Set "High Performance" mode during boot
* CyanogenMod CM12 2015-01-16 upstream changes
Thx to chrmhoffmann and lj50036 for some of this patches
Please, read the OP before flash it if you came from other rom or cm11.

CAF-6.0.1 [Osprey]

Hi All,
I've been working on a CAF version for osprey. This is started from kernel and device tree made by Alberto97 and Squid2, so thanks a lot to them for the bringup.
This version is very early and should only be flashed by people who know what they are doing. Flash this at your own risk.
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 if
* you point the finger at me for messing up your device, I will laugh at you.
*/
For now only a few things are working:
Working
Bluetooth
SMS/RIL
Sound
Camera preview
Not work
Maybe dual sim
Binaries
Here
Sources
https://github.com/boulzordev/local_manifests/tree/caf-6.0
There is still an issue when building, you must first build the kernel before being able to make a full ROM
XDA:DevDB Information
CAF-6.0 [Osprey], ROM for the Moto G 2015
Contributors
scritch007, squid2, Alberto97
Source Code: git://codeaurora.org/platform/manifest.git
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP
Based On: CAF
Version Information
Status: Testing
Created 2015-10-20
Last Updated 2016-01-05

Changelog
osprey-caf-87.zip
Updated to latest version of CM13 device specific + CM13 kernel)
Updated to LA.BR.1.2.7-00910-8x09.0.xml (February security patch)
Fixed the ringtone setting issue
Using frameworks_av from CM13 from now on.
osprey-caf-86.zip
Fix setting ringtone
Fix invalid number error when the call is ended by the other end
Sepolicy from cm imported (getting ready for Sepolicy being enabled)
osprey-caf-85.zip
Settings for light management ( When opening settings values reset to default)
Dual sims outgoing should be fine now
Updated frameworks_av with CM commits
Now building osprey/lux/surnia at the same time, this is why the version is 85
Rebased with newest version of LA.BR.1.2.7
Backup script when flashing in recovery. This works with open gapps. This means gapps are copied and restored when flashing
osprey-caf-0.25.zip
Updated to 6.0.1
Now using commonized msm8916 like cm13 will do
Using libshim from cm for the missing symbols
There is a bug the initial bootanimation doesn't seem to load. But it loads once rom is started and optimising applications.
aosp-caf-0.24.zip
Didn't have time to test it but this should include the following fixes. I might be off for a few days again, but I'll definitely keep on workin on this ROM.
The google webview
"Maybe the reboot option"
The time.sleep for the camera3 application that was posted somewhere in here (Or surnia's thread)
Let's hope exfat sdcard working too
aosp-caf-0.23.zip
Fixed boot. Kernel is now using squid2 repository directly. But had to use the osprey-stock_defconfig so that it boost.
aosp-caf-0.22.zip
Dual sim support (Couldn't test it since I don't have a dual sim Moto E 2015 phone, but on lux I can make some calls in dual sim)
Fix an issue with wifi bootloop after installing gapps (Can't really tell the trigger, but it's fixed )
I didn't have time to test this version on osprey nor surnia, so you can wait for me to test it or try it yourself and report any issue.
aosp-caf-0.21.zip
Rebased on LA.BR.1.26_rb1.3
OEM unlocked button is now correctly working
Broke video playing but restored it that's why number is much higher with so little changes
aosp-caf-0.16.zip
Video Recording
Change Language doesn't crash anymore when accessing to phone config (if I missed some languages please tell me I'll fix them too)
aosp-caf-0.14.zip
Actions (based on CMActions) + Added some actions from Victara phone
Added some commits for gapps package authentication, this should prevent a few errors but not fully working yet.
aosp-caf-0.12.zip
Sdcard mounting properly (didn't double check)
Sound working
Camera can now take pictures (recording not working)
aosp-caf-0.7.zip
Wlan
Sdcard
Init built from caf directly.
Updated APN so now Data is working.
aosp-caf-0.4.zip
Initial Version. Remember to flash the image-new-0.4.img (using fastboot) after flashing aosp-caf-0.4.zip

GG

Guys, you can try Gapps from: HERE

nice,

Do i need to boot or flash the "special" boot.img?

what is the fastboot command is it fastboot flash image-new-0.4.img?? help i just need the correct command because im not sure exactly what to type thanks..

fastboot flash boot image-new-0.4.img

i can confirm it boots and that's it..
but great work! hope you can fix the wifi soon!
thanks,
i have some screenshots to:
EDIT: lol my screenshots are on techdroider..
http://www.techdroider.com/2015/10/aosp-how-to-install-android-marshmallow-moto-g3-2015.html

madscientistdam said:
what is the fastboot command is it fastboot flash image-new-0.4.img?? help i just need the correct command because im not sure exactly what to type thanks..
Click to expand...
Click to collapse
I also did not understand ...... when the Rom will be fully functional will explain

This ROM isnt fully functional. If you want tot test this out flash the zip and then boot in to the bootloader and flash the boot img using 'fastboot flash boot #name of img#' than you can boot up. This ROM isnt for daily use.

Hey OP what is your github link?

What is the diference between caf and cm?

christopherrrg said:
Hey OP what is your github link?
Click to expand...
Click to collapse
https://github.com/boulzordev

squid2 said:
https://github.com/boulzordev
Click to expand...
Click to collapse
Wasn't sure if that was his, thanks!

Any updates yet?

is the any updates for this rom?

? guys..
No ETA.

if i'm not wrong, is see a cm-13 for osprey in the github of scritch.
can someone tell my about this or is it just nothing?

will squid2 kernel work on this rom?

[OFFICIAL][RECOVERY] TWRP 3.1.x for Samsung Galaxy Tab E [SM-T377P/SM-T560NU]

Code:
** Disclaimer
I am not responsible if flashing this recovery bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
Recovery Information
Recovery Target Device: Samsung Galaxy Tab E [ SM-T560NU | SM-T377P ]
Recovery Status: Stable
Recovery OS: TWRP 3.1.1-0
Maintainers: [ vince2678 ]
Project GitHub Repositories: https://github.com/TeamWin
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any recovery images!
Code:
[B]SM-T560NU[/B] - [COLOR="DarkSlateBlue"][B]gtelwifiue[/B][/COLOR]
[B]SM-T377P[/B] - [COLOR="DarkSlateBlue"][B]gtesqltespr[/B][/COLOR]
Click to expand...
Click to collapse
Download
Official Builds:
Code:
[B]SM-T560NU:[/B] [url]https://twrp.me/devices/gtelwifiue.html[/url]
[B]SM-T377P:[/B] [url]https://twrp.me/devices/gtesqltespr.html[/url]
Click to expand...
Click to collapse
Instructions
Installation using Odin
Installation using the App
Code:
* Download the Official TWRP App from the Play Store.
* Locate your device using the codename for your device.
* Download and flash TWRP (may require root).
Code:
* [B]Enable Developer Mode on your phone and unlock the bootloader from the
Settings, if not done already. [/B]
* Download a recent [B].tar[/B] archive from the links above for your device.
* Reboot into Download Mode [Press Power+Volume Down+Home].
* Flash the [I][B]tar[/B][/I] archive using ODIN by clicking [I][B]AP[/B][/I] and selecting
the [I][B].tar[/B][/I] file you just downloaded.
Click to expand...
Click to collapse
Changelog
Code:
[B][U]29/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated to 3.1.1-0.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Mouse cursor is now hidden from recovery screen.[/B]
Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] TWRP now has F2FS filesystem support [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] TWRP has USB OTG support integrated for external usb peripherals
(should work for vfat, exfat, ext4 or f2fs-format peripherals).[/B]
Code:
[B][U]07/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]gtelwifiue[/B][/COLOR]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Fixed reboot-to-system issue [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] adb shell now works [/B]
Code:
[B][U]07/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Build recovery image for SM-T560NU [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Create forum thread. [/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]gtelwifiue[/B][/COLOR]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] None [/B]
[COLOR="RoyalBlue"][B]gtesqltespr[/B][/COLOR]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Unknown. You tell me. [/B]
FAQ
Q: Are you taking device requests?
A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.
Click to expand...
Click to collapse
XDA:DevDB Information
[OFFICIAL][RECOVERY] TWRP 3.1.x for Samsung Galaxy Tab E [SM-T377P/SM-T560NU], Tool/Utility for the Android General
Contributors
vince2678
Version Information
Status: Stable
Created 2017-05-08
Last Updated 2017-06-21

I would like to know if compatible with model T560.

bira792 said:
I would like to know if compatible with model T560.
Click to expand...
Click to collapse
Nope.

Will this work on Galaxy Tab E SM-T560NZ?

deplorablemichael said:
Will this work on Galaxy Tab E SM-T560NZ?
Click to expand...
Click to collapse
If it's not a Qualcomm Snapdragon device, no, it will not work.

any way to do this if FRP is blocking it?

the TWRP versions linked in the OP doesn't work on my SM-T377P
I tried flashing both of the linked version 3's with Odin and Heimdall and all I get is boot loops. TWRP 2.8.7 installs fine using either method.
What else can I try?

mobilemischief said:
any way to do this if FRP is blocking it?[/QUOTE]
Go to developer settings and enable OEM unlock. Now try to flash it now. That's what I did. Also I had USB debugging on too.
Click to expand...
Click to collapse

The TWRP links are dead.
Any way someone could upload the t560 file?
Edit: NVM, just had to actually search for it. Thanks for pointing me in the right direction.

vince2678 said:
Nope.
Click to expand...
Click to collapse
Hi, I got SM-t377p with Nougat running, when I tired to flash these TWRPs it just boots back into System. I downloaded from here
https://dl.twrp.me/gtesqltespr/
I flashed this TWRP and it worked
https://androidfilehost.com/?fid=24385658843825618
its older model

[9] LineageOS 16.0 for z3c

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I 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.
*/
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Images
Here are some Screenshots of this ROM.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3 Compact
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Format data to get rid of encryption.
Install ROM.
Install 9.0 Gapps for ARM. **
* recommended TWRP: Post #2
** optional
Update:
Get the latest build
Boot into TWRP
Flash the downloaded build
Reboot, if you don't wipe system backuptool will handle to reapply your modifications, for example: GApps.
Changelog
Code:
Changelog 2019-10-07
* Fixed offmode charging at Wall chargers (previously bright screen)
* Fixed offmode charging at computers (previously reboot loop)
Old Changelogs
Code:
Changelog 2019-10-06
* Fixed camera for everyone
* Set media volume steps to 25 and voice call volume steps to 7
* Actually use our cache partition, previously we were using a link to /data/cache instead of mounting the cache partition as /cache
* Cleanup of rootdir scripts
Code:
Changelog 2019-08-28
* Rolled fingerprint back to Sony's 5.1.1 fingerprint
-> safetynet CTS check works again
* Set original shipping API level to KitKat
* Minor cleaning
Code:
Changelog 2019-08-14
* Singificantly improved GPS
* August Android Security Bulletin
* Cleaned, script generated vendor
Code:
Changelog 2019-08-05
* Attempt to fix ANT+
* Added settings to control the camera button
Code:
Changelog 2019-07-08
* July Android Security Bulletin
* Rebased Linux 3.4.113 Kernel
-> Solved video recording lags with Snap
Code:
Changelog 2019-06-15
* Fixed Audio problems
* LED Notifications work again
* Manual Network selection fixed
Code:
Changelog 2019-06-07
* June Android security Bulletin
* LED seems to work with notifications now
* 4.0 Audio HAL -> NO, this does NOT fix our problems :/
Code:
Changelog 2019-05-10
* Enforcing sepolicy
* Fixed sensors
* Fixed FM Radio
* Fixed EXFat, sdfat and vfat
* Camera works fine
* May Android Security Bulletin
* Sound seems fixed - Maximum Volume still decreases still after a few seconds when using internal speakers
Code:
Changelog 2019-05-06
* Fixed AudioFX
* Fixed Camera
Code:
Changelog 2019-04-24
* Fixed Notification LED
Code:
Changelog 2019-02-19
* Fixed GPS
* Fixed Video Playback
Code:
Changelog 2019-01-09
* Fixed Bluetooth
Downloads
Download the ROM
Sources
DEVICE:
https://github.com/z3c-pie/device_sony_z3c
https://github.com/z3c-pie/device_sony_msm8974-common
https://github.com/z3c-pie/device_sony_shinano-common
KERNEL:
https://github.com/z3c-pie/kernel_sony_msm8974
Addons
OpenGapps
Magisk
SU-Addon
Thanks
Whole LineageOS Team for this amazing ROM
@rcstar6696
@Myself5
@drakonizer
@tomascus
@koron393
@nailyk
@SpiritCroc
I hope I haven't forgot anyone
Bugs
WHAT'S BROKEN
4K Video recording doesn't work in stock camera, but works for example in OpenCamera.
You tell me.
FAQ
Q: Why i can't reboot into the recovery from advanced reboot?
A: Because you have installed Magisk 19.1 which breaks it. Keep up to date here: https://github.com/topjohnwu/Magisk/issues/1418 - fixed by @Myself5 since 2019.05.20
XDA:DevDB Information
[9] LineageOS 16.0 for z3c, ROM for the Sony Xperia Z3 Compact
Contributors
NeoArian
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: lineage-16-20190510
Stable Release Date: 2019-05-10
Created 2019-01-05
Last Updated 2019-10-10

TWRP 3.3.1 for our z3c out of an Android 9.0 environment!
Changes:
Code:
3.3.1-0.4-z3c
* Fixed fastboot boot
* Added bootlogo
* Dropped TWRP App
Code:
3.3.1-0.3-z3c
* Fixed encryption when security patch level doesn't match the recovery's
- [url]https://github.com/z3c-pie/twrp_device_sony_z3c/commit/411862532c247aea2c7b48d52aa596b40305e9ea[/url]
Code:
3.3.1-0.2-z3c
* Added a script to handle the CPU
-> increased the battery life significant ([url]https://github.com/z3c-pie/twrp_device_sony_z3c/commit/63f864068ad2f17ae2f1202b4edc311d74e2803d[/url])
Code:
3.3.1-0.1-z3c
* Fixed time
* Further Clean up's
Code:
3.3.1-0-z3c
* Switched from Android 6.0 to Android 9.0 environment
* Completely reworked tree
* Working decryption
The latest build is attached to this post.
Old builds are available here: https://sourceforge.net/projects/ephedraceae/files/z3c/twrp/
Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-9.0
How to install this build:
Rename the downloaded twrp image to twrp.img
Reboot to fastboot by holding volume up while connecting your device to your computer
Open a terminal and move to the directory with TWRP in it
Type
Code:
fastboot flash recovery twrp.img
Boot into TWRP while the device is powered off press the power and volume down button
Feel free to ask questions or give feedback about TWRP here .
Have a nice day!
Additional information about the recovery on this device:
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse

Reserved

Hi, I can't open your thread in XDA Labs app, I suppose that's the case of many people and that's why there is not much views and comments on this thread.
I didn't tried yet your ROM but it sound great and will try it ASAP.
Also which recovery do you recommend to avoid errors like error 7 (if I remember) ?
Also will you continue to work on RR ?
EDIT : after posting this comment via browser, I can now open this thread in XDA Labs
EDIT 2 : everything is working

SUPER KOKA said:
Hi, I can't open your thread in XDA Labs app, I suppose that's the case of many people and that's why there is not much views and comments on this thread.
I didn't tried yet your ROM but it sound great and will try it ASAP.
Also which recovery do you recommend to avoid errors like error 7 (if I remember) ?
Also will you continue to work on RR ?
EDIT : after posting this comment via browser, I can now open this thread in XDA Labs
Click to expand...
Click to collapse
I use twrp-3.2.3 from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192.
I don't know yet about RR. I wanna see first whether we can get Bluetooth and gps working as soon as possible.

https://sourceforge.net/projects/ep...age-16.0-20190109-UNOFFICIAL-z3c.zip/download
Another build was uploaded with the latest lineageos updates including the January android security bulletin. On the device side Bluetooth was fixed

Installed without any problems
You did a great job!
Installed without any problems. It seems all functions work fine!

update
I've been in lineage, whether for the latest version update I have to hard reset or like the ota update

SUPER KOKA said:
EDIT 2 : everything is working
Click to expand...
Click to collapse
Great to hear!
CDLion said:
You did a great job!
Installed without any problems. It seems all functions work fine!
Click to expand...
Click to collapse
Thanks!
muhibbuddin irsyad said:
I've been in lineage, whether for the latest version update I have to hard reset or like the ota update
Click to expand...
Click to collapse
To be honestly I can't follow you. Do you mean that you don't know how to update the build? For this case you have to download manually and flash it in TWRP. There are no wipes needed.

Hi, thanks for this and how is the battery performance?

Any plans for making an LineageOS for microG rom?

Thanks for the ROM, I am using it right now, everything is working good except the camera. Can take photos, but video is not working. When I'm switching to video, the app is freezing and stuck. I tried to use the stock camera with magisk, it can't take photos or video neither. Tried manual camera too, it can take photos but no video.

etram said:
WOW ... !!!
Great Job.
What about the notification LED?
Click to expand...
Click to collapse
Just tested shortly, it seems to be broken, I will add to broken things list. Thanks to notify (?)

I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log

frht5382 said:
I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log
Click to expand...
Click to collapse
I try and I install 20180105 build but I cant install new build why ?
twrp 255 error

frht5382 said:
I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log
Click to expand...
Click to collapse
frht5382 said:
I try and I install 20180105 build but I cant install new build why ?
twrp 255 error
Click to expand...
Click to collapse
Are you sure that you use the recovery from here?
https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192

NeoArian said:
Are you both sure that you use the recovery from here?
https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192
Click to expand...
Click to collapse
Solved.I dowloaded false file which 632 mb.Now I re download true file and it work thank you

frht5382 said:
Yes I am sure.I install 2019 01 05 build it work but I try 20190109 fail everytime error code 255
edit
I've just realized I clik download button and if I download latest version green color button I download 631 mb but down of button lineage-16.0-20190109-UNOFFICIAL-z3c.zip 448 mb which one should I download ?
why different size ?
Click to expand...
Click to collapse
The 631mb Rom is for my Xiaomi Mi 6, you have to use the one for z3c

NeoArian said:
Tue 631mb Rom is for my Xiaomi Mi 6, you have to use the one for z3c
Click to expand...
Click to collapse
I installed thank you .How to enable root access? Or magisk work ?

frht5382 said:
I installed thank you .How to enable root access? Or magisk work ?
Click to expand...
Click to collapse
Magisk works.

[ROM][Official][Nightly] LineageOS 17.1 for OnePlus 3/3T

LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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 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.
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. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 17.1 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We 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
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 17.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.4+ is highly recommended: https://dl.twrp.me/oneplus3/)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Changelog:
2019.10.24
Initial release
2019.10.25
Sync latest source
Fix bluetooth
2019.11.20
Sync latest source
Fix wifi display
Ship Snap
Fix vulkan graphics
Pass safetynet
Fix crash of some native services
2019.12.31
Sync latest source
SELiunx working in enforcing mode now
Update kernel to LA.UM.8.6.r1-02900-89xx.0
Update blobs from OOS 9.0.6
Fix suspend when AOD is on
Happy new year!
2020.1.12
Sync latest source
Fix ril of the last build
Update blobs from LA.UM.8.6.r1-02900-89xx.0
Add backuptools
Other trivial fixes
2020.4.2
Official nightlies started
Download:
https://download.lineageos.org/oneplus3
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao
ROM OS Version: Android 10
Version Information
Status: Nightly
Created 2019-10-24
Last Updated 2020-06-26

Any recommendations which gapps to use?

Why not the official ones? https://sourceforge.net/projects/opengapps/files/arm64/beta/20191006/

is this with kernel 4.4?

helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
https://github.com/LineageOS/android_kernel_oneplus_msm8996/blob/lineage-17.0/Makefile#L1-L3

helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...

dianlujitao said:
Important information:
This thread is for LineageOS 16.0 builds for OnePlus 3/3T.
Click to expand...
Click to collapse
OP needs some changes its for LOS 17 instead of 16 [emoji3][emoji39]
Sent from my ONEPLUS A3003 using Tapatalk

Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.

Master_TC said:
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...
Click to expand...
Click to collapse
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
mady51 said:
ya i built it once but it didn't booted. after that didn't spent time on it. may be ill give it another try soon
Click to expand...
Click to collapse
Anyway amazing work @dianlujitao you're one of our heroes ???

Viper The Ripper said:
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
Anyway amazing work @dianlujitao you're one of our heroes ???
Click to expand...
Click to collapse
https://github.com/dianlujitao/android_kernel_oneplus_msm8996 @dianlujitao did bring up a 4.4 kernel but it has issues.

Jus asked because of this

mvalda01 said:
Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.
Click to expand...
Click to collapse
Can you provide more info such as logs, my aptx headset works fine here.

Thanks for the effort,nice rom for nice phone.
From Op3 owner

Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks for the report, bluetooth should be fixed in 1025 build, for Digital Wellbeing crash you should probably report to opengapps devs, I'm not sure.
NFC works fine for me, it wound be nice if you could grab related logs.

Well done @dianlujitao!

Thanks for your work @dianlujitao! I'll probably flash next build

@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.

MJPollard said:
@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.
Click to expand...
Click to collapse
You need to pick - at least - https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/255737 from https://review.lineageos.org/q/project:LineageOS%2Fandroid_device_oneplus_oneplus3+status:open, maybe all.
There's a good reason why OP calls it an experimental build instead of alpha or beta... Rebuilding experimental needs skilld and patience...
EDIT:
For the blobs commits (i.e. https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/260573 and https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/262330) see also https://github.com/dianlujitao/proprietary_vendor_oneplus/commits/lineage-17.0 .

BillGoss said:
- Digital Wellbeing keeps stopping (logs attached)
Click to expand...
Click to collapse
On some other Android 10 ROM, force stopping, disabling and then re-enabling solved this issue.

Database Info

welcome