[ROM][UNOFFICIAL][9] LineageOS4Microg 16.0 (by Bernie_nix) - Moto G7 Power ROMs, Kernels, Recoveries, & Other D

[ROM][UNOFFICIAL][9] LineageOS4Microg 16.0 (by Bernie_nix) - Moto G7 Power ROMs, Kernels, Recoveries, & Other D

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.

Related

[ROM][AOSP][7.1/8.1/9.0 EXP][flo/deb] Unlegacy Android Project

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.

[ROM][UNOFFICIAL] LineageOS 14.1 Nightlies for the Google Pixel (marlin/sailfish)

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/.

[ROM] [UNOFFICIAL] LineageOS 13.0 for the M.O.J.O.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 13 is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), 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. You can also view the Changelog for a full list of changes & features.
Changelog:
Code:
[20180127]:
Improved powerHAL, fix hdmi audio issue and new libbt-vendor.
[20180122]:
New powerHAL from molly, should give better cpu management.
New libAudio from molly: AudioFX now working!
[20180106]:
Added NTFS support, thanks to K-Project for issue repport
[20180105]:
Updated Proprietary blobs (mainly video driver) from Jide ultratablet (LMY47V 5.1.1)
Remove nvcpud (NVidia cpu speed daemon)
Some cleanup
[20180102]:
Some cpu tweaks
Added buttons (and navbar) config in settings
Updated bluetooth config thanks to carp_be
[20171228]:
Initial build
Instructions :
Download the latest build and gapps
Reboot to recovery (newest TWRP 3.2.1-0 prefered)
Go Wipe->Advanced->Select system,cache and data partition (not required if coming from previous version)
Flash the latest build and gapps (gapps not required if coming from previous version)
Reboot
Downloads :
Builds : Google Drive folder Choose the latest
Root addon : https://download.lineageos.org/extras Required for full root! Without it you'll only have adb root, that's how LineageOS is made
Google Apps : http://opengapps.org/
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console_ramoops. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Working:
Allmost all, including Google WideVine and Microsoft DxDrm. Android System WebView installation is mandatory to avoid issues like bootloop when installing apps that use drm.
Not working:
AudioFx
XDA:DevDB Information
LineageOS 13.0 for the M.O.J.O., ROM for the Mad Catz M.O.J.O.
Contributors
nono2lozere, Unjustified Dev, carp_be
Source Code: https://github.com/nono2lozere
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Testing
Current Beta Version: 13.0
Beta Release Date: 2017-12-28
Created 2017-12-28
Last Updated 2018-01-27

Wowzers, you really did it! Thanks for putting some life into this marvellous device (or trying to anyway)!
Anyway, I've installed it. I used the older TWRP 2.8.2.0. Not sure if I need to be using something more recent now, but it worked.
Code:
What is your--
LineageOS version: 13
LineageOS Download: https://drive.google.com/open?id=1NJCHZo58BnZIyELYBqlx-0Fy61uBWCAO
Gapps version: open_gapps-arm-6.0-nano-20171228
Did you--
wipe: YES
restore with titanium backup: NO
reboot after having the issue: NO
Installed nicely and with no upset. It takes a while on first boot for those of you giving this a go, so allow a moment or two while it gets things together.
Got to say I am very impressed. It's Lineage 13! On the MOJO! Yes AudioFX doesn't work as you say, but it seems the rest does! However, I'm having a couple of issues you may be able to help with. Firstly, I tried rooting the device in the same way I did CM 12.1, basically by going into developer options and selecting root access. However, there's only an option to root via ADB, no apps access. Is this intentional? I was unable to install my quick reboot app meaning one has to hard shut down (i.e. pull the plug) on the device which is never an elegant way to do things. What is the best solution to root this please? Many thanks.
I also notice that when trying to use a browser, be it Firefox or Chrome, to download something it gives you an error. I tried to download a simple file and Firefox just failed, but luckily Chrome was a bit more verbose and explains why. It said it did not have access to the internal storage despite me confirming all the options after installing it. Not sure what's happening here.
Other than these things, at this early stage the only other thing I noticed was some tearing of the screen on animated transitions. Occasionally it seems to pull and break up a bit when whipping around.
I think I speak for everyone here when I say - THANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOU!!! I look forward to further adventures with this ROM!

