yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Themes, Apps, and Mods] gettinwicked:
What all themes are darker than stock, but not blacked out like swift dark/black? I'm running swift dark right now, and I dig it, especially since it themes a lot of apps too, but it's a little too dark. Maybe something a little more in between (even a little darker than in the middle), with a little more color? I'm new to this substratum thing, so please bear with me.

Thanks!
[Google Pixel 2 XL Themes, Apps, and Mods] thereal_bigjake:
Dark Infusion you can choose your background, card, primary and accent colors from a bunch of choices and if it's not in the theme I'll add it ? It's a paid theme but I give away codes on the Substratum G+ every update.
[Google Pixel 2 XL Themes, Apps, and Mods] gettinwicked:
That looks pretty bada$$! I'll give it whirl! Thanks! (I'll pay too btw. I like to support our devs :) )
[Google Pixel 2 XL Themes, Apps, and Mods] thereal_bigjake:
Thanks, it's a constant work in progress so of you see issues don't be afraid to report them ?.
[Google Pixel 2 XL Themes, Apps, and Mods] gettinwicked:
Okay, soooo, bought the theme, disabled and uninstalled swift black, rebooted. Went through dark infusion and hit install and enable. Reboot. Nothing. Reboot again. Nothing. (Checked display in settings to make sure I didn't need to enable it there too, didn't show anything) It showed nothing installed in substratum. Went to substratum recovery and had it uninstall all overlays just in case. Went and redid swift black, rebooted. I then had BOTH overlays installed and enabled... No idea how that was possible. So, went through the uninstall and disable process again, recovery, uninstall all overlays again. Reboot twice. Tried swift dark again. Now it doesn't work. Tried 3 times. Uninstalled dark infusion, tried 3 more times. Nothing. Works... Any ideas here? Now I can't seem to do anything with substratum...
[Google Pixel 2 XL Themes, Apps, and Mods] Prattham:
Might wanna uninstall amd re install substratum
[Google Pixel 2 XL Themes, Apps, and Mods] Badger50:
You have to remember that substratum got borked a little after the March update. So, you have to "build and update" your overlays first, 3-4 at a time, then reboot. Then, go back to substratum manager and enable them :good:
[Google Pixel 2 XL Themes, Apps, and Mods] worldsoutro:
This is what I do and have no issues:

1) uninstall all overlays

2)update swift black with all other apps that need update

3) build and update all the new overlays I do all at once and never had an issue

4) reboot

5) enable overlays

6)reboot

Good to go
[Google Pixel 2 XL Themes, Apps, and Mods] imucarmen:
I'm on the Verizon Pixel 2XL using the latest April 5th update. Loving the look of my device now. Tried my best to get everything on a dark theme since I hate white themes and rarely use my phone outdoors, and even outdoors I can still see everything fine.

I'm using flux dark on most things except for settings I'm using Pi dark. I'm also using rounded UI theme to add more roundness to the notifications so they match the screen corners.

My launcher is Action pro with a custom Zooper widget.
[Google Pixel 2 XL Themes, Apps, and Mods] azpatterson3:
I like your set up. What did you check to get notifications to theme?
[Google Pixel 2 XL Themes, Apps, and Mods] imucarmen:
I'm using Flux dark to make them dark and to add the gap and to add that extra roundness I used Rounded UI.

I checked 'Android System' and 'System UI'.
[Google Pixel 2 XL Themes, Apps, and Mods] AwkwardUberHero:
Love this setup. I am going to try and mimic it on mine. Saw that you are from Va, I am as well. Located near Charlottesville, Va. :laugh:
[Google Pixel 2 XL Themes, Apps, and Mods] imucarmen:
Thanks. I'm between Williamsburg and Richmond -- about an hour and a half from Charlottesville.

The app I'm using for the rounded corners is called Rounded UI, not rounded corners.
[Google Pixel 2 XL Themes, Apps, and Mods] AwkwardUberHero:
Ah nice! That is a great area. The Substratum theme, is it called Flux - Substratum theme? Thanks again.
[Google Pixel 2 XL Themes, Apps, and Mods] Prattham:
That's right
[Google Pixel 2 XL Themes, Apps, and Mods] AwkwardUberHero:
Awesome. Thank you!
[Google Pixel 2 XL Themes, Apps, and Mods] imucarmen:
There is a flux light and dark. Also, the settings theme is from Pi dark. The flux theme has your accent color at the top of settings and Pi makes the whole thing dark which I prefer.
[Google Pixel 2 XL Themes, Apps, and Mods] cjrivera04:
Here are my screenshots and working themes. Using GSAM battery for circle battery in the left corner. FYI, I'm running a transparent theme. Hard to see in the pictures.
[Google Pixel 2 XL Themes, Apps, and Mods] arvylas:
Hi guys,

