LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Unofficial LineageOS Builds
Pixel XL (marlin): https://updater.invisiblek.org/marlin
Pixel (sailfish): https://updater.invisiblek.org/sailfish
Google apps
Google apps (opengapps nano) are baked in to these builds. This is due to the A/B partition layout and complications backing up/restoring gapps between builds. This is not ideal, and is the major road block to getting this device in to official status with Lineage. I also include the Google camera app rather than Camera2 or Snap since it works much better.
Source
While I update the official LineageOS trees with completely usable source, these builds include a few more experimental things than what I would include in official Lineage builds, pending that ever happens. The device and kernel repos that these builds are based off are from my github.
Installation
The easiest way to install LineageOS is to load up twrp (see twrp thread on how to do that) and flash the zip from above for your pixel variant (marlin/sailfish). After that, the built-in updater app should handle future updates via A/B updates within android. Beware this feature is still a work in progress and can be broken at any time as well. If for whatever reason the install fails through the updater app, loading up twrp again and flashing a newer zip is perfectly acceptable.
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][UNOFFICIAL] LineageOS 14.1 Nightlies for the Google Pixel (marlin/sailfish), ROM for the Google Pixel XL
Contributors
invisiblek
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
Version Information
Status: Testing
Created 2017-05-05
Last Updated 2017-05-05
How come gapps are still baked in when there are working gapps for pixel? Beans gapps works fine.
Glad to see this finally getting an XDA thread so it gets more awareness. I only knew this existed prior due to the questions and answers thread.
I know OP says it comes with nano gapps. But does that mean that it has all the essential pixel gapps. I can't find myself using the also ones. I wish there was a flashable stock gapps package
TheNewNEXUS said:
I know OP says it comes with nano gapps. But does that mean that it has all the essential pixel gapps. I can't find myself using the also ones. I wish there was a flashable stock gapps package
Click to expand...
Click to collapse
You can't flash beans full gapps? Actually it will probably just have duplicates since gapps are already installed
Having issues with youtube. Is anyone having issues?
pcriz said:
You can't flash beans full gapps? Actually it will probably just have duplicates since gapps are already installed
Click to expand...
Click to collapse
That is correct. However, the there are still those aosp apps that don't hold a candle to the Google alternatives. I am super used to flashing the stock Google package on all my phones. I guess I will just stay on stock May Factory Image until I find one with all pixel features. Lineage OS is one of the most stable ROMs that I have came across.
TheNewNEXUS said:
That is correct. However, the there are still those aosp apps that don't hold a candle to the Google alternatives. I am super used to flashing the stock Google package on all my phones. I guess I will just stay on stock May Factory Image until I find one with all pixel features. Lineage OS is one of the most stable ROMs that I have came across.
Click to expand...
Click to collapse
What apps are you looking for that can't just be downloaded from the play store? Any of the AOSP ones can be disabled, so you never see them (yea a bit of a pain but you only have to do it once per app that you replace from the play store). For instance, I install google's calendar app and disable the AOSP one. You can do the same with any other app as far as I know.
invisiblek said:
What apps are you looking for that can't just be downloaded from the play store? Any of the AOSP ones can be disabled, so you never see them (yea a bit of a pain but you only have to do it once per app that you replace from the play store). For instance, I install google's calendar app and disable the AOSP one. You can do the same with any other app as far as I know.
Click to expand...
Click to collapse
All apps are on the Play Store. I will end up disabling them I guess
invisiblek said:
What apps are you looking for that can't just be downloaded from the play store? Any of the AOSP ones can be disabled, so you never see them (yea a bit of a pain but you only have to do it once per app that you replace from the play store). For instance, I install google's calendar app and disable the AOSP one. You can do the same with any other app as far as I know.
Click to expand...
Click to collapse
That's what I do. Then things stay put when you flash an update. If you delete the app it will come back when you flash an update.
Cool beans and good to see you again invis (I've also had tenderloin, d2vzw and vs985 so you've kind of been following me around). How's the general status of the build? Any known breakages?
And btw, the changelog links on the download page don't go anywhere.
Doesn't boot for me. 15 minutes at the boot animation and all that's happened so far is that my phone is hot. Installed 20170506 over NHG47L.
Edit: ah you need to be on N2G47O.
So this is the May O build. It's been said all over the forums but just to nip it in the bud here, don't go trying to flash a different kernel that isn't signed or use Chainfire's zip to sign the kernel, otherwise you'll get stuck in a boot loop. The May bootloader update made it so it won't boot with an unsigned boot image.
@invisblek Great to see you here I've always been a big fan of your work unfortunately I haven't had a device for several years where you were making ROMs for. I'm generally not a fan of lineage but will give this a try just because you built it.
I noticed in the kernels git that you have WALT enabled across the board, but the official spec is to use PELT with EAS - new for rev 1.2. did you have a reason for choosing Walt? It isn't a big deal anyway, assuming the properties are exposed users can use ex kernel manager to turn Wall off and turn Pelt on.
Also 8 branches, 6 active you've been busy! I take it the default 14.1 branch is the kernel used in this ROM? I see all sorts of new stuff across your code and am very thankful you've came over to pixel development.
A side note in regards to build to Verizon users:. I flash the modem and radio from the L build as its May's Verizon only and I don't nearly have as many problems with signal retention. It didn't completely fix the problem but it's definitely been improved. and when I say retention I mean I'll be at the same location and my pixel will suddenly lose signal completely for a random period of time and then go back to having a signal. This used to occur very often the phone would be intolerable without Wi-Fi calling but the L build which specifies it's Verizon only must have had some changes in it to improve this.
Looking forward to trying your work. Thanks for your time and effort!
I don't use either so it doesn't matter to me, but I noticed that LiveDisplay and Color Calibration do not work at all. Neither change the screen color when you adjust them. I'm on the May 5th build right now.
@invisiblek just a heads up. I flashed today's build and Google Camera video recording at 30FPS crashes. "Camera error".
I've posted the logcat before, let me know if you still need one.
It was a full wipe including internal SD, just FYI.
I didn't install any apps or superuser. I booted up for first time and immediately tested Google Camera.
CZ Eddie said:
@invisiblek just a heads up. I flashed today's build and Google Camera video recording at 30FPS crashes. "Camera error".
I've posted the logcat before, let me know if you still need one.
It was a full wipe including internal SD, just FYI.
I didn't install any apps or superuser. I booted up for first time and immediately tested Google Camera.
Click to expand...
Click to collapse
He's already aware of it and I believe he already pushed the fix for it, I just don't think it's been merged. It's something to do with ffmpeg.
Been running or a few days now, everything is good except that the updater doesn't work. It detects updates, clicking the Download button goes to Downloading state, then Downloaded, and the Install button shows up; clicking Install goes to Installing state for a little while then back to Downloaded, and clicking Install again gives a message "an update is already in progress", and the update never completes.
I'm interested in doing my own builds for my Pixel XL, for some stuff I want to test but I'm wondering if you can tell me which SafetyNet patch you're including and what you're including to enable the blue Pixel theme and Pixel navbar.
So, I've been running the ROM for over 3 days now and I've got to say that it has been great so far. Currently using 20170508 right now, and it's all good.
Have disabled all the AOSP apps and have installed all the Google apps from the Play Store to replace them. Everything is almost the way it is on stock.
Had to install the live data wallpapers, and install the Pixel launcher as a system app to get the Now feed integration, but so far it's been like stock but with all the extra features I've wanted. Even installed the AptX codecs, and my phone still passes SafetyNet.
So far the only downsides I've seen are that Google Camera crashes upon taking a second video, haven't gotten WiFi assistant to work yet, and my phone gets a bit toasty playing music but I'm pretty sure that it is GPM being stupid again and not the ROM. But overall it has been an excellent experience.
hobbified said:
Been running or a few days now, everything is good except that the updater doesn't work. It detects updates, clicking the Download button goes to Downloading state, then Downloaded, and the Install button shows up; clicking Install goes to Installing state for a little while then back to Downloaded, and clicking Install again gives a message "an update is already in progress", and the update never completes.
Click to expand...
Click to collapse
The updater has worked just fine for me, taking me from 20170506 to 07 without TWRP installed and from 07 to 08 when I had TWRP installed. Don't if 08 to 09 is broken right now so I need to test.
admiralspeedy said:
He's already aware of it and I believe he already pushed the fix for it, I just don't think it's been merged. It's something to do with ffmpeg.
Click to expand...
Click to collapse
Yes, I was aware of that "fix". And it's already merged.
But it does not work.
Google Camera 30fps video still crashes.
I was just letting him know the fix he was told about does not work.
The fix being to remove FFMPEG from /system/etc/media_codecs.
I even tried deleting the media_FFMPG file and duplicating at /system_root/etc/.
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KK), which is designed to increase performance and reliability over stock Android for your device.
------------THIS IS AN UNOFFICIAL UNSUPPORTED BUILD-----------
This is my attempt at porting CyanogenMod 11 to the Galaxy Tab 4 10.1. I use a SM-T530NU, so that is the only device I have tested.
Any other device variations have not been tested and are at your own risk. I will not be able to support other variations as I don't own them for testing.
Special thanks to MetaIIica - I have been using his Alpha build of PAC-ROM KitKat since December. I studied the code for that, along with stock and some other ROMs before starting this port. This is my first time doing any work with Android, so I'm not sure if I'm technically doing things correctly or not.
I know CyanogenMod 12 is under development already, but I have decided to do a CM11 based build in hopes of a making a stable daily driver offering. I have fixed many of the issues present that were present in the PAC-ROM build. They can probably be backported to PAC-ROM easily if its built with my tree, but I prefer the plain CM-based offering myself.
You may get the source of my changes for this ROM on my github. If you'd like to help and submit a patch, feel free to open a pull request. You will of course be credited accordingly.
See below for instructions, what's working, and issues I fixed over the PAC-ROM Alpha.
For any bug reports or feature requests, please use the appropriate tabs at the top of the thread. Please include as much information as possible and if possible a logcat or other debug information in the case of bugs. Requests for supporting other device variations will not be honored - sorry,
Feedback and constructive criticism is always appreciated. I hope you enjoy using the ROM; if you use the ROM, please consider leaving a thanks, rating, and/or review
CURRENT VERSION:
DOWNLOAD LINK - 04/26/2015
OLD VERSIONS:
DOWNLOAD LINK - 04/20/2015
DOWNLOAD LINK - 04/19/2015
DOWNLOAD LINK - 04/07/2015
DOWNLOAD LINK - 04/05/2015
DOWNLOAD LINK - 04/04/2015
DOWNLOAD LINK - 04/03/2015
DOWNLOAD LINK - 03/29/2015
DOWNLOAD LINK - 03/24/2015
DOWNLOAD LINK - 03/23/2015
DOWNLOAD LINK - 03/22/2015
INSTRUCTIONS
- Install PhilZ Touch Recovery (recommended)
- Copy CM11 & GAPPS (Optional) ZIPs to your SDCard
- Boot into Recovery
- Do "Clean to Install a New ROM" (FULL WIPE REQUIRED INCLUDING SYSTEM, NOT JUST DATA/CACHE - even if coming from another CM-based ROM, as my device tree is different)
- Flash CM11 ZIP
- Flash GApps zip from SDCard
- Reboot
UPGRADING
-In general, you should be able to just flash over the previous build, but if you encounter any weird issues please clean using the steps above
Working that I've tested:
Audio: Speakers, Headphones, Bluetooth
Bluetooth
CIFS/NFS (Network File Systems - see notes below)
Front Camera
GPS
IR Blaster [SM-T530NU Only]
Magnetic Cover Sleep/Wake
MTP
Rear Camera
USB OTG
Video (w/ Hardware Decoding)
WiFi (2.4ghz & 5ghz)
NOTE ON BUTTONS: This ROM is configured to use the hardware buttons-- so you won't see the software buttons taking up space at the bottom of the screen, as they are disabled. This is not a bug. Use the hardware buttons, as they are the same. If you really want the software buttons for some reason, edit /system/build.prop, change qemu.hw.mainkeys to 0, save, and reboot. If you map the menu button to a long press of another button, some apps such as TitaniumBackup will count this as a hardware key and hide their soft menu button - but only after a reboot.
NOTE ON CIFS/NFS: Many of the mounting utilities on the play store are outdated and broken due to changes in the linux kernel. For best luck, mount using the command line. For CIFS, you can tweak CIFSManager into working - see this thread
CHANGELOG:
[04/26/2015]
-Fix reading MAC address from EFS
-Fix suspending charging while the device is off (special thanks to @sub77 for pointing out the right config option)
[04/20/2015]
-Enable physical keyboard menu for use with BT/USB keyboards. Auto hides soft keyboard & allows selection of layout.
[04/19/2015]
-Add support for magnetic cover sleep/wake
[04/07/2015]
-Roll back to using the Non-CAF Display HAL Fixes SurfaceFlinger constantly eating 100% CPU
[04/05/2015]
-Fix issues with reconnecting Bluetooth Devices after a reboot (if upgrading, break pairing and re-pair all devices)
-Fix mounting /efs
-Fix persistant Bluetooth MAC Address
[04/04/2015]
-Fix issues with detecting whether or not the device has a hardware menu button.
[04/03/2015]
-Fix the Time Service, allowing Date & Time to persist during a reboot without a wifi connection. Special Thanks: sub77 for pointing the discussion in the thread in the right direciton on this
[03/29/2015]
-Support Bluetooth Audio & AVRCP
-Support Consumer IR [SM-T530NU Only]
-Upgrade Display HAL to CAF Version
-Misc Bugfixes and Cleanup
[03/24/2015]
-Fix Missing Sensors HAL (Fixes Autorotate regression from the last build)
-Behind the scenes work for IR (need someone to test on plain 530 as IR is NU only). Does not actually work yet because its using the stub HAL, but the kernel drivers are loaded, and the IR service runs.
[03/23/2015]
-Fix lighting issues with rear camera
-Reduce some dependencies on vendor libs.
[03/22/2015]
-Added support for Front/Back Camera
-Added support CIFS/NFS
-Fixed 5 ghz WiFi
-Fixed Duplicate VSYNC spam in logcat
-Fixed issues with video decoding (YouTube HD, MXPlayer HW+ Video, etc)
-Fixed various Bluetooth issues
-Fixed wallpaper issues with Trebuchet
-Identify device correctly as MSM8226 chipset
-Use Hardware Buttons by Default
XDA:DevDB Information
CyanogenMod 11 Unofficial [TM-530NU], ROM for the Samsung Galaxy Tab 4
Contributors
starlightknight
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2015-03-29
Beta Release Date: 2015-03-22
Created 2015-03-29
Last Updated 2015-04-25
Congratulations ! :good:
Nice ROM, it installed fine on my T530 will test some more, thanks for the hard work
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Time for a new test, i'll test it in my t530 and report back the results.
Sent from my GT-I9300 using XDA Free mobile app
steve30x said:
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Click to expand...
Click to collapse
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
starlightknight said:
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
Click to expand...
Click to collapse
I always completely wipe everything before installing a new rom. Never wiping the tablet before installing a new rom might cause problems. I no longer have the rom installed. I will install it again and see if it was just a flike that it didnt work properly the last time. I also have Philz recovery installed because its the only one that has full brightness on the screen.
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! Glad to hear that it is working well for you. I believe the only difference between the SM-T530 and the SM-T530NU is the the NU has an IR blaster, which I haven't actually enabled yet. I need to figure out how to test that because I never use it. After i do that and post a build with IR, it will be useful if you check and make sure it doesn't break the regular 530. Those two from what I can tell are vary similar, its more of any celluar varients that I would be worried about, because this is build for wifi only..
Let me know if you find anything broken
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
steve30x said:
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
Click to expand...
Click to collapse
Glad its working for you now
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
starlightknight said:
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Click to expand...
Click to collapse
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
starlightknight said:
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
Click to expand...
Click to collapse
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Gustave17 said:
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Click to expand...
Click to collapse
The GAPPS package I modded is only 76MB. Its just the bare essentials
steve30x said:
The GAPPS package I modded is only 76MB. Its just the bare essentials
Click to expand...
Click to collapse
Oh ok, so it's what we need...
Y
steve30x said:
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Click to expand...
Click to collapse
I used an aroma based gapps. You can install only what you need. About using YouTube without gapps, i dont know if tubemate could do the trick. Use aptoide to install it if you dont like play store. Here is the link for the aroma gapps: http://forum.xda-developers.com/showthread.php?t=2547250
Sent from my GT-I9300 using XDA Free mobile app
---------- Post added at 11:01 PM ---------- Previous post was at 10:45 PM ----------
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Click to expand...
Click to collapse
It has something to do with the lighting detection or some other initial initialization that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
starlightknight said:
It has something to do with the lighting detection that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
Click to expand...
Click to collapse
Tested and working fine. Is a nice workaround. I dont mind about this bug as I only use front camera for Skype and such things, but im glad this workaround is pretty easy and fast
Sent from my GT-I9300 using XDA Free mobile app
Hi Everyone,
I updated the original post with a new build. This build should fix the lighting issues with the rear camera the first time it is used. After I debugged the mode switching with logcat I was able to find out what the issue was. I also am working on reducing dependencies on vendor libs where possible by getting more of the modules that can be built from source building from source.
I've started exploring IR blaster support for NU users and I am continuing to look for a solution for bluetooth audio, but I don't have either yet. Stay tuned for future updates
If you already installed the ROM most times you should be able to flash over it, but if you see anything weird after, try wiping to confirm if its a bug or weirdness after upgrading (you can always nandroid before wiping if you're unsure and roll back if its not related to upgrading).
Please let me know if you find any issues. Include model number and if possible a logcat as well.
Enjoy!
Congrats starlightknight!
Anyone tried this on the SM-T530?
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), 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). LineageOSdoes still include various hardware-specific code, which is also slowly being open-sourced anyway.
Important information:
This thread is for Unofficial LineageOS 13.0 builds for v2awifi (SM-T900). The following will not be supported here:
Custom kernels
Mods
Xposed
Do not ask for ETAs. If you do, I will ignore you and your post.
SEANDROID ERROR
If you see a message at boot about Recovery or Kernel is not SEANDROID Enforcing, you can ignore it. This is just telling you that you are not running Samsung stock software. It has no effect on recovery or the ROM itself nor related to either.
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Bootloader Information
You need to make sure you have a Lollipop bootloader installed or else your device won't boot. Here you can go grab the latest bootloader and odin and flash it in download mode. Read all the steps before you do this.
Make sure you have a full backup because just in case you something fails.
Here are the steps to flash this via ODIN:
Make sure you have a full backup because just in case you something fails. Here are the steps to flash this via ODIN.
Reboot your tablet into download mode. Do this by first switching off the phone, then pressing and holding the volume down + home button together and then pressing the power button. Press volume up button to enter download mode.
Open ODIN on your computer. You?ll see the ID:COM box turning yellow with a COM port number upon successful connection with the tablet.
In ODIN click the BL button, select the bootloader firmware. It's a tar file.
Make sure Auto Reboot & F. Reset Time options are selected in ODIN
Click on the start button. When the process is completed your phone will reboot.
Installation
Download the zip(s)
Install a compatible Recovery (This will not work with the P900 recovery)
--1.*I have built a new version of TWRP with the MM kernel. MTP, Vibations, ADB now work and there are performance increases. The rom will need to allow v2awifi naming for flashing in recovery. Link
Perform a nandroid backup of your current ROM (optional)
Wipe data/factory reset
Flash LineageOS
Install the Google Apps addon package (Optional)
Reboot
Issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs or it didn't happen! You can use this: Syslog App
Downloads
Nightlies
Latest Nightly Date 12/23/16
Device Builds
Google Apps
http://opengapps.org/ - Thanks to the OpenGapps team!
Issues
Lower than stock audio volumes
MHL out to TV not working
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging, & documentation.
Source:
Kernel: Link
Device Tree: Link
Credits
@Valera1978 Initial device tree
@UpInTheAir for his kernel magic and misc fixes
@chhaggerty, @tbjr50 and @titidu3701 for their testing efforts
Exynos5420 Dev Team ( @deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin, @javelinanddart )
XDA: DevDB Information
[6.0.x|SM-T900| Unofficial LineageOS 13.0 (v2awifi), ROM for the Samsung Galaxy Tab Pro 12.2
Version Information
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Status: Stable
Created 2016-10-01
Last Updated 2016 -12-23
Kernel Info:
M Kernel base from the Galaxy Tab S
M GPU driver from Galaxy Tab S
CPU Voltage Control
CPU OverClock/UnderClock (Up to 2.1GHZ)
MIF/INT Voltage Control
UKSM instead of KSM
Added the following IO Schedulers: fifo, fiops, sioplus, tripndroid, vr, zen, bfq (Default)
Full f2fs support updated off the mainline (Stock cm kernel has limited support)
Modified Thermal Throttling temperatures for all devices so hopefully they won't get as hot
Exynos thermal exposed to sysfs
Android Logger disabled by default can be enabled over sysfs
WQ power efficient workqueues (Still need to apply in more places)
Frandom Support
Readahead bumped to 256 from 128
Currently Disabled:
GPU Voltage Control/GPU OverClock/UnderClock (Needs to be rewritten for the M driver)
Awesome!
Thank you very much Tom!
Thank you! I would like to report that vibration isn't working. Other than that, everything works great.
c19932 said:
Thank you! I would like to report that vibration isn't working. Other than that, everything works great.
Click to expand...
Click to collapse
I will look into this. I am fairly confident I know what the fix is. Thanks for the feedback.
Hmmm...
I did wipe cache/dalvik cache/system and data with TWRP 2.8.7.0
and installed your cm-13.0-20161001-UNOFFICIAL-v2awifi.zip along with the open_gapps-arm-6.0-pico-20160925.zip (which I got as .ZIP for/from my Nexus 10)
After installing wiping cache/dalvik cache again and reboot system - but then after the SM-T900 Logo the screen is only blank.
No boot animation and no other sign that it will do something.
I could go to TWRP via Power+VolUp+Menue....
Do you got an Idea what went wrong?
[EDIT] also only the cm-13.0-20161001-UNOFFICIAL-v2awifi.zip without Open GApps gives me a black screen.
For now Iam back on CM 12.1 from the 09.07. and pico Open GApps from today.
Why was the SM-T900 files formerly named v2wifixx and now v2awifi? Could this be a problem for me?
guidol, try updating your bootloader, as per the OP.
TP, thanks much for your work on Tab/Note Pro 12.2.
gorgthetroll said:
guidol, try updating your bootloader, as per the OP.
TP, thanks much for your work on Tab/Note Pro 12.2.
Click to expand...
Click to collapse
How to do that? I have the same issue. Thnx
gorgthetroll said:
guidol, try updating your bootloader, as per the OP.
Click to expand...
Click to collapse
Thanks @gorgthetroll
Now it works - didnt read the part before the installtion carefully enough
@kutzman: read the part above the part of the installtion instruction:
Bootloader Information
You need to make sure you have a Lollipop bootloader installed or else your device won't boot.
I did this Bootloader-Part with Odin (Ok, on my device I has it to fo 2 times and 2 times it told me OK, but it did boot with a read Message about the Kernel in the 2nd try.
Now - after the seond try of the BootLoader-Flash my SM-T900 did boot - so I updated the TWRP via Flashify to the latest version (3.0.2.0) - but for that you have to enable root access in the developer options of CM13
thompatry said:
I will look into this. I am fairly confident I know what the fix is. Thanks for the feedback.
Click to expand...
Click to collapse
Does look great the first version of the CM13 for the SM-T900 :good:
Sadly I can confirm the missing vibration.
But as I did promise you - I donated another $30 for the "working" version of CM13 :laugh:
I hope this will encourage your development on the SM-T900-Builds! :angel:
guidol said:
Does look great the first version of the CM13 for the SM-T900 :good:
Sadly I can confirm the missing vibration.
But as I did promise you - I donated another $30 for the "working" version of CM13 :laugh:
I hope this will encourage your development on the SM-T900-Builds! :angel:
Click to expand...
Click to collapse
Thanks a lot to Guidol for being the most generous "facilitator", helping keep our great Tom in great spirit
Glad to see this rom!
Thank you for a working MM build for this amazing tablet, which I lost hope for any development. I appreciate all the hard work you put into getting this working!
I am having issues with the Play Store hanging at times and the File Manager not showing up properly and slowing down the device significantly
Getting a lot of issues regarding "Package Installer"
No Xposed installed*
Edit: tried multiple file managers from the Play Store and each have problems. No way to view files
Neekeet said:
Glad to see this rom!
Thank you for a working MM build for this amazing tablet, which I lost hope for any development. I appreciate all the hard work you put into getting this working!
I am having issues with the Play Store hanging at times and the File Manager not showing up properly and slowing down the device significantly
Getting a lot of issues regarding "Package Installer"
No Xposed installed*
Edit: tried multiple file managers from the Play Store and each have problems. No way to view files
Click to expand...
Click to collapse
Make sure you did a clean install, as mentioned in the OP's original message, and use an up-to-date OpenGapps package (for ARM, 6.0).
Thanks,
Eric
vochong said:
Make sure you did a clean install, as mentioned in the OP's original message, and use an up-to-date OpenGapps package (for ARM, 6.0).
Thanks,
Eric
Click to expand...
Click to collapse
Thanks for the reply
I have a clean installation and the exact same Gapps package installed.
Going to reflash and see keep an eye out for better results
Anyone else notice their tablet getting really hot? near the camera front and back.
Edit: Just reflashed using the Nano Gapps package and everything seems to be working great! will update if i run into anything. I had issues using the Pico version and wonder if that is suspect to the issues I was having. Any ideas?
Neekeet said:
Thanks for the reply
I have a clean installation and the exact same Gapps package installed.
Going to reflash and see keep an eye out for better results
Anyone else notice their tablet getting really hot? near the camera front and back.
Edit: Just reflashed using the Nano Gapps package and everything seems to be working great! will update if i run into anything. I had issues using the Pico version and wonder if that is suspect to the issues I was having. Any ideas?
Click to expand...
Click to collapse
Since the system partition in SM-T900 is quite large, I've always installed the STOCK package so it would remove most of the built-in stock/AOSP apps/tools and replace them with Google ones.
Also, with the STOCK package, I can still have access to useful Google apps even after a configuration reset, and without Google login (to download apps from Google PlayStore.)
Thanks,
Eric
Neekeet said:
Edit: tried multiple file managers from the Play Store and each have problems. No way to view files
Click to expand...
Click to collapse
I didnt got a problem with the EFS Explorer.
But for some access-methods you have to grant access-rights if the app/CM13 did ask.
And I got root-access enabled in the developer options.
---------- Post added at 06:25 PM ---------- Previous post was at 06:16 PM ----------
Neekeet said:
Edit: Just reflashed using the Nano Gapps package and everything seems to be working great! will update if i run into anything. I had issues using the Pico version and wonder if that is suspect to the issues I was having. Any ideas?
Click to expand...
Click to collapse
I didnt got any Problems with the pico Open GApps.
But you have to install something like GMail afterwards to get the actual Google/Playstore Services as Update.
After that I only do install the Google-Appsvthat I want.
Love this feature not having some odd G-Services in the Background or in the System-Partition.
(and I also use the pico on my Nexus 10 with CM13 because there is the /system only 800MB in size)
---------- Post added at 06:51 PM ---------- Previous post was at 06:25 PM ----------
Neekeet said:
Anyone else notice their tablet getting really hot? near the camera front and back.
Click to expand...
Click to collapse
on normal usage I didnt noticed the tablet being really hot.
Which apps do you use at this time? games with much graphics?
Tom did write about the voltage-selector of the gfx-card(?) that the voltage cant set down for underclocking or higher for overclocking....or somthing like this....moment I will copy the part...
"
Currently Disabled:
GPU Voltage Control/GPU OverClock/UnderClock (Needs to be rewritten for the M driver)
"
Dont know if your tablet will be hot about this disabled setting....
Everything is running fine now! thanks everyone
Love having MM on this tablet finally haha
Anyone's tablet feel a bit sluggish? it may be difficult to replicate but bringing down notifications seems to have some lag to it
Neekeet said:
Anyone's tablet feel a bit sluggish? it may be difficult to replicate but bringing down notifications seems to have some lag to it
Click to expand...
Click to collapse
for its fast as before with CM12....the Notifications werent for me the fastest ones....but Iam happy wirh this first build.
guidol said:
for its fast as before with CM12....the Notifications werent for me the fastest ones....but Iam happy wirh this first build.
Click to expand...
Click to collapse
Try to change the speed for windows animations, and the transition and animator duration. You can do that in developer options half way xown deist under drawing. Change the settings from window animation s ale, transition animation scale and animator duration scale from 1 to 0.5. See attached screenshot
pandoraman said:
Try to change the speed for windows animations, and the transition and animator duration. You can do that in developer options half way xown deist under drawing. Change the settings from window animation s ale, transition animation scale and animator duration scale from 1 to 0.5. See attached screenshot
Click to expand...
Click to collapse
I did try these settings - seems to be much better - many thanks
The Unlegacy Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for flo/deb include:
- Linux kernel 3.4.y merged in (currently 3.4.108 - mostly security patches and minor bug fixes)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data only!)
- SELinux in Enforcing mode
Installation
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
- No known issues for flo/deb yet.
If you notice anything, be sure to report it in this thread. Stability is our main concern. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds
We will have a built-in OTA updater (just like stock) soon (it's a work in progress)
Information about our experimental builds and progress you may find here.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
XDA:DevDB Information
Unlegacy Android Project, ROM for the Nexus 7 (2013)
Contributors
Ziyan, Clamor
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 8.1
Stable Release Date: 2017-03-24
Created 2017-03-24
Last Updated 2019-04-05
Reserved
GApps
If you want to install GApps, we recommend Open GApps Micro.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Stock-like setup
Disable the following built-in (AOSP) apps:
- Android keyboard (once you installed Gboard)
- Browser
- Calculator
- Camera
- Clock
- Email
- Gallery
Install the following apps from the Play store:
- Google Photos (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)
- Calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
- Chrome (https://play.google.com/store/apps/details?id=com.android.chrome)
- Clock (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
- Gboard (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin)
- Gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)
- Google Calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)
- Google Camera (https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera)
- Google Now Launcher (https://play.google.com/store/apps/details?id=com.google.android.launcher)
SafetyNet
The ROM should pass SafetyNet after installing GApps, without anything else. Keep in mind that installing extra stuff (SU, ...) might make it fail!
Rooting
You can flash the latest Magisk to get rooted.
Hello)
Please add a night mode, with the icon in the blind
boom1982 said:
Hello)
Please add a night mode, with the icon in the blind
Click to expand...
Click to collapse
I simply use Darker for night time playing in the bed personally, I reduce brightness to 65% and apply a slight yellow tint. When most websites are white, theming the framework wouldn't matter that much anyways... and we kinda want to feel like a factory image (no dark mode in them either)
@Ziyan
It's a pity)
The rom itself works fine. Good job)
@Ziyan Thanks for your efforts on these older devices. I've used your work on both Gtab 2 and Grouper before I sold them. I just downloaded 0324 builds for Flo and Hammerhead, neither one matched the MD5. I just downloaded Flo again but still no match. I haven't tried flashing any of the roms yet but figured I'd let you know.
Also, don't know if you use Netflix but it's been a problem getting a current version of the app working properly on ANY Nougat rom for Flo. Without any modifications, the Netflix app will load and give you an option to download and watch at a later time. However, if you try to just do a normal streaming of a movie or show, it will give you an error 0013. As is mostly the history of Netflix, it appears to be a drm issue. @Startrek852 was able to compile a zip with drmblobs that will eliminate the error 0013 and allow normal streaming but you lose the ability to download and watch at a later time. Although I don't use Google Movies, it's my understanding that it will not work if you flash the drmblobs.
Anyway, just wondering if "in your travels" you've heard of this Netflix issue and might possibly know of a proper fix. Thanks again.
Mike T
webdroidmt said:
I just downloaded 0324 builds for Flo and Hammerhead, neither one matched the MD5. I just downloaded Flo again but still no match.
Click to expand...
Click to collapse
This issue seems to haunt us... We'll try looking into it again ASAP. Oddly enough, every time I download, I get a match, and it flashes perfectly
webdroidmt said:
Also, don't know if you use Netflix but it's been a problem getting a current version of the app working properly on ANY Nougat rom for Flo. Without any modifications, the Netflix app will load and give you an option to download and watch at a later time. However, if you try to just do a normal streaming of a movie or show, it will give you an error 0013. As is mostly the history of Netflix, it appears to be a drm issue. @Startrek852 was able to compile a zip with drmblobs that will eliminate the error 0013 and allow normal streaming but you lose the ability to download and watch at a later time. Although I don't use Google Movies, it's my understanding that it will not work if you flash the drmblobs.
Click to expand...
Click to collapse
Play Movies works perfectly, so I'm not sure how to debug that either ways - can look into that zip later on.
Ziyan said:
This issue seems to haunt us... We'll try looking into it again ASAP. Oddly enough, every time I download, I get a match, and it flashes perfectly
Play Movies works perfectly, so I'm not sure how to debug that either ways - can look into that zip later on.
Click to expand...
Click to collapse
Thanks for your reply. Here's the D/L for the drmblobs zip if you decide to take a look. https://www.androidfilehost.com/?fid=529152257862690585
Very weird on the MD5 thing, as mentioned I downloaded it twice and on a desktop PC so it shouldn't be a mobile issue??? I'm gonna' flash it later, will report if there's a problem.
Mike T
@Ziyan
Updates come out every day ...?)
And why the cache is not f2fs?
I'm sorry that there are a lot of questions. I just made this rom basic and I want to figure it all out
p.s. That there were no problems with gapps - you need to restart the recovery after flashing the main rom
have volume wake option?
edit: stuck at "patch image "Patching system image unconditionally..."
boom1982 said:
@Ziyan
Updates come out every day ...?)
And why the cache is not f2fs?
I'm sorry that there are a lot of questions. I just made this rom basic and I want to figure it all out
p.s. That there were no problems with gapps - you need to restart the recovery after flashing the main rom
Click to expand...
Click to collapse
Our little build server likes overdoing its job and building even if the changes don't affect flo - until this is fixed, it's enough to update every 3-4 weeks or so to get the security updates, unless I make an announcement here about a change
About /cache f2fs: there's simply no point, as that partition isn't actively used by the system (other than maybe OTA updates). I usually don't support it, as it can lead to more complications than what it worth...
@Ziyan
Thank you for your reply)
I really like the way the rom works.
Only have to use a lot of additional tools to at least somehow expand the settings)))
Good work... but video recording with green lines in Google Camera 3.2, stock kernel, Nexus 5
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Mayrbek86 said:
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Click to expand...
Click to collapse
Mind giving me a bit more details regarding this? I can connect to a Wi-Fi Hotspot created with my Nexus 4 (also running Unlegacy Android 7.1) just fine, and can browse the internet with the Nexus 7 through it (mobile data activated on the Nexus 4)
Mayrbek86 said:
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Click to expand...
Click to collapse
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
maksimus0021 said:
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
Click to expand...
Click to collapse
Alright. We'll be soon opening a Nexus 5 thread as well.
Ziyan said:
Alright. We'll be soon opening a Nexus 5 thread as well.
Click to expand...
Click to collapse
Good news! Thanks for your work!
Regards.
maksimus0021 said:
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
Click to expand...
Click to collapse
Where did you find this fix wi fi, give me a link?
Mayrbek86 said:
Where did you find this fix wi fi, give me a link?
Click to expand...
Click to collapse
Install via TWRP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/
Click to expand...
Click to collapse
Rom Built by Bernie_nixKnown issues:
USB-C headphones work for music, watching videos, etc. They don't work in the phone app...yet. (working on this)
Some users report VOIP calls don't work properly. YMMV. Skype, Whatsapp, Nextcloud Talk, working great for me.
Automatic updates not yet implemented but will be in a future build.
You tell me.
Install Instructions(If coming from stock or another rom):
Prerequisites: Coming from stock rom with bootloader unlocked, Developer settings enabled, android debugging enabled.
(1) ADB reboot bootloader,
(2) Fastboot boot twrp.img
(3) Install copy A/B partitions zip,
(4) Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache, Data, Internal Storage, System. Then Swipe to Wipe all of these.
(5) Select Back arrow button
(6) Select Format Data Button. Type yes
(7) Select Install button. Choose rom zip. Swipe to confirm flash.
(8) Press back arrow button 2x to get back to main screen. Select Wipe button. Select format data button. Type yes.
(9) Reboot. Phone will mention "no os installed." Ignore it. Proceed with reboot. Phone will boot twice, then take you to the lineage recovery screen. Use volume down button to select Factory data reset, press power button, select yes to delete data. Phone will reboot into lineageos4microg.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM.
Upgrade Instructions(If coming from one of my previous builds):
(1) ADB reboot bootloader,
(2) Fastboot boot twrp.img
(3) Select Install button. Choose rom zip. Swipe to confirm flash.
(4) Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache
(5) Reboot(6) If you had Magisk installed, you can then reboot into TWRP/Ofox and flash magisk.zip
Tips for Use
1. Root can be enabled in this build by going to Developer Settings->Root Access->Apps and ADB
2. To turn off battery led when charging, Settings>Apps & notifications>Notifications>Battery Light
3. To set up Microg,
(1) open MicroG app,
(2) press self-check, press battery optimizations ignored and allow,
(3) go back one screen, select unified nlp settings, configure location backends, press the checkbox next to mozilla location service and ok, configure address lookup backends, press checkbox next to nominatum and ok,
(4) then go through Google services from top to bottom and enter your information.
(5) Enable location from pull-down shade. Open maps, get your location. Go back to Microg. Run self-check. All boxes should show a check.
(6) Microg is setup in less than 5 minutes and fully working.
(7) Turn off location from pull-down shade bc they're tracking you 4. Want a better GPS experience? Install Deja Vu Location Service, GSM Location Service and Radiocells.org Unified Network Location Provider Backend from F-Droid. Works great with Google Maps or OSM.
5. Looking for a great camera? Try Hypercam for Moto G7 from gcambrasil at https://gcambrasil.com.br/motorola
1. After installing, go to internal storage, create folder "gcam" (without quotes), create folder "Configs" inside of "gcam," and place the Pixelmod_byJGB.xml (attached) file in that folder.
2. Open up Hypercam, double tap on black space near camera button, load Pixelmod_byJGB.xml file.
Reporting bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed.
Please report bugs in this thread.
Logcats are helpful but not required. Grab a full logcat right after the problem has occurred.
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Thread Purpose & LimitsThis thread has been created to discuss the installation and use of this rom. If you have questions about building roms, this thread is not the place to do it. Please create a thread under Q/A and/or visit the Telegram group https://t.me/mG7Power. I'm happy to help but going to the telegram group or opening a Q/A thread allows many users to assist you and will help to keep this thread on-topic. Failure to follow this request will result in a warning followed by report to XDA if continued. Some excellent resources for building microg include https://lineage.microg.org/ and https://8192.one/post/lineage_build_with_docker/.
Download:
Change log
1. Latest March security update
Status: Stable
ROM OS Version: 9.x Pie
Android Security Patch Level: Mar. 5, 2020
Download link: https://www.androidfilehost.com/?fid=4349826312261741637
MD5: 54b467570f65ce85f164bd8e99943ab7
Older Versions:
Change log
1. Latest sources
2. Root option enabled in development settings
Status: Stable
ROM OS Version: 9.x Pie
Android Security Patch Level: Feb. 5, 2020
Download link: https://androidfilehost.com/?fid=4349826312261727435
MD5: aeb4aa1141c6d74ac016e8fba797c245
Next update news...:
Mar 10, 2020 - Currently working on USB-C audio during phone calls, increasing audio volume. Once USB-C audio gets fixed, I'll enable OTA updates.
Source and Additional Links
https://github.com/LineageOS
https://github.com/LineageOS/android...otorola_sdm632
Telegram group for additional ROMS, files and support: https://t.me/mG7Power
Rom Last Updated Mar. 10, 2020
Thread Info Last Updated Mar. 10, 2020
Guide on how to build your own posted here: https://forum.xda-developers.com/g7...d-lineageos4microg-16-0-t4070079#post82069641
hi im really interested in this rom but If twrp is already my permanent recovery, this rom won't install correctly?
edit.. tried it anyway since this is a secondary phone, figured i didnt have much to lose, followed instructions to the TEE, and it installed just fine.
clarkkentxda said:
hi im really interested in this rom but If twrp is already my permanent recovery, this rom won't install correctly?
edit.. tried it anyway since this is a secondary phone, figured i didnt have much to lose, followed instructions to the TEE, and it installed just fine.
Click to expand...
Click to collapse
I should have another update with OTA server and a few other fixes soon. It's also super quick to update from current build. Stay tuned and enjoy!
Bernie_nix said:
I should have another update with OTA server and a few other fixes soon. It's also super quick to update from current build. Stay tuned and enjoy!
Click to expand...
Click to collapse
Thanks for your efforts, I've been enjoying it, it's hard to find a rom that offers a little privacy from google, most things are working just fine, one thing I've noticed is that video is super super dark, No matter if it's stock camera or open camera but that's all I've came across in the issues department so far
clarkkentxda said:
Thanks for your efforts, I've been enjoying it, it's hard to find a rom that offers a little privacy from google, most things are working just fine, one thing I've noticed is that video is super super dark, No matter if it's stock camera or open camera but that's all I've came across in the issues department so far
Click to expand...
Click to collapse
Thanks for your feedback! No problems with video if using a different app. Try Hypercam version 1.3.030119.0645build-6.1.021
Bernie_nix said:
Thanks for your feedback! No problems with video if using a different app. Try Hypercam version 1.3.030119.0645build-6.1.021
Click to expand...
Click to collapse
Hypercam works like a charm, thank you for the suggestion! does hyper cam rely on anything google related like services or frameworks or binarys? (not sure what to call it since im not a developer) i'm wondering because I own a pixel 3a and im thinking of installing graphene os but any apps that rely on those ran on those will not work on graphene
clarkkentxda said:
Hypercam works like a charm, thank you for the suggestion! does hyper cam rely on anything google related like services or frameworks or binarys? (not sure what to call it since im not a developer) i'm wondering because I own a pixel 3a and im thinking of installing graphene os but any apps that rely on those ran on those will not work on graphene
Click to expand...
Click to collapse
Hypercam is ported from gcam so YMMV. Given that it works on this ROM with microg, if it has any hooks they probably aren't deep. I'd give it a go
I've been a user of root explorer (pro) for seven+ years or so now. I side loaded the apk that I extracted from a previous setup on my phone and it works perfect. Some may already know that but just figured I'd share. Awesome job on this rom! Appreciate you sharing your builds!! :good:
flash713 said:
I've been a user of root explorer (pro) for seven+ years or so now. I side loaded the apk that I extracted from a previous setup on my phone and it works perfect. Some may already know that but just figured I'd share. Awesome job on this rom! Appreciate you sharing your builds!! :good:
Click to expand...
Click to collapse
Glad you like it and thanks for your feedback; tip on root explorer pro.
Bernie_nix said:
Glad you like it and thanks for your feedback; tip on root explorer pro.
Click to expand...
Click to collapse
Couple questions.. What busy box are you using and where did you get it? I've been using Osmosis’s magisk module busy box for so long idk where to even begin. haha. I attempted to install one from fdroid but it failed install. Can I flash his busy box in recovery? Probably not because we are using the LOS built in root instead of magisk correct? Would all hell break loose if I flashed magisk root now and something would possibly get messed up? Thinking if that's what I wanted I would have had to flash it in the beginning so it would over ride the other root...?
This rom runs better than anything besides ugly stock moto on my device. I was off work yesterday so I started messing with my device, hours went by and my battery barely moved at all. Not having Google play services really saves a good bit of juice. Havoc has spoofing now too. I vote that it becomes mandatory for all roms to have signature spoofing. :victory: Should call it the ImNOtgoingback rom or something. I’ve used micro g and fdroid before on previous devices but never for as long as I've been using this. Im like a binge crackflasher nowadays instead -vs- back when Euroskank CM10 bacon was on and popping every morning at around 6am central time the world would all flash. One last thing.. Do you decrypt your data or leave it encrypted? Reason I ask is I was wondering what method you do or would do if you wanted to decrypt?
This rom really runs great! Anyone who hasn't tried this yet should!
Edit
Ps: I've used many great gcams but HyperCam is most definitely at the top of my list. It reminds me of the pictures my Pixel XL used to take. Awesome camera app! Thanks for recommending it and sharing links!
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
DanAlucard said:
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
Click to expand...
Click to collapse
You're right, but it's not easy to be a maintainer - and use your free time to resolve problems for others.
Maybe you should try to create your own build using code created by more advanced users synced with latest LineageOS repo.
If you're interested in that, here's an attached manifest file which would build working LineageOS 16.0 for ocean with February security patch - I'm using such one right now(built 3 days ago), but with microg. It's all possible thanks to LineageOS team and Dark98 (and many others) work, as you can see.
Good luck
robson_89 said:
You're right, but it's not easy to be a maintainer - and use your free time to resolve problems for others.
Maybe you should try to create your own build using code created by more advanced users synced with latest LineageOS repo.
If you're interested in that, here's an attached manifest file which would build working LineageOS 16.0 for ocean with February security patch - I'm using such one right now(built 3 days ago), but with microg. It's all possible thanks to LineageOS team and Dark98 (and many others) work, as you can see.
Good luck
Click to expand...
Click to collapse
Thanks a lot. Will have a look at it. Who knows, maybe I end up maintaining it
DanAlucard said:
Thanks a lot. Will have a look at it. Who knows, maybe I end up maintaining it
Click to expand...
Click to collapse
That would be great!
In the meantime, i've built and updated my LOS 16 as attached - forgot to add screenshot previously.
DanAlucard said:
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
Click to expand...
Click to collapse
Not from me. I build this for personal use, share it and have no interest in a vanilla los build. Robson is correct. Go with his build of you don't want microg.
flash713 said:
Couple questions.. What busy box are you using and where did you get it? I've been using Osmosis’s magisk module busy box for so long idk where to even begin. haha. I attempted to install one from fdroid but it failed install. Can I flash his busy box in recovery? Probably not because we are using the LOS built in root instead of magisk correct? Would all hell break loose if I flashed magisk root now and something would possibly get messed up? Thinking if that's what I wanted I would have had to flash it in the beginning so it would over ride the other root...?
This rom runs better than anything besides ugly stock moto on my device. I was off work yesterday so I started messing with my device, hours went by and my battery barely moved at all. Not having Google play services really saves a good bit of juice. Havoc has spoofing now too. I vote that it becomes mandatory for all roms to have signature spoofing. :victory: Should call it the ImNOtgoingback rom or something. I’ve used micro g and fdroid before on previous devices but never for as long as I've been using this. Im like a binge crackflasher nowadays instead -vs- back when Euroskank CM10 bacon was on and popping every morning at around 6am central time the world would all flash. One last thing.. Do you decrypt your data or leave it encrypted? Reason I ask is I was wondering what method you do or would do if you wanted to decrypt?
This rom really runs great! Anyone who hasn't tried this yet should!
Edit
Ps: I've used many great gcams but HyperCam is most definitely at the top of my list. It reminds me of the pictures my Pixel XL used to take. Awesome camera app! Thanks for recommending it and sharing links!
Click to expand...
Click to collapse
Thank you for your kind words! I use busybox from osmosis via magisk module; yes, I enjoy magisk on this rom. Busybox (osmosis) actually makes apps like Titanium Backup work great if you've purchased a non-Google play license file from them. This rom is my personal build that I uploaded to xda and shared, and I plan on maintaining it for some time. So...Magisk flashed via twrp/ofox works great, and so does busybox magisk.
+1 on your comment about Hypercam. Completely agree about hypercam. I've tested a lot on this device and of course am open to suggestions.
I will update this rom via the Lineageos patches, however, the Feb update hasn't been pushed yet so no new rom for now. I have isolated a few bugs, e.g. usb-c for calls and am working on OTA, however, I am going to release a surprise test build in the next couple of days (hopefully). It's building as we speak, and I will test before releasing. Stay tuned, and I look forward to yours and others feedback and questions.
P.S. I am a linux user and believe in the power of open-source. If you or others have any questions or comments, feel free to reach me via the telegram link in the 1st post; I usually answer a bit quicker there but also answer on here. Best wishes and thanks again!
P.S.S. Welcome Robson to our open-source team! If any of you are looking for a lineageos build without microg, check out his post a couple of posts above.
generally audio is lower quality than stock rom, it's not as loud and not as clear.
clarkkentxda said:
generally audio is lower quality than stock rom, it's not as loud and not as clear.
Click to expand...
Click to collapse
Did you try the audiofx app that is included?
Bernie_nix said:
Did you try the audiofx app that is included?
Click to expand...
Click to collapse
Indeed sir, it doesn't help all that much for me though.
rottenwheel said:
I accompany this sentiment. It happens with most Motorola Moto G devices I own and use: if kept with stock builds both camera and audio have a far better quality than custom ROMs do. Motorola engineers do hell of a job when working on their OEM firmware. It is a real shame yet not so far from reality that we need to take these tradeoffs to obtain better privacy.
An idea that comes to mind is for us to debloat the stock build, bake in microG and possibly update security patches as they come out. Motorola Moto G1 (falcon) has something alike with IDCrisis - https://forum.xda-developers.com/moto-g/development/rom-identity-crisis-6-t3324595
Thank you for the heads-up, though. I definitely love the audio on stock.
Click to expand...
Click to collapse
Unfortunately you can't do that with stock. Microg requires signature spoofing enabled in the ROM which is a patch applied when building a ROM. You could try patching stock to enable signature spoofing with a tool like Heystack but it most likely won't work on stock. Another route is using another ROM with signature spoofing support e.g. crdroid or omni, applying signature spoofing patch if necessary and then patching in twrp with something like nanodroid patcher.
That being said I am working through desired edits and bugs in this ROM but can't provide any ETAs. I encourage anyone with a bit of coding experience or interest to build their own and learn. Making changes to rom builds is not hard, just time consuming and unfortunately doesnt pay the bills...so its done in hobby time. I do plan on maintaining this ROM for some time though and will probably be on Pie longer than most users until 10 is ready; right now 10 has way too many bugs for me to use or build for daily driver material.
Code:
/*
* 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.
*
*/
Hi,
here you can find my preview version of LineageOS 20.0 for our Samsung Galaxy Note 8.0 devices.
At first I want to thank @rINanDO and @ChronoMonochrome for all your work which helped me a lot.
This is a ALPHA build, also on the LineageOS side, so don't install it if you want a completley stable rom and don't report my already listet bugs!
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Bluetooth
Audio
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Stylus
RIL
much more...
Spoiler: Whats not working
Random reboots
Accelerometer
GPS for N5100 and N5110
Network monitoring because of missing eBPF
Encryption
Maybe more
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
ROM Mega
Gapps, I don't recommend them, use the smallest package
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
download
I would recommend to use microG (much faster experience) or open Gapps as soon they are available.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
XDA:DevDB Information
[ROM][13.x][N5100/N5110/N5120][ALPHA] LineageOS 20.0, ROM for the Samsung Galaxy Note 8.0
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 13.x T
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Alpha
Created 2022-11-03
Last Updated 2022-11-03
*reserved
@html6405 , thanks for building 20.0 on these devices. Your link in post #1 for mega is incorrect. It shows
Code:
https://forum.xda-developers.com/mnt/wwn-0x5002538f4142e6ee-part5/LineageOS_20_out/target/product/n5100/20.0-20221103-HTML6405-n5100.zip%20/mnt/wwn-0x5002538f4142e6ee-part5/LineageOS_20_out/target/product/n5100/20.0-20221103-HTML6405-n5100.zip.sha256sum
I tried 2 different browsers and both show the same.
retiredtab said:
@html6405 , thanks for building 20.0 on these devices. Your link in post #1 for mega is incorrect. It shows
Code:
https://forum.xda-developers.com/mnt/wwn-0x5002538f4142e6ee-part5/LineageOS_20_out/target/product/n5100/20.0-20221103-HTML6405-n5100.zip%20/mnt/wwn-0x5002538f4142e6ee-part5/LineageOS_20_out/target/product/n5100/20.0-20221103-HTML6405-n5100.zip.sha256sum
I tried 2 different browsers and both show the same.
Click to expand...
Click to collapse
Ooooh, there happened a stupid copy paste error, I'm really sorry.
I will update the download link tomorrow morning, I don't have access yet by myself.
html6405 said:
Ooooh, there happened a stupid copy paste error, I'm really sorry.
I will update the download link tomorrow morning, I don't have access yet by myself.
Click to expand...
Click to collapse
There's no rush. BTW, your 19.1 thread also has the incorrect link for Mega. I think it's another cut and paste error from you trying to shim a symbol because it starts with _Zn.
Thanks.
Thank you for your dedication.
@html6405
I think the thread title is wrong. It should be Android 13 instead of Android 12L.
everything seems to be working apart from the things that you listed. only thing i noticed is that the battery life is really poor, mic is not working and the keyboards scaling is a little bit weird? Great work tho keep it up )
I have have the Android 13 version now running on my GTN-5100 since 3 days. Besides 1-2 crashes it seems to be stable enough. Things I am missing most with that ROM is GPS and missing encryption.
The Android 13 version has one bug, I not have seen on the earlier versions. I can not change the background picture when this has a certain size. How to reproduce:
Store an image ~ 3 MB e.g. into your Download folder
Long press in Trebuchet launcher to change background & style
Select Change background
Try to load the picture from the Download folder => error message stating "Background image could not be loaded. Either the image is defect or not accessible, which is both not the case
Since Android 11 I see the following behavior with certain apps. Example organic maps from F-droid. The app is not able to store the maps on the SD card.
How to reproduce:
Install "organic maps" from F-droid. Launch app
The app asks you to download the world map.
If you store the map on the internal storage, all is fine and the map can be displayed
If you store the map on the SD card, which is the wanted behavior because of the amount of data of offline maps, the map can not be displayed but no further error message about not being able to store the data.
I use the ROM withou Gapps. I am happy with the pre-installed Aurora store
Happy to do some further testing in case it helps
Again, I am really happy with the speed and quality of the releases
Hi @html6405, I generated now a log file created during organic map tries to download and store the basic map on the device. I hope that helps detecting where their might be a bug.
I remain using the ROM happily with a crash occasionally.
A minor thing I am missing, which was there on the 19. and 18. version is the wake up functionality when pulling the device out of a wallet. Not sure if this is simply due to Android 13 functionality or something you added to the ROMs before.
TibReg said:
I have have the Android 13 version now running on my GTN-5100 since 3 days. Besides 1-2 crashes it seems to be stable enough. Things I am missing most with that ROM is GPS and missing encryption.
The Android 13 version has one bug, I not have seen on the earlier versions. I can not change the background picture when this has a certain size. How to reproduce:
Store an image ~ 3 MB e.g. into your Download folder
Long press in Trebuchet launcher to change background & style
Select Change background
Try to load the picture from the Download folder => error message stating "Background image could not be loaded. Either the image is defect or not accessible, which is both not the case
Since Android 11 I see the following behavior with certain apps. Example organic maps from F-droid. The app is not able to store the maps on the SD card.
How to reproduce:
Install "organic maps" from F-droid. Launch app
The app asks you to download the world map.
If you store the map on the internal storage, all is fine and the map can be displayed
If you store the map on the SD card, which is the wanted behavior because of the amount of data of offline maps, the map can not be displayed but no further error message about not being able to store the data.
I use the ROM withou Gapps. I am happy with the pre-installed Aurora store
Happy to do some further testing in case it helps
Again, I am really happy with the speed and quality of the releases
Click to expand...
Click to collapse
How is your experience with this ROM so far? stable? bugs?
All ROMS are very usable and stable. I am, after testing all of them went back to the /e/ version based on Android 9 for the following reasons:
Stability
Encryption
Data Privacy
Simplistic UI
All applications I need are running well on the device
I know, that there are no more updates and I will probably make the move back to one of the later ROMs when I can encrypt and all applications are running with no storage access issues. That is a very personal preference and there are many reasons to have a different preference. I am thankful to have this number of choices for such an old device with still a great form factor an an active pen
Which Android-9 based ROM you're running right now?
Hi, Do you have screen rotation, I don't have
Awesome Rom, thanks
thanks