K-Project said:
Wowzers, you really did it! Thanks for putting some life into this marvellous device (or trying to anyway)!
Anyway, I've installed it. I used the older TWRP 2.8.2.0. Not sure if I need to be using something more recent now, but it worked.
Code:
What is your--
LineageOS version: 13
LineageOS Download: https://drive.google.com/open?id=1NJCHZo58BnZIyELYBqlx-0Fy61uBWCAO
Gapps version: open_gapps-arm-6.0-nano-20171228
Did you--
wipe: YES
restore with titanium backup: NO
reboot after having the issue: NO
Installed nicely and with no upset. It takes a while on first boot for those of you giving this a go, so allow a moment or two while it gets things together.
Got to say I am very impressed. It's Lineage 13! On the MOJO! Yes AudioFX doesn't work as you say, but it seems the rest does! However, I'm having a couple of issues you may be able to help with. Firstly, I tried rooting the device in the same way I did CM 12.1, basically by going into developer options and selecting root access. However, there's only an option to root via ADB, no apps access. Is this intentional? I was unable to install my quick reboot app meaning one has to hard shut down (i.e. pull the plug) on the device which is never an elegant way to do things. What is the best solution to root this please? Many thanks.
I also notice that when trying to use a browser, be it Firefox or Chrome, to download something it gives you an error. I tried to download a simple file and Firefox just failed, but luckily Chrome was a bit more verbose and explains why. It said it did not have access to the internal storage despite me confirming all the options after installing it. Not sure what's happening here.
Other than these things, at this early stage the only other thing I noticed was some tearing of the screen on animated transitions. Occasionally it seems to pull and break up a bit when whipping around.
I think I speak for everyone here when I say - THANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOU!!! I look forward to further adventures with this ROM!
Click to expand...
Click to collapse
I personaly use TWRP-2.8.7.0.
For full root you need to install root addon, it's how Lineage is made.
And try to reboot or force close chrome or firefox, sometimes it doesn't take permission at first launch, hope it works because I didn't try chrome.
Have you made an advanced wipe? because without format system the install script will backup some garbage of the previous rom witch can cause issue.

Thanks for replying.
Yes I did an advanced wipe. I wanted to be sure that this was cleanly done.
I'm not familiar at all with Lineage so I had no idea about root addons. I think I've found them now, so I'll reflash the device and post back later. Thanks for the heads up.
I didn't attempt to reboot either Chrome or Firefox so I'll give that another go too after the reflash.

Code:
What is your--
LineageOS version: 13
LineageOS Download: [url]https://drive.google.com/open?id=1NJCHZo58BnZIyELYBqlx-0Fy61uBWCAO[/url]
Gapps version: open_gapps-arm-6.0-pico-20171228
Did you--
wipe: YES FULL
restore with titanium backup: NO
reboot after having the issue: NO
Youtube works perfect (my "test" video plays) :highfive:
Still two other crashes is here View attachment 2017-12-28-20-39-36e.txt
Process ru.norgen.homevideo (pid 3189) has died
Process com.lolapp.lolapptv (pid 3527) has died
Nice work - looks very promissing

This is amazing , wow , thanks so much ,I will try it asap

Nice, next week I have again a good internet connection so I can sync the lineageos tree. I'll then will try to port androidTV

Very impressed with the WiFi so far. No issues that I've discovered, though of course this is an early stage. It works even when booting with an SD card in.
OK, so reflash... I switched to TWRP 2.8.7.0 as you said.
Following your reply I grabbed the Lineage AddonSu package that seemed relevant, but unfortunately this would not flash. It gave me an error message 4 and said there was a problem with the binary. I tried it twice but no luck. However, I had an older Super Su package I kept from a while ago (2.46) and flashed this. It worked fine and even updated from the Play Store OK. This allowed me to install and use the reboot app just fine. So I set about installing some apps.
As you stated, after a reboot of Firefox it downloads fine. Simply permit it access to your storage, and then close and reopen. This works.
I installed both Kodi and Retroarch but I am getting no sound at all. At first I thought I'd done something wrong in the settings for both apps and the device but it appears not. There's no sound at all. I will attempt a reboot again but it didn't work after a couple of reboots. Is this expected at this stage or is there something I need to do? Please let me know.
Anyway, my thanks again for a great update. I really hope you carry on the work and I look forward to continuing with this OS. I hope my posts are helping rather than causing any problem.
---------- Post added at 10:52 PM ---------- Previous post was at 10:47 PM ----------
Only other thing I noticed was the MOJO seems to get very warm and does seem to lag a little bit with the mouse after half an hour. I checked the memory usage and it seemed OK, so perhaps it's hammering the CPU? I dunno, but thought it worth mentioning to see if other folks notice the same thing.