Is it possible to change the lock screen clock? I've changed the device font and now I get a box divider instead of the usual :

I'm on stock rooted rom.
[Google Pixel 2 XL Themes, Apps, and Mods] cjrivera04:
Look up the thread in the image below. These fonts have been fixed for the pixel 2 xl
[Google Pixel 2 XL Themes, Apps, and Mods] Mikkey81:
PI Dark Notification and Navbar, Pitch Black Google, Drive, and power Menu, Linear Android System and System UI, Outline and Mono Art... All, Rounded UI all. Running Validus...
[Google Pixel 2 XL Themes, Apps, and Mods] chadhoard:
Is there any work around to get Substratum working on Android P?
[Google Pixel 2 XL Themes, Apps, and Mods] Badger50:
Not ATM ?
[Google Pixel 2 XL Themes, Apps, and Mods] miked2332:
Android P Stock with flash kernel.

Substratum Valerie
[Google Pixel 2 XL Themes, Apps, and Mods] miked2332:
I use screen saver and substratum Valerie.
[Google Pixel 2 XL Themes, Apps, and Mods] Eduardo1974:
As of now is theming through Substratum/Andromeda on the Pixel 2 XL running Android Pie only through root?

Edit: I didn't see the same inquiry earlier in this thread. Sorry! Question answered!
[Google Pixel 2 XL Themes, Apps, and Mods] matique:
How did you get so many qs tiles? Is it linear android system and system ui? Can't find a post regarding it.
[Google Pixel 2 XL Themes, Apps, and Mods] Mikkey81:
99.9% chance I used substweaks on the playstore . https://play.google.com/store/apps/details?id=me.msfjarvis.substweaks. Thats your best bet anyway to add them. I don't recall whether that was a ROM setting with the lowboy qs settings pulldown. Its been a while since I've played with QS settings.

VZW PIXEL 2 XL
[Google Pixel 2 XL Themes, Apps, and Mods] Curiousn00b:
You can also give Tiles a shot. It's what I use for the things that stock rom doesn't have.

https://play.google.com/store/apps/details?id=com.rascarlo.quick.settings.tiles

Edit: Just remembered it was a paid app. You should read the description of the app for the full information, but it's worth it.
[Google Pixel 2 XL Themes, Apps, and Mods] Mikkey81:
Pitch Black Google APK, settings are swift Dark UI with Mono Art Settings tiles and Quick Settings. Colors are Spectrum.
[Samsung Galaxy S8 Questions and Answers] andrizmitnick:
would anyone share how i can properly add setting menu to SecSettings2.apk? when i try using apktool it always failed on compiling. i already specify my rom framework.

the file i've edited:

device_info_settings.xml @ res/xml folder

strings.xml @ res/values folder
[Huawei GX8] شرعا لا يجوز:
Hi everyone.. Update oreo will came the phone??
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
Lenovo Tab 3 8/TB3-850F

Question & Answer Forum

Link & General Resource Guide

RE: Stock & Custom ROM(s)​

INTRODUCTION & PURPOSE:

I have started this thread as a Q&A forum and general info guide for my Stock 6.0 ROM for the Lenovo Tab 3 8, and as a forum for my stock-based custom ROM which is nearing completion. In addition, I have posted some useful threads for this device below. It has been brought to my attention by XDA Senior Member [MENTION=7550078]pndwal[/MENTION], as well as other members, that topics regarding systemless rooting, dm-verity, force encryption, Trusted Execution Environment (/tee1 & /tee2), etc., need a dedicated forum for open discussion and brain-storming, all while adhering to XDA's policy of staying on topic in the device threads. In addition to the topics outlined, this forum welcomes any questions, concerns and colloquy regarding ROMs, kernels, recoveries, & other development for this device.

LENOVO TAB 3 8/TB3-850F LINKS:

Stock Android 6.0 ROM Thread: https://xdaforums.com/android/general/rom-lenovo-tab-3-8-tb3-850f-t3617594

Bootloader, TWRP & Rooting: https://xdaforums.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786/page17

Unbricking/Restoration Tutorial: https://xdaforums.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727

Stock Firmware Partition Images: https://xdaforums.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043

Lenovo Tab 3 8" User Manual (PDF)

for TB3-850F & TB3-850M: English: https://drive.google.com/file/d/18gCTfuZecJnlB0ddBIN02YPaDpuvmzov/view?usp=drivesdk

