Database Info

[ROM][UNOFFICIAL][7.1.2] OmniROM

{
"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"
}
OmniROM is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance, reliability and features over stock Android for your device. It's also about options, which is the beauty of Android.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
OmniROM 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.
All the source code for OmniROM is available in the OmniROM Github repo.
Homepage:
=================
http://omnirom.org/
Wiki:
=================
http://docs.omnirom.org/Main_Page
Gerrit:
=================
https://gerrit.omnirom.org/
Bugtracker:
=================
http://jira.omnirom.org
Use this thread to report bugs as this is UNOFFICIAL
IRC:
=================
irc.freenode.net #omnirom
Be Advised:
=================
Root access is not included by default. Please flash SuperSU for root (See below).
If problems arise from your use of custom kernels, "performance scripts", etc. etc., we can't be responsible.
Screenshots:
=================
http://abload.de/img/screenshot_20170814-2qlsi5.png
http://abload.de/img/screenshot_20170814-2mssai.png
Installation Instructions:
=================
First time installing OmniROM to your Shield Tablet or coming from another ROM:
- Read known issues and FAQs
- Make sure you're running a proper working Team Win Recovery Project (TWRP) - https://twrp.me/devices/nvidiahshieldtablet.html
- Copy GApps and OmniROM ZIPs to your SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Flash OmniROM zip from SDCard
- Flash GApps zip from SDCard
- Reboot
- Don't restore system data using Titanium Backup!
Upgrading from earlier version of OmniROM:
- Copy the OmniROM zip to your SDCard
- Boot into Recovery
- Flash the OmniROM zip from SDCard
- Reboot
Downloads:
=================
UNOFFICIAL builds
omni-7.1.2-20171110-shieldtablet-HOMEMADE.zip md5:196df454441117da0962015063573a95
omni-7.1.2-20170901-shieldtablet-HOMEMADE.zip md5:02b22807016a3e39d0b0e46986fb24d9
omni-7.1.2-20170818-shieldtablet-HOMEMADE.zip md5:1ebc771fa3626a2a2bd7e68d72df9f7b
omni-7.1.2-20170816-shieldtablet-HOMEMADE.zip md5:4710c3ec9347e1c9ca7dc4013fde0bbf
MIRROR: omni-7.1.2-20170816-shieldtablet-HOMEMADE.zip
Gapps: Open Gapps
http://opengapps.org/
SuperSU:
http://www.supersu.com/download
Device Source Code:
=================
Device trees:
https://github.com/Lolzen/android_device_nvidia_shieldtablet
https://github.com/Lolzen/android_device_nvidia_shield-common
Kernel:
https://github.com/Lolzen/android_kernel_nvidia_shield
Nvidia hardware:
https://github.com/Lolzen/android_hardware_nvidia_power
https://github.com/Lolzen/android_hardware_nvidia_thermal
https://github.com/Lolzen/android_hardware_nvidia_libstagefrighthw
Vendor blobs:
https://github.com/Lolzen/proprietary_vendor_nvidia
Credits:
=================
Steel01 for providing device trees and blob sources and doing an excellent job maintaining them
BitOBSessiOn and OmniROM folks for pointing me in the right direction getting past the Black Screen
OmniROM Project for code base and being #swag in General

Thanks ! The only problem is that the video is not working

marcostesvk said:
Thanks ! The only problem is that the video is not working
Click to expand...
Click to collapse
Thanks for reporting! Could you specify which app? I do have mixed results on this, on one hand YT / MX Player are working on the other one Clover can't play webM's.
I'll certainly look into it.

The YouTube app played only sound, and when I installed opengapps Pico or mini the Google play setup crashed. Bean gapps worked just fine. I am using original shield tablet wifi. Should I install k1 staging blob ?

marcostesvk said:
The YouTube app played only sound, and when I installed opengapps Pico or mini the Google play setup crashed. Bean gapps worked just fine. I am using original shield tablet wifi. Should I install k1 staging blob ?
Click to expand...
Click to collapse
I'd advice against that, personally.
However, i have a workaround for the videos. There's some problem with the hardware decoding, i still have to figure out why.
For now i simply disabled hardware decoders, the software decoding seems to work fine, but this isn't a fix by any means.
I'll add the link to the download once the upload finished.
added to OP
Another bug i've encountered is that the Shield Camera's pictures are distorted, however when you activate HDR everything is fine. Again, just a workaround for now. The alternative is to use AOSP Camera.