awesome thanks for this

[Sorry for multiple posts]
Sound is back today. Not sure what happened but it's working fine. I've decided to just set everything up as I normally have it and really see how it goes. So far everything seems to be working as it should.
Awesome!
However, I am definitely experiencing some lag once the device has been on for some time. I've been playing with the MOJO all morning and there's definitely screen tearing and some lagginess in transitions over time. It seems better after a reboot, but it's not long before it creeps back in again. I'll be curious to see if anyone else has this issue.

K-Project said:
Very impressed with the WiFi so far. No issues that I've discovered, though of course this is an early stage. It works even when booting with an SD card in.
OK, so reflash... I switched to TWRP 2.8.7.0 as you said.
Following your reply I grabbed the Lineage AddonSu package that seemed relevant, but unfortunately this would not flash. It gave me an error message 4 and said there was a problem with the binary. I tried it twice but no luck. However, I had an older Super Su package I kept from a while ago (2.46) and flashed this. It worked fine and even updated from the Play Store OK. This allowed me to install and use the reboot app just fine. So I set about installing some apps.
---------- Post added at 10:52 PM ---------- Previous post was at 10:47 PM ----------
[/COLOR]Only other thing I noticed was the MOJO seems to get very warm and does seem to lag a little bit with the mouse after half an hour. I checked the memory usage and it seemed OK, so perhaps it's hammering the CPU? I dunno, but thought it worth mentioning to see if other folks notice the same thing.
Click to expand...
Click to collapse
I havn't seen su addon issue before because I havn't try it yet! the issue is in twrp, so I have two option: make a compatible addon or a new twrp recovery.
I'm going for the new twrp solution because it will also allow Lineage 14.1 install if i want to try it.
For the lags I need to check clocking parameters, maybe they are wrong.

nono2lozere said:
I havn't seen su addon issue before because I havn't try it yet! the issue is in twrp, so I have two option: make a compatible addon or a new twrp recovery.
I'm going for the new twrp solution because it will also allow Lineage 14.1 install if i want to try it.
For the lags I need to check clocking parameters, maybe they are wrong.
Click to expand...
Click to collapse
I was testing with TWRP 2.8.2 and addonsu-13.0-arm-signed.zip - everything was fine.
Only Lineage SU was forgetting "allow" after reboot...
P.S. TWRP 2.8.7 was doing something wrong with CM builds or OpenGapps or SuperSU installation - only don't remember what... Now long time sitting on 2.8.2 - everything OK :angel:

nono2lozere said:
I havn't seen su addon issue before because I havn't try it yet! the issue is in twrp, so I have two option: make a compatible addon or a new twrp recovery.
I'm going for the new twrp solution because it will also allow Lineage 14.1 install if i want to try it.
For the lags I need to check clocking parameters, maybe they are wrong.
Click to expand...
Click to collapse
Not sure if there's a better way to check CPU, but I notice when using KODI it runs at 100% all the time. I use an external drive with my media files, and while they would play you could tell it was struggling. Lots of stutter, despite changing the settings etc.
rahsoft said:
I was testing with TWRP 2.8.2 and addonsu-13.0-arm-signed.zip - everything was fine.
Only Lineage SU was forgetting "allow" after reboot...
P.S. TWRP 2.8.7 was doing something wrong with CM builds or OpenGapps or SuperSU installation - only don't remember what... Now long time sitting on 2.8.2 - everything OK :angel:
Click to expand...
Click to collapse
I'd be curious to know what the difference is. Like I say, I ended up using TWRP 2.8.7.0-mojo and then flashed the older SuperSu 2.46 zip. This seems to work and has done the job, but I wonder if it there's an incompatibility that is causing my lag issues...?