Lenovo File Manager (APK): https://xdaforums.com/android/general/app-lenovo-file-manager-lenovo-tab-3-8-t3706161

RULES:

Rule 1: Be respectful to XDA policies and to one another. We are all here to learn and to grow. The only stupid question is a question not asked;

Rule 2: Read Rule 1.
[Android Q&A, Help & Troubleshooting] pndwal:
A generous interpretation... Thanks for invitation. I'll be sure to come up with a curly one or two.

For now, could you give a rough idea of what needed changing to bypass force encryption? And also, reasons for pre-rooting? Thanks, PW.
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
Reasons for pre-rooting are merely as a convenience to the user. Many users will use the stock build I compiled and root themselves, while others will take the more convenient route and flash the ROM which is pre-rooted. The advantages of the rooted ROM are that it will be moderately debloated, deodexed, zipaligned, and will of course have BusyBox binaries pre-injected and the Magisk Systemless User Interface installed.

To bypass force encryption, I first needed to bypass dm-veriity. Both are enabled by default on this tablet within the ramdisk/fstab. So the boot image needed to be unpacked, the values of "1" enabling both dm-verity & force encryption needed to be changed to values of "0", thus disabling both features. The boot image was then repacked and then archived within my ROM installation package (zip).
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
I'd also like to take a poll to ask whether members want Viper4AndroidFX v2.5.0.5 (with NEON audio drivers) on the custom ROM, in lieu of the Dolby Digital Sound audio package that comes pre-installed on the tablet. Any input would be appreciated.
[Android Q&A, Help & Troubleshooting] pndwal:
Viper can be installed as a module in magisk. PW
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
Yes it can, but it breaks the stock camera completely, due to the SELinux policy mod which is installed by the module. If included as a feature of the ROM, I have a workaround which sets SELinux to permissive on boot, instead of permanently disabling the policy from within the kernel. This prevents breaking of the stock camera.
[Android Q&A, Help & Troubleshooting] pndwal:
I did that in past too. Don't think its needed now.

Viper working fine for me as Magisk module (phone and TB3-850f tablet). SELinux enforcing, camera working fine (incl. video), 2.5.0.4 driver, 2.5.0.5 app.

Seems SELinux policy change no longer required as V4A module for Magisk installs AML (Audio Modification Library) as Magisk framework which no longer requires permissive. Let me know if I'm missing something. PW.
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
You are pretty well correct. But, in order to enjoy the full spectrum of the NEON audio drivers, SELinux must go permissive. The Viper version I am speaking of was compiled by Deuteronomy Sound Technologies (and Arise) and is known as Viper4 AriseFX (a modded, themeable, and undoubtedly the most feature packed Viper package available for Android). The Viper module available on Magisk is a bare bones package, and when used in combination with my patched boot image (due to SELinux policy) it breaks the stock camera and causes other instabilities within the ROM.

I'm working also on a custom kernel for the TB3-850F, which will have some audio tweaks available from the kernel itself, as well as some tuneable governors, preset TCP congestion algorithms, etc.
[Android Q&A, Help & Troubleshooting] pndwal:
I see. Perhaps you could explain the benefits of neon audio - I wasn't aware.

Also, would permissive SELinux not break SafetyNet check? Thanks, PW.
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
Yes and no. Depending on how you set the SELinux policy. I've found that setting SELinux to permissive on boot only, by way of a third party app like Kernel Adiutor-Mod or The SELinux Toggler, does not break SafetyNet. However, permanently disabling SELinux as enforcing, by way of modding the kernel itself, has been reported to cause a SafetyNet fail on both custom and stock ROMs.

You raise a good question though, and it is a factor to which I'll be paying close attention during development for this tablet.

I think I've decided to include Viper4AriseFX in my ROM as optional, and available by flashing a separate zip installer subsequent to installing the ROM itself.
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
By the way [MENTION=7550078]pndwal[/MENTION], you seem to know your way around Android pretty well. What are some other features you would like to see in a custom built ROM for the Tab 3 8?
[Android Q&A, Help & Troubleshooting] pndwal:
Optional install sounds like a good idea, especially if SELinux permissive is optional to. I'm hesitant to use permissive environment as many apps etc require enforcing, and attempts to circumvent this, eg Magisk's ability to hide permissive etc, are reportedly not foolproof.

Not sure about attraction with Neon and ARISE, but seems permissive SELinux requirement to use these may be short-lived anyway. See post from today, at https://xdaforums.com/android/software/r-s-e-sound-systems-auditory-research-t3379709/page3125