Charging issue fix available?
Hi. Any input on charging? I was able to flash the latest version but I see it doesn't want to charge above 88%, even when left plugged over night. Thanks very much for any input. Nvidia Shield Tablet, wifi, rooted.

fmcgregor said:
Hi. Any input on charging? I was able to flash the latest version but I see it doesn't want to charge above 88%, even when left plugged over night. Thanks very much for any input. Nvidia Shield Tablet, wifi, rooted.
Click to expand...
Click to collapse
Seems weird.
Does anybody else have this issue?

klo_lol said:
Seems weird.
Does anybody else have this issue?
Click to expand...
Click to collapse
Thanks for trying. And thanks to anyone for replying. In terms of self help, I downloaded some battery apps to see if they can re-align the battery so it can charge up to 100%. Still only charging up to 89%. Tried cleaning the input ports and the chargers. I have wiped cache partitions. I have the latest TWRP. I'm scared to try to re-flash because it was so difficult - "setup wizard keeps stopping."

you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!

klo_lol said:
you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!
Click to expand...
Click to collapse
I'm very VERY grateful for your replies. I will try the battery link tonight. I didn't update the blob from any OTAs. This tablet is the replacement tablet from the recall. I rooted it and I don't get any OTAs. Perhaps it's something I can get and flash? If so, I would gladly try it. Re. setup wizard, I always clean flash ROMs and in fact I wipe all twice for luck and then again after flashing Gapps. Setup wizard error popped up and you can't swipe down to get to the Settings or the wifi. On the 70th try (and after youtube videos and articles) of trying to quickly slide to the notification bar, I was able to slide down and get to Settings to turn on wifi (ie, the solution). Last thing I did was out of frustration (nothing was flashing, Tesla, Lineage 14.1, etc., and this came closest) I unplugged the charger while sliding down and suddenly the bar came down -coincidence? Don't know. You don't want that error, it's like the android on his back. Full disclosure, I had to go into the updater script file and delete the assert lines so I'd stop getting the TWRP Error 7. Which worked. Learned that from here https://www.youtube.com/watch?v=wed03948gcg. I'll report back. Thank you for your attention and sorry to be a PITA!

fmcgregor said:
I'm very VERY grateful for your replies. I will try the battery link tonight. I didn't update the blob from any OTAs. This tablet is the replacement tablet from the recall. I rooted it and I don't get any OTAs. Perhaps it's something I can get and flash? If so, I would gladly try it. Re. setup wizard, I always clean flash ROMs and in fact I wipe all twice for luck and then again after flashing Gapps. Setup wizard error popped up and you can't swipe down to get to the Settings or the wifi. On the 70th try (and after youtube videos and articles) of trying to quickly slide to the notification bar, I was able to slide down and get to Settings to turn on wifi (ie, the solution). Last thing I did was out of frustration (nothing was flashing, Tesla, Lineage 14.1, etc., and this came closest) I unplugged the charger while sliding down and suddenly the bar came down -coincidence? Don't know. You don't want that error, it's like the android on his back. Full disclosure, I had to go into the updater script file and delete the assert lines so I'd stop getting the TWRP Error 7. Which worked. Learned that from here https://www.youtube.com/watch?v=wed03948gcg. I'll report back. Thank you for your attention and sorry to be a PITA!
Click to expand...
Click to collapse
I'm grateful for the feedback too, no worries!
You can get any OTA here https://developer.nvidia.com/shield-open-source directly from nvidia, labeled recovery images.
Inside the zip are instructions, but the most important parts are the blob and bootloader.
I sincerly hope this fixes any issues.
Regarding gapps: that truly sounds like hell. I'll do a backup and clean flash probably tomorrow. I'll report back on that matter when i have some details.
You are on the latest TWRP, is suppose?

klo_lol said:
I'm grateful for the feedback too, no worries!
You can get any OTA here https://developer.nvidia.com/shield-open-source directly from nvidia, labeled recovery images.
Inside the zip are instructions, but the most important parts are the blob and bootloader.
I sincerly hope this fixes any issues.
Regarding gapps: that truly sounds like hell. I'll do a backup and clean flash probably tomorrow. I'll report back on that matter when i have some details.
You are on the latest TWRP, is suppose?
Click to expand...
Click to collapse
Yes TWRP 3.1.1-1. Thx very much for the OTA link. Just fyi, the battery zip link was dead. But I'll find a working link now that I know the general name..