Don't know if anyone can help here. Installed this and it just upgraded my CM 12.0 I had installed.
I lost root so couldn't boot back into recovery using an app.
I went to boot into recovery using PC and a male to male (which I did originally when flashing CM 12.0 but it just sends me to a boot loop with the liniage os intro scene.
If I boot again normally I get back to Lineage OS. Problem is I wanted to install this as all my apps were crashing constantly after a year of no issues (with CM12).
They're still crashing with Lineage OS but I can't get it to recovery mode for a fresh install.

TrentLane said:
Don't know if anyone can help here. Installed this and it just upgraded my CM 12.0 I had installed.
I lost root so couldn't boot back into recovery using an app.
I went to boot into recovery using PC and a male to male (which I did originally when flashing CM 12.0 but it just sends me to a boot loop with the liniage os intro scene.
If I boot again normally I get back to Lineage OS. Problem is I wanted to install this as all my apps were crashing constantly after a year of no issues (with CM12).
They're still crashing with Lineage OS but I can't get it to recovery mode for a fresh install.
Click to expand...
Click to collapse
Are you sure you've plugged the male-to-male USB cable into the right slot? It has to be in the USB2 one or the MOJO will continue to boot as normal. I know this as I did exactly the same thing very recently. Plug your mouse into the blue USB3 slot instead.
You cannot brick the MOJO unless the hardware has failed. It can always be rescued by connecting it to a PC/laptop and reflashing TWRP then ROM etc. I posted here not so long ago that my MOJO suddenly and for no real reason decided to plunge into a bootloop just as it was installing some simple updates from the Play store. It had been absolutely fine for nearly two years. Nevertheless I was able to connect it to the laptop and reflash and run TWRP. There I completely erased the device and installed Lineage 13 as the timing couldn't have been more perfect.

TrentLane said:
Installed this and it just upgraded my CM 12.0 I had installed.
Click to expand...
Click to collapse
Wait... so can I upgrade from CM 12.1 without losing anything?!

EdoNINJA93 said:
Wait... so can I upgrade from CM 12.1 without losing anything?!
Click to expand...
Click to collapse
don't think so
Instructions :
Download the latest build and gapps
Reboot to recovery
Go Wipe->Advanced->Select system,cache and data partition
Flash the latest build and gapps
Reboot
Click to expand...
Click to collapse

Wmapa said:
don't think so
Click to expand...
Click to collapse
It would have been too good to be true...
From his message it seemed that all the apps remained untouched... :/

EdoNINJA93 said:
Wait... so can I upgrade from CM 12.1 without losing anything?!
Click to expand...
Click to collapse
You can try but make a backup before, I don't know if it's possible.

First post updated.
Enjoy new build!

[DEPRECATED][ROM][UNOFFICIAL][N][SM-T285] /e/ OS for Samsung Galaxy Tab A 7.0 LTE (gtexslte) | BYE Google, HELLO Privacy!

{
"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"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of LineageOS
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds UNOFFICIAL?
There are no differences. its pure /e/. "just" build on my server
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Camera does work but only for photo, i.e. video recording fails.
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP (recommended) build.
Do a full (i.e. Nandroid) backup before doing anything!
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? STOOOOOOP! NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easiest way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/nougat/gtexslte/
If you have a previous version of my(!) /e/ ROM installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
search results from this thread: click
Support
Of course in this thread but also by Telegram.
I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
jedld, really he did a great job and making this project possible at first!
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
and all I forgot to mention ....!
Sources
build manifest
XDA:DevDB Information
gtexslte_eos-n_unofficial, ROM for the Samsung Galaxy Tab A series
Contributors
steadfasterX, jedld(!)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2020-11-18
Last Updated 2020-11-18

FAQ
Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
No plans on my site. I may check that later but the chance is very low.
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #5: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #7: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
.-

steadfasterX said:
Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
No plans on my site. I may check that later but the chance is very low.
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #5: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
On windows:
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #7: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
.-
Click to expand...
Click to collapse
Very nice job. Looking awesome:good:

Everything is ok except some problems/issues.
First is the camera. As you have said, camera does work but only for photo. But it only happens on the foundation.e.camera (default camera app). And in other apps require camera such as Qanda, it does not work. Like this:
The second problem is the cellular (or phone signal) problem. It says that "Emergency calls only" and I can't use mobile data(4g) or make any phone calls.
The next one is stability. Sometimes Espeak have fc (force-close) after using camera app.
and sometimes Bliss launcher (pre-installed) have some fc when i press home button.
Sorry if I can't provide to you the proper log because of some reasons.
Anyways, the rom works very well and actually better than the LOS i used before.
Without Google spyware, The performance increases and i have more ram to do other things.
I hope you will fix those issues i have mentioned above in future OTA updates.
Thank you for the nice work.

espeak is a known issue of /e/ OS and should be fixed hopefully anytime soon: https://gitlab.e.foundation/e/backlog/-/issues/1890
cam is nothing I will work on sorry..
signal issue is very likely because of your STOCK firmware --> make a screenshot of the full " about" menu in settings (where you see build number etc)

Can I encrypt /data partition like in the Settings > Encryption > Encrypt phone
and Encrypt SD Card with this ROM?
Also, how stable it is for daily driver/use?
Did you fix the mic routing issue when in call? Use earphone mic instead of the built in mic of the tablet?
How about the video when app like Element.io or some other video conferencing apps?

steadfasterX said:
espeak is a known issue of /e/ OS and should be fixed hopefully anytime soon: https://gitlab.e.foundation/e/backlog/-/issues/1890
cam is nothing I will work on sorry..
signal issue is very likely because of your STOCK firmware --> make a screenshot of the full " about" menu in settings (where you see build number etc)
Click to expand...
Click to collapse
Here are some screenshots
This one is from "about tablet" menu.
And I bonus some screenshots include some information i have from the "Device info HW" app (ru.andr7e.deviceinfohw, maybe you've already known it before).
That's all the screenshot i provided.

GAPS does not work. I'm using the open_gapps-arm-7.1-nano-20170503.zip version

ijlara said:
GAPS does not work. I'm using the open_gapps-arm-7.1-nano-20170503.zip version
Click to expand...
Click to collapse
Uhm.. Maybe read the OP again??

Sorry ... I really read it and ended up forgetting that GAPS doesn't work ....

johnnyhoang said:
Everything is ok except some problems/issues.
First is the camera. As you have said, camera does work but only for photo. But it only happens on the foundation.e.camera (default camera app). And in other apps require camera such as Qanda, it does not work. Like this:
The second problem is the cellular (or phone signal) problem. It says that "Emergency calls only" and I can't use mobile data(4g) or make any phone calls.
The next one is stability. Sometimes Espeak have fc (force-close) after using camera app.
and sometimes Bliss launcher (pre-installed) have some fc when i press home button.
Sorry if I can't provide to you the proper log because of some reasons.
Anyways, the rom works very well and actually better than the LOS i used before.
Without Google spyware, The performance increases and i have more ram to do other things.
I hope you will fix those issues i have mentioned above in future OTA updates.
Thank you for the nice work.
Click to expand...
Click to collapse
ok your cell service issue could come from a too old stock firmware. yours is from 2016 and there were some releases later on.
I have adjusted the OP with instructions (pls see topic "Requirements") with the firmware I am using without issues.
.-

It is difficult to find a ROM that works well on this device. It is for my daughter and I also can't get a ROM that works with Samsung's Kids Mode.

steadfasterX said:
ok your cell service issue could come from a too old stock firmware. yours is from 2016 and there were some releases later on.
I have adjusted the OP with instructions (pls see topic "Requirements") with the firmware I am using without issues.
.-
Click to expand...
Click to collapse
i have tried so many ways. And it is not working after all.
installed T285XXU0AQH1 baseband from the BTU csc , but the cell service issues still happening.
my original csc is XXV, and the latest update still T285XXU0API1 baseband (20171115 ver.)

johnnyhoang said:
i have tried so many ways. And it is not working after all.
installed T285XXU0AQH1 baseband from the BTU csc , but the cell service issues still happening.
my original csc is XXV, and the latest update still T285XXU0API1 baseband (20171115 ver.)
Click to expand...
Click to collapse
uhm.. well that was not what I said. I did not say "install the baseband" I said install the FULL(!!!!!) STOCK firmware. Here again:
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version (===> hint: this info is the best indicator to find out your current STOCK firmware, afaik)
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
There is nothing mentioned to extract just a subset and only flashing a subset. No. flash it completely or leave it. Just flashing part of it will break and/or even hard brick.

steadfasterX said:
uhm.. well that was not what I said. I did not say "install the baseband" I said install the FULL(!!!!!) STOCK firmware. Here again:
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version (===> hint: this info is the best indicator to find out your current STOCK firmware, afaik)
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
There is nothing mentioned to extract just a subset and only flashing a subset. No. flash it completely or leave it. Just flashing part of it will break and/or even hard brick.
Click to expand...
Click to collapse
Ok,i have given up. I don't know the way to install that properly because of the CSC differences(you said it should be in T285XXU0AQH1 but it didn't available in my country XXV. XXV still use T285XXU0API1 even with the latest update from 2017). So i will use that normally bc i'm ok without cellular.Btw things still work like a charm, and i have no regret of choosing this rom.

steadfasterX said:
uhm.. well that was not what I said. I did not say "install the baseband" I said install the FULL(!!!!!) STOCK firmware. Here again:
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version (===> hint: this info is the best indicator to find out your current STOCK firmware, afaik)
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
There is nothing mentioned to extract just a subset and only flashing a subset. No. flash it completely or leave it. Just flashing part of it will break and/or even hard brick.
Click to expand...
Click to collapse
Sorry for misunderstanding.
I have found the reason why the cellular issues comes out. It is made by the SIM card itself, not the baseband version or the stock firmware version as you have said. I was wrong when i think that it come from the software or stock firmware. Now i found out the reason for that. Sincerely apologize to you.
johnnyhoang said:
Ok,i have given up. I don't know the way to install that properly because of the CSC differences(you said it should be in T285XXU0AQH1 but it didn't available in my country XXV. XXV still use T285XXU0API1 even with the latest update from 2017). So i will use that normally bc i'm ok without cellular.Btw things still work like a charm, and i have no regret of choosing this rom.
Click to expand...
Click to collapse
Anyways thanks for noticing the recquirements. I think it is not necessary now since i found the real reason for the cellular issues.
When I changed another SIM card, it works flawlessly.

johnnyhoang said:
Sorry for misunderstanding.
I have found the reason why the cellular issues comes out. It is made by the SIM card itself, not the baseband version or the stock firmware version as you have said. I was wrong when i think that it come from the software or stock firmware. Now i found out the reason for that. Sincerely apologize to you.
Anyways thanks for noticing the recquirements. I think it is not necessary now since i found the real reason for the cellular issues.
When I changed another SIM card, it works flawlessly.
Click to expand...
Click to collapse
great stuff and thx for the feedback!

It ok, but google services framework stop. Fash zip Dolby Atmos (DAP_r6.5.zip) work Vanced manager install Youtube Vancednon root work. addonsu-14.1-arm-signed.zip work. VOLUME+BOOSTING+SOUND+(Very+Loud).zip work

binhdt said:
It ok, but google services framework stop. Can not flash zip Dolby Atmos, Vanced manager can not install Youtube Vanced
Click to expand...
Click to collapse
apps which require google crap will not work on /e/. That is by design..
You can browse the e foundation forum to find alternatives though.
How To's: https://doc.e.foundation/how-tos/
General Forum: https://community.e.foundation/
--> e.g a quick search here shows a bunch of alternatives for youtube: https://community.e.foundation/t/alternative-to-youtube/23703/10
or here another huge listing: https://github.com/tycrek/degoogle
Other alternatives: https://community.e.foundation/t/ho...urce-alternatives-of-your-apps-services/13616
.-

steadfasterX said:
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of LineageOS
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds UNOFFICIAL?
There are no differences. its pure /e/. "just" build on my server
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Camera does work but only for photo, i.e. video recording fails.
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP (recommended) build.
Do a full (i.e. Nandroid) backup before doing anything!
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? STOOOOOOP! NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easiest way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/nougat/gtexslte/
If you have a previous version of my(!) /e/ ROM installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
search results from this thread: click
Support
Of course in this thread but also by Telegram.
I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
jedld, really he did a great job and making this project possible at first!
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
and all I forgot to mention ....!
Sources
build manifest
XDA:DevDB Information
gtexslte_eos-n_unofficial, ROM for the Samsung Galaxy Tab A series
Contributors
steadfasterX, jedld(!)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2020-11-18
Last Updated 2020-11-18
Click to expand...
Click to collapse
I just flashed it and looks very nice thank you, titanium backup force closed, is there any restriction?

hotmatua.parulian said:
I just flashed it and looks very nice thank you, titanium backup force closed, is there any restriction?
Click to expand...
Click to collapse
Should work. Follow FAQ #1 in the second post

[OFFICIAL] LineageOS 19.1 for the Google Pixel 4

{
"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"
}
Google Pixel 4
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Google Pixel 4.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
flame
flame - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.14

Great news! Thanks for bringing Android 12 to this device!
I just reading the installation instructions and there are some questions:
1. The instructions don't mention wiping the system/data partition. Does this mean that my device will work as before, that I will not have to reinstall my apps and data after upgrading? My device is neither rooted, nor do I use anything like Magisk.
2. The instructions say:
"Note: If you previously had any Google Apps add-on package installed on your device, you must install an updated package before the first boot of Android! If you did not have Google Apps installed, you must wipe the Data partition (or perform a factory reset) to install them."
That confuses me: when I installed LOS 18.1, I also installed the MtG package, that was available for the P4 at that time. After that, I never installed anything else via adb, I only updated what was offered in the PlayStore or by the OTA updater function.
How should I interpret that instruction:
A) I need to install the latest MtG, that is available for LOS 18.1, and then I can install LOS 19 plus MtG for LOS 19.
B) Installing LOS 19 plus the appropriate MtG at the same time (=before the first booting) is sufficient to make the system work again.
Thanks in advance for any help!