problem:

NEON Enabled: No

Enabled: No

Status: Abnormal

ETC...

How solve it please?

Magisk 14.3 thats why. You need permissive. ARISE hasnt been updated for the new changes to how magisk handles selinux.

Just for now you'll need to switch to permissive to get viper to work

. Hopefully we'll have a build up soon to make it work, I know that ZackPTG and Ghost started to update it although i'm not sure on progress.

Hope it helps, PW.
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
I've got Viper4AriseFX fully functional with Magisk v14.3. SafetyNet pass. I'm using a method which does not permanently set SELinux to permissive, but which toggles it to permissive only upon boot.

My pre-patched boot image is probably key to the successful installation as well. I'll list a complete change log of the exact mods once my beta release is ready. From what I'm gathering on logcat, Viper4AriseFX is "seeing" SELinux as permissive, while other system components are seeing the policy as enforcing. I believe I've stumbled upon the key to this SELinux policy dilemma.
[Android Q&A, Help & Troubleshooting] pndwal:
No really unique ideas, but interested in improved performance (speed and battery), battery being pretty good already.

MT8161p CPU specs say Quad-Core, 1.3 GHz, but TB3-850f is limited to 1.0 GHz, so a kernel modified to allow overclocking should achieve 30% boost easily (and CPU can usually go ~30% higher than specs, so perhaps 1.7 GHz or so would be achievable) unless I'm missing something.