klo_lol said:
you could try if this will make any difference, provided by BitOBsessiOn: https://www.androidfilehost.com/?fid=24591000424962292
Did you update the blob from the latest OTA for your Tablet (OG/K1)?
I honestly have no idea otherwise.
In terms of setup wizard, as you are not the only one having this problem apparently. Did you clean flash (aka wiping all necessary partitions) prior to flashing omni?
I personally didn't have any crash setting it up, but that may be sheer luck.. i've seen commits from Steel01 to Lineage which adress that issue, but i want to make as less changes in the general codebase as possible.
As an alternative you can use Bean gapps as marcostesvk pointed out. I may change this in OP if everbody has problems with the setup wizard.
Thanks for the feedback guys!
Click to expand...
Click to collapse
Hi, just an update. I re-flashed and used bean gapps this time. No problems this time, but the battery still won't charge above 89%. Just as a by the way, the clock and date start up at factory until I get it on the wifi and it syncs. Every time. If there's no wifi, it's set to Dec. 31, 2012. Anyone else with this?

uploaded a new build. Link in OP.
No major changes, just up2date with omni source as of today

new build in OP.
*updated with latest omni 7.1 changes
*updated with some device changes from Aaron Kling
*updated kernel with latest nvidia kernel sources
i'm still bumping my head against a wall why hwencoders seem to have some sort of problems. You can play media, it's just not working with the configs it's supposed to.

M7+M7vzw+M7spr AICP-13.1-O 8.1 UNOFFICIAL BUILDS

{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LAOS) we are now LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors/bugs to them!!
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. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
 @maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.1