dvdram said:
Great news! Thanks for bringing Android 12 to this device!
.
.
.
Thanks in advance for any help!
Click to expand...
Click to collapse
Simply - boot into LOS 19 recovery
- Goto advance factory reset Format Data
- Then apply Update via ADB
- Reboot to recovery
- Apply MTG Packg [Gapps](https://wiki.lineageos.org/gapps.html) for LOS 19
- Boot into system

dvdram said:
Great news! Thanks for bringing Android 12 to this device!
I just reading the installation instructions and there are some questions:
1. The instructions don't mention wiping the system/data partition. Does this mean that my device will work as before, that I will not have to reinstall my apps and data after upgrading? My device is neither rooted, nor do I use anything like Magisk.
2. The instructions say:
"Note: If you previously had any Google Apps add-on package installed on your device, you must install an updated package before the first boot of Android! If you did not have Google Apps installed, you must wipe the Data partition (or perform a factory reset) to install them."
That confuses me: when I installed LOS 18.1, I also installed the MtG package, that was available for the P4 at that time. After that, I never installed anything else via adb, I only updated what was offered in the PlayStore or by the OTA updater function.
How should I interpret that instruction:
A) I need to install the latest MtG, that is available for LOS 18.1, and then I can install LOS 19 plus MtG for LOS 19.
B) Installing LOS 19 plus the appropriate MtG at the same time (=before the first booting) is sufficient to make the system work again.
Thanks in advance for any help!
Click to expand...
Click to collapse
reboot to recovery, flash newest ROM, reboot to recovery, flash MTG 12.1 - reboot to OS - done.