Could improve Adoptive Memory (SD) handling, but may have to wait for port to N or O for this as anomalies with handling Dev. manifest values to make moveable apps automatically go to SD (as well as not allowing some even to be moved manually that should move fine) seem to an Android M limitation. (Works beautifully/ as expected on my phone with lineage N, and if Dev. hasn't enabled 'move apps to SD', can 'Force allow apps on external' in Developer Options [Makes any app eligible to be written to external storage, regardless of manifest values].) Guess N / O may be a way off, but would be nice.

Lenovo is now pushing ~30MB OTA update to TB3-850F_S100031_171010_ROW, so you'll probably want to capture / incorporate this in your ROM. (Is it possible to modify OTA update to allow flashing on rooted devices without restoring stock recovery? [Edit: Seems this would require merging differential update with complete files updated, and likely should only be flashed as complete ROM unless stock restored. Saw this: https://twrp.me/faq/officialota.html]) This is not available as a complete downloadable ROM on Russian Websites (lenovo-forums.ru or 4pda.ru) or others as yet as far as I can see.

Hope ideas are helpful, PW.
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
You may have read the wrong specs. There has been much confusion between the TB3-850M (which runs on the MT8161p), and the TB3-850F (which runs on the MT6735m). A lot of online sources have misstated the board platforms on these two tablets.

My TB3-850F build.prop clearly lists the board platform as MT6735m, as does the hardware reading given by the SP Flash Tool when I sync the device on my PC. I wish mine did have the MT8161 (1.3GHz) versus the 1.0GHz of my MT6735.

But just to be certain there are not variants of the TB3-850F, read your build.prop via file explorer or build prop editor and let me know if yours is in fact the MT8161p.

Thanks for the heads up on the OTA. I wasn't aware of it and I'll definitely be updating my stock ROM thread accordingly.

Oh to answer your question on the OTAs, yes you can flash an OTA to a rooted/modified device by editing the updater-script and omitting the crypto-hash checks performed during the typical OTA installation, and by editing the incremental target and source lines (or omitting them entirely).
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
Just got the 33mb OTA captured. Looks like there are the usual bug fixes & stability improvements, but also the KRACK exploit has been patched, the partition index updated, and kernel updates. I'm currently compiling an up-to-date stock ROM with TWRP flashable installer.
[Android Q&A, Help & Troubleshooting] pndwal:
Yes, I'd forgotten this confusion.

Actually, didn't check online sources, but assumed Phone Tester was reporting correctly. It gives CPU Info: MT8161p.

Just checked Kernel Auditor which gives MT8161p as vendor, but MT6735 as hardware.

CPU-Z gives MT6735 as SoC.

My build.prop also gives ro.board.platform=mt6735m, but also ro.lenovo.cpuinfo=MT8735P.

Russian 4PDA forum gives 850f Processor Type: MT8161, with MT8735 for 850M variant. (http://4pda.ru/devdb/lenovo_tab3_8:850f)

So it's hard to know what or who's correct, but

looks to me that newer CPUs have likely been installed on boards originally designed for MT6735

. (My CPU could actually be MT8735 as given by build.prop if Lenovo had excess chips from 850M, or simply decided to use these in both models. - I guess they may even have started with MT6735 for 850f before progressively using MT8161 and MT8735.)

So seems to me to be in the realms of possibility that a kernel allowing overclocking may just render spectacular results (as long as later CPUs were in fact used, and these are not crippled by an older board chipset.) But then, I may be way off base . . . Let me know your thoughts. PW.
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
Yeah I agree with you wholeheartedly that overclocking - at least moderately - could provide some benefit. I'm seeing that our current 1.0GHz maximum clock could safely be overclocked to about 1.33GHz. Definitely something I will be considering. I've been able to optimize this device's meager 1GB RAM by zipaligning the apk files, and by setting a maximum background process limit to build.prop. I've also found that setting the stock kernel's Adaptive Low Memory Killer to Very Aggressive helps as well.

I've installed the OTA and it seems to improve general stability of the device, and provides us with much needed security patches. I'll be updating my stock ROM to the most recent version later today. Here is a link to the captured OTA if anyone is interested in exploring it. However, in order to flash it to a rooted/modified device, the updater-script first needs to be modified. But again, I'll have the updated build posted later today.

OTA_TB3-850F_S100031_171010_ROW: https://drive.google.com/file/d/11xo-7X06ST1RV8X5TJHjM5o2MHfcsNhl/view?usp=drivesdk
[Android Q&A, Help & Troubleshooting] pndwal:
Great. What do you make of build.prop entry: ro.lenovo.cpuinfo=MT8735P? PW.
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
It's simply a typo that was made in build.prop I believe. Going by ro.board.platform, they seem to have it correct with the 6735 entry. I was just messing with some components of the unpacked boot image from this device, and it seems that except for the SoC differences, the 850M and 850F are otherwise identical. Of course, the 850M, by way of its mt8161p, has full SIM & 4G/LTE data support. In our variant, the SIM slot (next to the micro SD card slot) is blocked off, whereas it's fully accessible in the 850M.

P.S, if you're rooted, add this line to build.prop and let me know if you see a difference in RAM optimization: ro.config.low_ram=true
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
By the way [MENTION=6939319]Hemphiz[/MENTION], feel free to chime in with some ideas old friend. After all, you paved the way for me in development for this tablet.
[Android Q&A, Help & Troubleshooting] Hemphiz:
All gravy here mate. Just appreciating all the work your doing really. Great stuff :good:
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
Thanks mate. Good to hear from you as always. By the way, latest build is up.

https://xdaforums.com/android/general/rom-lenovo-tab-3-8-tb3-850f-t3617594
[Android Q&A, Help & Troubleshooting] pndwal:
Thanks, I'll try your RAM trick soon when I have time. Been pretty busy. PW.

---------- Post added at 12:36 PM ---------- Previous post was at 12:28 PM ----------

You will no doubt be interested in this:

Magnum Opus 20171114 Stock Edition​

20171114 Stock Edition has been updated to reflect the way Magisk handles SeLinux so ARISE will now process on Enforcing for those of you who use Magisk 14.2+

The same change has occured in the following themed versions of ARISE packaged and hosted by [MENTION=8383546]sonophilos[/MENTION]

20171114 Black 'n Cheese Edition - BlackRed​

20171114 Black 'n Cheese Edition - Inverted​

NOTE: Users of ViPER4Android 2.3.4.0 variants will have to manually enable the Storage permission in Settings/Apps for profiles and IRS to show up in ViPER. Apologies - this is how the stock apk, as well as the D Rey themed apks which are based on the stock apk, behave.

(https://xdaforums.com/showpost.php?p=74519163&postcount=31299). PW.
[Android Q&A, Help & Troubleshooting] pndwal:
From my limited understanding of Viper4AriseFX with NEON, I wouldn't mind seeing / trying this as standard inclusion in ROM now that it's no longer necessary to toggle SELinux to permissive. (Not sure if 'Dolby' FX should also be removed - or left to co-exist?) PW.
[Android Q&A, Help & Troubleshooting] exelinguy:
[MENTION=7383447]MotoJunkie01[/MENTION] Sir, would be very grateful if you could tell me if the stock ROM for TB3-850F would be compatiable with TB3-850M. I was unable to find any info on my searches. Thank you very much!
[Android Q&A, Help & Troubleshooting] MotoJunkie01:
Yes it is compatible. I searched the source code and found that the 850F and 850M variants of the Tab 3 both use the same stock ROM. Take a look at the source code and you'll see what I mean. https://pcsupport.lenovo.com/us/en/products/tablets/a-series/tab3-8/downloads/ds112711