Download link m7: https://www.androidfilehost.com/?w=files&flid=239910
Download link m7vzw: https://www.androidfilehost.com/?w=files&flid=238220
Download link m7spr: https://www.androidfilehost.com/?w=files&flid=239908
Full Changelog link: http://dwnld.aicp-rom.com/
Google Apps:
(link the best one for your device, there are several variants out there right now, pico/nano gapps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You will need to use the version arm64/arm/whatever for SDK 27.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot", then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash, and then reboot.
Using the ROM:
Q. How do I enable software buttons?
A. Go to Aicp Extras/Navigation bar, and enable it.
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I keep losing root with Magisk, how do I fix it?
A. Check this out. If that doesn't work for you, ask for help in this thread, read or ask in the Magisk thread on XDA or just re-flash Magisk!
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the deivce, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
KERNEL:
The kernel in this ROM follows LAOS source with custom additions.
PREREQUISITE FOR OTA:
To be able to flash using the built-in OTA app, TWRP recovery is needed.
You can still use the LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. The Zipfile gets saved in the "aicp_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!​
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/icxj1/android_kernel_htc_msm8960/tree/o8.1
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
 @icxj1
 @alial04
 @tathanhlam66
ROM OS Version: 8.1.x Oreo
Kernel: Linux 3.4.113
Version Information: Development
Status: UNOFFICIAL
Release Date: 02-28-2018
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
HTC ONE M7ul,wlv,wls, ROM for the HTC One (m7)
Contributors
icxj1, alial04
Source Code: https://github.com/AICP/platform_manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: All of the above
Version Information
Status: Testing
Created 2018-02-28
Last Updated 2018-02-27

[/ATTACH][/ATTACH]

This ROM is testing & development. I know it must be hard for some to comprehend, the source is not complete yet. And the more they advance the less compatible m7 becomes.
Please report bugs with logs! No need to report what works on N ROM that does not work on O. M7 is not compatible for Oreo & i have many modifications to make it work. If you cannot live with a few bugs for awhile then GTFO! I do not get paid to maintain or develop so I don't want to here your pissing & moaning about an piece of **** obsolete device.
Bugs= "system process isn't responding" anr warning on boot. Select wait & carry on. This is caused by system partition not being mounted early enough in the boot process. 8.0+ expects an early mounted system partition. This is handled in the kernel by use of a separated dts, our kernel does not support dts for m7.
Lock screen with pin or password causing problems for some user's. not sure the entire issue, but reports of waiting up to 5 minutes to unlock. ??? send logs on this please.
Rooted devices must enable d2tw & pocket mode in kernel aduitor to fix proximity wake not working on outgoing phone call, (when screen is black dt2w it). Not an issue on non-rooted devices.
It is pointless to post here, most don't read it & will report the same bugs over & over in thread.

Should have ffcamera in this one & mobile settings partialy fixed, no data usage info & quick settings tile will crash. please do not report these bugs, i already have logs for them. enjoy!
m7 += https://www.androidfilehost.com/?fid=673956719939822539
m7vzw += https://www.androidfilehost.com/?fid=890129502657586018
m7spr += https://www.androidfilehost.com/?fid=746010030569956907

Can you guys make a kernel with wake gestures included?

lucyr03 said:
Can you guys make a kernel with wake gestures included?
Click to expand...
Click to collapse
They are already working on it but it makes some problems with oreo. If it is working they will release it.

Hi @icxj1
Thanks for the developement work!
May I ask,...? What's about Google certification? PlayStore says: "not certified".
And Magisk says: "basicIntegrety: true" but "ctsProfile: false"
Will you even work on that? That would be great. Thank you very much.
samhhmobil

samhhmobil said:
Hi @icxj1
Thanks for the developement work!
May I ask,...? What's about Google certification? PlayStore says: "not certified".
And Magisk says: "basicIntegrety: true" but "ctsProfile: false"
Will you even work on that? That would be great. Thank you very much.
samhhmobil
Click to expand...
Click to collapse
Gapps are beta, search their unofficial thread & see if you can find anything. And m7 will probably have to start using the magisk universal cts module. Search magisk modules for zip.
https://forum.xda-developers.com/an...cial-opengapps-builds-android-t3743495/page28

samhhmobil said:
Hi @icxj1
Thanks for the developement work!
May I ask,...? What's about Google certification? PlayStore says: "not certified".
And Magisk says: "basicIntegrety: true" but "ctsProfile: false"
Will you even work on that? That would be great. Thank you very much.
samhhmobil
Click to expand...
Click to collapse
Flash this zip in twrp to fix safetynet, I tested it and working fine on this rom.
https://www.androidfilehost.com/?fid=962187416754455235

first of all, thx for sharing all the work, the rom (20180228) works very smooth and definitely usable this time. besides the known bugs, i've also noticed (so far) problem with the proximity sensor (not working incalls and cpuz), wifi doesn't reconnect when registered network becomes visible (i have to turn it on and off to get it going), some wifi drops (occasionally) and wifi disconnecting while sleep (also occasionally).
sorry no logs, will do them when can, just wanted to say thank you!
edit: also, i have to reinsert the sim card upon restart.

olivrd said:
first of all, thx for sharing all the work, the rom (20180228) works very smooth and definitely usable this time. besides the known bugs, i've also noticed (so far) problem with the proximity sensor (not working incalls and cpuz), wifi doesn't reconnect when registered network becomes visible (i have to turn it on and off to get it going), some wifi drops (occasionally) and wifi disconnecting while sleep (also occasionally).
sorry no logs, will do them when can, just wanted to say thank you!
edit: also, i have to reinsert the sim card when os booted.
Click to expand...
Click to collapse
This device, the m7 allways had wifi problems even with stock rom it drops sometimes and doesnt connect when a known network is around sometimes. That must be related to the hardware because it was in all android versions from 4.1.2 up to 8.1 in stock and all custom roms the same no matter which firmware is used stock sense or gpe.

olivrd said:
first of all, thx for sharing all the work, the rom (20180228) works very smooth and definitely usable this time. besides the known bugs, i've also noticed (so far) problem with the proximity sensor (not working incalls and cpuz), wifi doesn't reconnect when registered network becomes visible (i have to turn it on and off to get it going), some wifi drops (occasionally) and wifi disconnecting while sleep (also occasionally).
sorry no logs, will do them when can, just wanted to say thank you!
edit: also, i have to reinsert the sim card upon restart.
Click to expand...
Click to collapse
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
---------- Post added at 21:21 ---------- Previous post was at 21:20 ----------
Did anyone managed to install V4A on this rom? I installed it but the driver isn't functional.

lucyr03 said:
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
Click to expand...
Click to collapse
Aha, good idea. It seems this sim card issue is only happening on m7 if build m7vzw first. Next builds I will make clean & run m7 first then will see if problem still exist.

lucyr03 said:
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
---------- Post added at 21:21 ---------- Previous post was at 21:20 ----------
Did anyone managed to install V4A on this rom? I installed it but the driver isn't functional.
Click to expand...
Click to collapse
Is that video related?

icxj1 said:
Is that video related?
Click to expand...
Click to collapse
I don't know about video, it just shows driver: abnormal, neon: no, audio processing: unsupported and of course any settings have no effect.

lucyr03 said:
I don't know about video, it just shows driver: abnormal, neon: no, audio processing: unsupported and of course any settings have no effect.
Click to expand...
Click to collapse
Aha, oK. I will look into it. Thanks

lucyr03 said:
Flash this zip in twrp to fix safetynet, I tested it and working fine on this rom.
https://www.androidfilehost.com/?fid=962187416754455235
Click to expand...
Click to collapse
Thanks, THAT'S IT. Great.
---------- Post added at 08:13 PM ---------- Previous post was at 08:00 PM ----------
I see, it's working very well.
- Video recording in Camera app is not working (as told before by some other member).
- GPS is marked as "Supported" but Enabled "No", and not possible to enable (but working GPS is important to me, so we have to wait for the devs and their great work).
- IR is marked as "Not supported" - even it is in the device -, sigh (it's not really very important to me, but it's "nice to have").
- Mobile data work correctly, but it's impossible yet to switch it off.
- WiFi works to me, even reconnects.
Thanks again,
samhhmobil

lucyr03 said:
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
Click to expand...
Click to collapse
tried this, but not working, still had to reinsert it, at least on my device (international version)

olivrd said:
tried this, but not working, still had to reinsert it, at least on my device (international version)
Click to expand...
Click to collapse
I have international version too but with GPE firmware.
Sent from my OnePlus 2 using XDA Labs

lucyr03 said:
I have international version too but with GPE firmware.
Click to expand...
Click to collapse
same here

[ROM][Pie][OFFICIAL] Resurrection Remix v7.0.2 [evert]

{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
​
Make sure you have the latest TWRP.img
Download the latest RR-P zip and GApps zip (opengapps nano or smaller)
fastboot boot twrp.img (NEW!! See post #2 for info on installing TWRP)
If coming from stock for the first time, flash copy-partitions-AB.zip from second post (It takes a backup of active slot to inactive slot)
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (Note: this will wipe internal storage)
Flash latest RR-P.zip
Reboot and let the ROM boot once (it is necessary to reboot between ROM flash and GApps/Addon flash due to slot-swap logic)
Reboot back to bootloader and fastboot boot twrp.img again
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (You may be able to get away with just doing a factory reset at this point, but that's on you to try)
Flash Google Apps package (optional)
Flash Magisk (also optional) (Note: If Magisk doesn't stick after setting up your device, fastboot boot twrp.img one last time and flash it again, no need to wipe anything)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.​
​
XDA:DevDB Information
Resurrection Remix Pie v7.0.2, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi, rahulsnair, RR Team
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2019-02-25
Created 2019-02-26
Last Updated 2019-04-21

Copy partitions zip & TWRP installation info
[size=+2]Important info, please read...[/size]
Starting from build 20190414, encryption is disabled (temporarily) and you must clean flash
The new TWRP version now supports decryption on Pie when booting twrp. However, I have updated TWRP to include the new magisk repacktools which allows users to download and install one twrp.img without the need of an installer zip. The reason behind releasing the ROM with encryption disabled? If you were to try to install TWRP while using an encrypted ROM, you would end up in a bootloop that would bring you back to TWRP. But, install TWRP on a ROM with encryption disabled, and everything works as expected.
[size=+1]TWRP Installation[/size]
-> TWRP download || twrp-3.3.0-v2-evert-jlb.img
->>> The twrp.img you download above will also be the same twrp.img you will install, so make sure to put a copy on your device as well
-> Boot twrp
Code:
fastboot boot twrp-3.3.0-v2-evert-jlb.img
-> In TWRP, choose Advanced / Install Recovery Ramdisk
-> Select the twrp-3.3.0-v2-evert-jlb.img
->>> At this point twrp will automagically unpack your boot.img and the twrp.img, swap out the recovery-ramdisk, and repack your boot.img. When this process completes, twrp will be permanently installed.
->>> Always flash Magisk AFTER you've installed twrp
-> Reboot and enjoy. You should now be able to reboot to recovery from the Power Menu!!
DO NOT try to install twrp on an encrypted rom. You will most likely end up in a bootloop, you have been warned!
Important
To keep TWRP installed between ROM updates, there is a Magisk Module named "TWRP A/B Retention Script" by @osm0sis. Search for it within Magisk Manager Downloads section. You'll want to flash this script zip after each OTA has installed, but before you install Magisk to the Inactive Slot from Manager.
[size=+1]Coming from stock?[/size]
Make sure to flash the copy-partitions-AB.zip in twrp before you do anything else. You can download it from the attachment below...

Reserved

Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.

Woks awesome, thank you dev

Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.

WYPIERDAALAAC said:
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Click to expand...
Click to collapse
The install instructions in the OP are generic, and don't necessarily apply for this device. You're better off following the install instructions from Lineage-16.0. I will update the OP with proper install instructions when I have some time asap.
LDMx96 said:
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
Click to expand...
Click to collapse
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.

Jleeblanch said:
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Click to expand...
Click to collapse
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.

Awesome! I'm using magisk with Ainur Sauron and Viper, working flawlessly! Everything works pretty well so far. Thanks for the amazing job!
I flashed it over the stock pie without wiping system, only factory reset. I don't know if this helps because I'm still a newbie P, just sharing!
RR rocks!

LDMx96 said:
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Click to expand...
Click to collapse
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.

Jleeblanch said:
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Click to expand...
Click to collapse
No worries mate, I'll look forward to the update on the weekend then.
Thanks a bunch.

Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
LDMx96 said:
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
Click to expand...
Click to collapse
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
There is a manual or some guide to do that? Please

asesinodilusion said:
There is a manual or some guide to do that? Please
Click to expand...
Click to collapse
There are basic instructions in the OP to take logs on the device using Matlog. There is also a decent tutorial here on xda: [Tutorial] How To Logcat

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
https://www.dropbox.com/s/rqz2t7d57epq7i9/data.txt?dl=0
I hope this help

BT Calling not working
Hello together,
i installed th RR Rom on my phone and everything seems to be fine.
BUT the only thing is, "Bluetooth Calling" does not work. I tried it with to different Bluetooth devices, my oneplus wireless bullets, and my car.
No Microphone and no Sound is Working, very rare.
But when i do BT Calling with SIGNAL or VOIP app CSipSimple everthing is fine. It looks like, that the only problem is the telefone app itself from android pie.
Before i used the [ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] and BT Calling was working fine!
Does someone have a tip for me, where i can take a look?
Thanks a lot.
Greetings

It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk

titofariasl said:
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
Click to expand...
Click to collapse
Is there any way of improving in-call audio quality? There is just too much background noise.

[ROM][OFFICIAL][hotdogb][10] RESURRECTION REMIX [Sept 9 2020]

[10.0][OFFICIAL]Resurrection Remix v8.x [device_code]
{
"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"
}
Resurrection Remix Q
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters. For 7T: Be sure to be on latest oos, beta or stable is fine (flash both slots prior to installing the rom)
Download the latest Resurrection Remix Rom (currently on V8.6)
(7T builds gave gapps included) so disregard flashing gapps.)
You can use either twrp (mauronfrios latest or Chinese) to flash the rom.
Additionally - you can unpack the bin that is in the zip and fastboot flash as many other roms. SEE POST#4!! Importantly, after flashing, no matter the method, once you see the RR boot logo, force reboot to bootloader mode, and use the buttons to cycle to recovery. Select this as it will now reboot to the roms recovery. Go to wipe data. Wipe data and now reboot. This is mandatory if you flash via twrp or want to run f2fs vs ext4; bc the rom will run very well on f2fs as it is much faster file system than ext4.( Once you format after the first flash.) If using twrp, the first boot sets it as this but unless a format is done, it will not boot. So, do not skip this step. After the data wipe and rebooting, the rom boots up in a few Mins. If it doesn't boot in 5mins. You may have made a mistake and in that case reflash stock to both slots and try again.
Yes, Ota updates work fine, be sure to go to updater and prioritize update process. I usually send a build every couple days.
You can retain root by after the download and install occurs but before reboot, launching magisk manager and installing to opposite slot and then rebooting.
**Ota will not work unless RR is on both slots before taking ota. To fix that, after you get it booted, boot to bootloader and fastboot set_active other, and reflash via fastboot. OR if you used twrp, flash the ota again and it puts it on the opposite slot.
Neutrino Kernel is built in-line, latest Hoth 1.95
​
Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest Resurrection Remix Rom & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ResurrectionRemix Rom
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.​
​

Current download and details:https://forum.xda-developers.com/showpost.php?p=83469869&postcount=465
7T TG Chat https://t.me/rr_op7t
Payload Dumper
https://drive.google.com/open?id=1Q5Cq9nAXWvjw9z6wgCDfQi40qk4mw3ut

Thanks for this! Glad to see you here as well

Here are some more detailed instructions by my long time constituent @aer0zer0 thank youuuu!!!
how to extract a payload and flash a rom for noobs, windows only
pre-requisites:
1. In general, you want to have the SAME version of OOS on both sides. Im not going to go into detail on how to MSM, and flash a full OTA locally, reboot, then flash the same OTA locally again and reboot.
2. payload dumper for windows: https://drive.google.com/file/d/1Q5Cq9nAXWvjw9z6wgCDfQi40qk4mw3ut/view?usp=sharing its windows 64 bit only
3. Latest ADB/Fastboot binaries: when flashing using using a script, and you see errors such as system partition cannot be found, etc... your binaries are old, most likely cause by some ghetto version minimal adb/fastboot thats jank. To verify where your adb/fastboot is running from, in a shell, type fastboot --version this will tell you where you resident adb/fastboot binaries are running from. The link to updates binaries is here https://developer.android.com/studio/releases/platform-tools select the windows SDK version. Once downloaded, copy and paste them over top of the ones being used from the fastboot --version output.
4. a bat file to flash all the images you are dumping. https://drive.google.com/file/d/1HW1Q82wpsnBPUcPkAnXO-tQjVIWSZ_oQ/view?usp=sharing this wipes, goes to fastbootd, will flash all the images from the payload.bin dump to both sides, wipes, and sets it to boot from slot A.
5. lots of common sense
Instuctions
1. extract the payload dumper somewhere on your PC, you will see an "IN" folder, "OUT" folder, and an executable.
2. extract the payload.bin file from the rom.zip you wish to install, and place it in the "IN" folder.
3. run the payload dumper exectuable, a shell will pop up, showing the images being extracted.
4. once the shell closes, the images are all succesfully unpacked. Copy those images in the "OUT" folder to whereevr you would like to store your rom.
5. copy/paste the bat file wherever you placed your images.
6. reboot your phone to fastboot, plug it into the PC, and run the bat.
7. process takes 4-5 minutes, sit back, it will then reboot back to fastboot.
8. start the phone from fastboot, and wait for your new rom to boot.
9. finish and enjoy!

Also, there is no real bugs. On occasion one may think there is a bug, and if there is in fact one, we work promptly to resolve it as a team. Typically, one thinks a bug is a bug, but the rom has so many features, it is just a conflicting setting most likely, I implore you all to exercise trial and error. If something was fine and you fiddled with settings, go unfiddle and see what could make something not work. We could not foolproof all features to not conflict on the occasion if we get kinda crazy with what we expect our device and it's software to be able to do. All works flawlessly. Enjoy the rom and thanks to my colleagues and my friends who have always been there in this wonderful android world, never quick to judge, always quicker to help and teach. Never from the class of elitist android dev who is "too cool" to just be nice. Thanks guys.
The names below have helped me in numerous ways over the years, thanks for the help, support, and overall non-douchebaggery activities:
KangaroosterMeadows-Where the magic happens
@wrongway213
@aer0zer0
@xstefen
@NoSpamDan
@varund7726
@Freak07
@return.of.octobot
@abalam
@hondajohn
@Neo
@unixandria
@fKm
@lil_kujo
@kdp162
@omariscal1019
@DeathStroke
@risasuke
JackEagle-his guides and advice in chat, Anthony P, DPryor, Cody S, and everyone else I haven't named. Thanks also go to AOSiP- for solid trees that most of us all use.

Congrats @FullOfHell what a great rom

Just installed it and I'm liking every bit of it thank you @FullOfHell!

I am touched! I was losing hope for this device. thank you!

Thanks! Will try it soon.
Enviado de meu HD1903 usando o Tapatalk

Face unlock included? How about Fp? Works great, even with low brightness?

Kollachi said:
Face unlock included? How about Fp? Works great, even with low brightness?
Click to expand...
Click to collapse
yes faceunlock is included and fingerprint works flawlessly, low light, no light, any situation

Kollachi said:
Face unlock included? How about Fp? Works great, even with low brightness?
Click to expand...
Click to collapse
Yes fp works great even with nightlight on , face unlock is also included . It's a super solid rom

lil_kujo said:
Yes fp works great even with nightlight on , face unlock is also included . It's a super solid rom
Click to expand...
Click to collapse
Thanks man appreciate it. Hope you enjoy it

The news of a stable ROM coming to 7T just made my day. I want to heartily thanks the developer who invested their told in building this goodness.
Also would payment apps work on this ROM? Maybe someone could confirm the same? I am preety new to the ROM scene these days but have some past experience ages ago, I have heard Magisk safety net would work?
Also I wouldllike to know do stable ROMs like these have om par camera performance as the stock builds of OOS does? Or can we make it work just as better with installing a supported Gcam build here from forums?

AnkeshReborn said:
The news of a stable ROM coming to 7T just made my day. I want to heartily thanks the developer who invested their told in building this goodness.
Also would payment apps work on this ROM? Maybe someone could confirm the same? I am preety new to the ROM scene these days but have some past experience ages ago, I have heard Magisk safety net would work?
Also I wouldllike to know do stable ROMs like these have om par camera performance as the stock builds of OOS does? Or can we make it work just as better with installing a supported Gcam build here from forums?
Click to expand...
Click to collapse
I recommend latest arnovo gcam for optimum photography.
I don't know if gpay works as I only use PayPal, but safety net passes. Happy it made your day. Enjoy

FullOfHell said:
I recommend latest arnovo gcam for optimum photography.
I don't know if gpay works as I only use PayPal, but safety net passes. Happy it made your day. Enjoy
Click to expand...
Click to collapse
Great to know the safety net passes.
Would just leave a message here asking if any forum member based from India installing RR can confirm if the payment apps like PayTM, PhonePe and the likes of it work? It's the just last thing that's stopping me from getting this beauty on 7T.

Along with info of banking apps, i would also like to know if this has auto call recording feature ? 90hz display support ?

Also I would like to know the proper install instructions for this ROM, I tried searching for this but feels like I'm a bit lost. Thank you for helping out :victory

shetty_chadda said:
Along with info of banking apps, i would also like to know if this has auto call recording feature ?
Click to expand...
Click to collapse
No call recording feature as the lineage dialer is overridden for gapps, ie google dialer. Find a 3rd party app/mod. Sorry, I tried adding the option to allow the user to pick los dialer or google dialer, it but broke other things the majority of users need over call recording. Yes, 90hz support. 60/90 or auto

AnkeshReborn said:
Also I would like to know the proper install instructions for this ROM, I tried searching for this but feels like I'm a bit lost. Thank you for helping out :victory
Click to expand...
Click to collapse
It's easy. Use twrp, or unpack the bin file in the rom and flash with fastboot. same as other roms, just must format after install and reboot.

[ROM][OFFICIAL][11] LineageOS 18.1 for Galaxy Note10/Note10+/Note10+ 5G Exynos

{
"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 is a free, community built, aftermarket firmware distribution of Android 11, 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.
Instructions:
Follow the instructions on the wiki page for your device https://wiki.lineageos.org/devices/#samsung
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
GApps: https://wiki.lineageos.org/gapps.html
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 /proc/last_kmsg. (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:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820

reserved

reserved

What is different between this build and your previous one ?

Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available

Vishnarov said:
What is different between this build and your previous one ?
Click to expand...
Click to collapse
Read the thread's title ... It's official now.
[email protected] said:
Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available
Click to expand...
Click to collapse
No, sorry hardware is too different.

builds have been removed from the lineage os website?

Enddo said:
builds have been removed from the lineage os website?
Click to expand...
Click to collapse
Yes, see this for the reason
This affected all devices so builds of last few days were pulled and sadly we had only that one build yet
There will be new ones next week

Does the build support hardware encryption or software encryption?

You should put what models this is for as to avoid confusion

just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch

Enddo said:
just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch
Click to expand...
Click to collapse
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.

CerebralFlex said:
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.
Click to expand...
Click to collapse
certainly no locked bootloader here (have had it unlocked since right after I bought it at launch)
but yea, I'm going to try and reflash the ROM and start from scratch. I was on an outdated version of ONe UI (maybe from December) so maybe that was part of the issue
EDIT - oddly enough, I couldn't get LOS recovery installed via Odin. I tried, got success messages, but a reboot into recovery mode just showed stock recovery (I wasn't missing the button combo, to my knowledge). tried a few times before going back to using heimdall
the second attempt (with a fresh install of OneUI's latest firmware) helped me get past that vbmeta error with heimdall
got LOS recovery installed, the ROM sideloaded, and I'm up and running
thanks for the hard work @Linux4 (and all others involved in working on lineageos)

First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?

Phosphoros said:
First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?
Click to expand...
Click to collapse
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)

is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before

Enddo said:
is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before
Click to expand...
Click to collapse
It is not broken or whatever, see this from my telegram group in case you just don't figure it out on your own:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
All samsung devices using FOD have that issue it seems, only on first enrollment tho, after that it's completely fine

Linux4 said:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
EDIT - was able to get it working through a factory reset with the 'tap fast' being the key thing. it needs to fail that first attempt or something?
but it's quite quick once that hassle is over with

Enddo said:
this worked for me on my first install. describes my exact experience
but yea, it's not working right now. you need a logcat or something?
it's immediately throwing up the enrollment error message right when it attempts the first scan (every time)
Click to expand...
Click to collapse
No need for a logcat, it does work, for retrying you will need to close settings completely, just going *back* is not enough (HAL will stay in that error state)
I'm 100% sure you didn't do so also it works for everyone else

Linux4 said:
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)
Click to expand...
Click to collapse
Ok, thought about waiting for this ... thanks for confirming it!