npjohnson said:
reboot to recovery, flash newest ROM, reboot to recovery, flash MTG 12.1 - reboot to OS - done.
Click to expand...
Click to collapse
So, no need to reinstall all personal apps and stuff?

dvdram said:
So, no need to reinstall all personal apps and stuff?
Click to expand...
Click to collapse
Correct. Again. Follow the wiki upgrade guide and all will be fine.

I had a problem with the March 17 update of my P4a. Thus, I didn't update the P4 that is also in my household. The problem is with visual voicemail failing. I created an issue here: https://gitlab.com/LineageOS/issues/android/-/issues/4523
Does anyone know if this also happened with the P4? I imagine the move to LOS19 would carry the same problem, since (I think) this update https://review.lineageos.org/c/LineageOS/android_packages_apps_Dialer/+/325978/ caused the issue.
Thanks for your work on this & keeping my old V20 useful.

npjohnson said:
Correct. Again. Follow the wiki upgrade guide and all will be fine.
Click to expand...
Click to collapse
That worked out very well. Thank you!
A few things I have not been able to figure out yet:
1. I can't find the quick setting tile for system profiles.
2. If the lockscreen's clock is set *not* to use two lines, it sticks to the upper left corner of the screen. The same is true for the "always-on-screen".
3. The owner's information used to be displayed directly beneath the clock and date, taking only one line. Now it is displayed at the button, taking more than one line.
4. How to change the white background when entering the unlock code?
I guess some, if not all of these things have not yet been implemented.

dvdram said:
That worked out very well. Thank you!
A few things I have not been able to figure out yet:
1. I can't find the quick setting tile for system profiles.
2. If the lockscreen's clock is set *not* to use two lines, it sticks to the upper left corner of the screen. The same is true for the "always-on-screen".
3. The owner's information used to be displayed directly beneath the clock and date, taking only one line. Now it is displayed at the button, taking more than one line.
4. How to change the white background when entering the unlock code?
I guess some, if not all of these things have not yet been implemented.
Click to expand...
Click to collapse
1.search for "Profiles" they're there
2. Intentional
3. An android 12 thing.
4. Don't think you can.

npjohnson said:
1.search for "Profiles" they're there
2. Intentional
3. An android 12 thing.
4. Don't think you can.
Click to expand...
Click to collapse
4: It was possible in A11.
3: Well, it looked better in A11.
2: Hm, why?
1: The system profiles are usable, there's just no tile for the quick settings. These are all quick setting tiles that I can see:

Hello guys...does this rom support VoLTE or VoWi-Fi? I don't know why, but if i insert the same SIM into my other phone, i have both of these services active...but not in my Pixel phone.

aresbv2000 said:
Hello guys...does this rom support VoLTE or VoWi-Fi? I don't know why, but if i insert the same SIM into my other phone, i have both of these services active...but not in my Pixel phone.
Click to expand...
Click to collapse
If stock supports it for your carrier, then yes. If not, no.

npjohnson said:
If stock supports it for your carrier, then yes. If not, no.
Click to expand...
Click to collapse
Thank you. So the answer is "No, it doesn't support VoLTE ot VoWi-Fi", since stock android 12.1 doesn't support . In my area the GSM signal is weak, VoWi-Fi was great on the other phone. So sad that Google decides to block some functions on different markets.

An old security issue has risen again: profiles should not switch while the device is locked.
Why? Because of this:
- create a profile with no screen lock.
- set a trigger for that profile: activate when connecting to a known wifi
- turn off wifi, switch to normal profile and make sure device is locked
- swipe down quick settings and activate wifi
- after a few seconds, wifi will connect, the new profile will be activated and the device will be unlocked without having to enter the unlock PIN!
I think this is a serious security issue, because any one who will find your "lost" phone and reaches the area covered by that specific wifi, will have instant access to your unlocked phone!

dvdram said:
An old security issue has risen again: profiles should not switch while the device is locked.
Why? Because of this:
- create a profile with no screen lock.
- set a trigger for that profile: activate when connecting to a known wifi
- turn off wifi, switch to normal profile and make sure device is locked
- swipe down quick settings and activate wifi
- after a few seconds, wifi will connect, the new profile will be activated and the device will be unlocked without having to enter the unlock PIN!
I think this is a serious security issue, because any one who will find your "lost" phone and reaches the area covered by that specific wifi, will have instant access to your unlocked phone!
Click to expand...
Click to collapse
That's intended behavior.
If you set up a profile to automatically unlock the device when you are at Wi-Fi, you can expect that anyone using the device would have that, how should we know it's out of your hands?

how should we know it's out of your hands?
Click to expand...
Click to collapse
That's exactly the point: you can't, but you also can not be sure that it's the rightful owner who holds the phone in his hands when the profile switches and the device unlocks!
I agree that there is a point in making things as convenient as possible for the user. But convenience and security exclude each other.
So, what about an extra option that, when activated, will not switch profiles while the device is locked? This option could be hidden in the developers options, so normal users are not even bothered to take care of it.
I remember this "feature" in LOS 16, and it was fixed, and I am surprised to see it again.

Thanks for the hard work. Will there be an update that bypass the screenlock when double press power button to launch the camera? In stock android 12 it doesn't require to unlock.

The camera app now stores its pictures in "pictures" instead of "dcim/camera". Is there a way to change this path to the old setting?

Starting with the very last 18.1 update, and continuing through now, with the 19.1 upgrade...
I can manually create shortcuts on the homescreen, but none of my apps can do it. In fact, when I did an OTA update of the last 18.1, it deleted all the widgets and shortcuts created by various apps. My browser cannot create shortcuts. Neither can the "Shelter" app, which I use to put a few "big brother" type apps into my work profile as a sandbox.
Am I missing some permission that I should change? What allows apps to create shortcuts?
Everything else works fine. Love this OS; been using it for years now!

npjohnson said:
Google Pixel 4
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Google Pixel 4.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
flame
flame - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.14
Click to expand...
Click to collapse
Perfect ROM for the Pixel 4, thank you so much!
Question though: is SOLI/RADAR working?
I can't find motion sense feature, and AOD only has the option to be on (or even off - no 'tap to wake' or motion sensing).
Cheers

Better Mobile App

welcome