yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Themes and Apps] JohnMcW:
This is my J Dark Ice theme, works with Lineage OS 14 (vers 02/13 and older)

also tested with Tesla Rom, and Pure Nexus (on the Nexus 6P)

Works great on current AICP

Color Choices available -- Ice Blue (default) -- Ice Gold -- Ice Jade -- Ice Mint -- Ice Pink -- Ice Purple -- Ice Silver

-- -- --Primary Blue -- Primary Green -- Primary Red -- Primary Yellow

Color choice is under Android System...You must install Android System if you want the other apk's to theme.

--3 Signal style choices under SystemUI

You must have Substratum installed (get from play store)

MAKE SURE that you enable permissions for Substratum or you will get Apk could not be signed messages

If you are having problems with Substratum not changing themes properly, you should probably be checking the substratum forum

One thing they are saying helps on the newer versions of Nougat is to :

1) go to Settings--Google--Security--Verify Apps and turn everything off

2) go into Developer Options--UnCheck verify apps over usb

This is a almost ready to go to the play store version, I am looking for useful comments for problems that may be evident.

Warning: when using with 2/13, no problems...when using with newer version of lineage, removing the theme or changing might put you in a boot loop, this is a known issue with Substatum

Download J Dark Ice Substratum Theme

For matching icons, I recommend using my J Blue Ice Icons with Nova Launcher (See signature)

This is a dark theme, Wallpapers are included to use in the theme, I use the first one "carbon dark" (it looks black, but has a pattern when enlarged)

Don't forget that some apps have an option to choose a dark theme, you should switch to that when possible,

for instance the Default keyboard will originally show up much lighter, choose the material dark option and you get

what you see in the picture attached

What is themed?

AdAway

Android Keyboard (AOSP)

AudioFX

Bluetooth Share

Browser

Calculator

Calendar

Call Management

Camera

Chrome

Clock

Contacts

Email

File Manager

Gallery

Gmail

Google App

Google Play Store

Google Text-to-speech Engine

Hangouts (Talk)

Inbox

Maps

Messaging

Music

Nova Launcher

Package Installer

Phone

Root Explorer

Settings

Should I Answer

SwiftKey Keyboard

SystemUI - Status Bar icons - Nav Bar icons -etc

Trebuchet

cLock

substratum
[X Style (Pure) Themes and Apps] JohnMcW:
Update Log

See new updates in the play store.

V2.0 03/18/2017 - Substratum 7 - Color Choices added - Name Change - More Vector Xml graphics

V1.8 03/05/2017 - converting png's to Vector xml graphics, most settings screen updated. Added Tesla tweaks

V1.7 02/27/2017 - fix for rom compatablity with Pure Nexus, Contacts all column white text, other tweaks

V1.5 02/22/2017 - possible bad upload of v1.4. re-upped

V1.4 02/21/2017 - Inbox white on white compose text fixed

V1.3 02/20/2017 - Fixed Cut and paste text issue.

Known Issues

Google Maps - when selecting more information for a specific location, Maps closes. If you need this, just don't select Google Maps when Selecting theme
[X Style (Pure) Themes and Apps] JohnMcW:
v1.7

system_bar_background_semi_transparent usage changed to bright_foreground_light_disabled because this name not found on some roms.
[X Style (Pure) Themes and Apps] JohnMcW:
V1.8 available

V1.8 converting png's to Vector xml graphics, most settings screen updated.

Added Tesla tweaks for some graphics and to fix editing quick Panel,

various other updates and tweaks.
[X Style (Pure) Themes and Apps] JohnMcW:
V2.0

Now in the play store

New in V2.0

Name Change,

Theme is now called J Dark Ice Substratum Theme,

you will need to uninstall the J Blue Ice Substratum Theme If you don't want them both active

Re-based Project with Substratum 7

More Png's changed to vector graphics

New Color Choices available --

Ice Blue (default) -- Ice Gold -- Ice Jade -- Ice Mint -- Ice Pink -- Ice Purple -- Ice Silver

-- -- --Primary Blue -- Primary Green -- Primary Red -- Primary Yellow
[X Style (Pure) Themes and Apps] Nimueh:
I just discovered this theme in the Playstore and am thrilled to have it back - I used to love the golden CM theme. My absolute favorite part is the boot animation though, as a cat lover I LOVE that tiger and am so happy to have it back.

Thank you :) :victory:

Edit: You really should move your thread out of this device specific forum and into a general one like Substratum - that way more users would find your great theme :cool:
[X Style (Pure) Themes and Apps] Andy2No:
Working well with [ROM][7.x] nAOSProm for Nexus 7 (2012) By millosr, version nAOSP 7.1.2 b01 - 2017/04/13 based on android-7.1.2_r5 (April security fixes).

The app drawer still has a bright background though - the ROM uses Launcher3. Could that be lured over to the dark side too? Is it its destiny?
[X Style (Pure) Themes and Apps] JohnMcW:
Have you tried nova launcher? it is a favorite one that I use,
[X Style (Pure) Themes and Apps] Andy2No:
Thanks. I hadn't. I was hoping to be able to get the launcher that came with the ROM to behave, but I'm having a look at it....

It seems promising, but I can't see any way to stop it lighting the screen up almost white, when I drag an app from the app drawer - even after setting the background to black. I've tried putting my hand over my eyes, but it's hard to see where I'm putting it then :)
[X Style (Pure) Themes and Apps] jogai:
Thanks for this unique theme! I'm using it on a Nubia phone with RR rom. Works nice with the red notification light.
[X Style (Pure) Themes and Apps] theninjew:
Does this work on Oreo? Can you make an IceBlack accent?
[X Style (Pure) Themes and Apps] theninjew:
See attached. Does this theme have this "bug" where you can't see the name of the person posting in a whatsapp group? Or does this theme not have this option for an overlay?
[X Style (Pure) Themes and Apps] JohnMcW:
I do not know, I do not use Whatsapp,

an overlay is included for Whatsapp, but Whatsapp continuously changed their application with, what would appear, a clear intention of stopping people from theming it. In addition Whatsapp rolls out their changes very slowly so that there can be up to 3 different versions active at the same time.

The amount of time it takes to keep up with Whatsapp is too much to keep on top of it.
[X Style (Pure) Themes and Apps] Shellyaffff:
Battery icon missing and percentage and can you make that white flash go as you go in to settings just before it goes black
[Mate 8 Q&A, Help & Troubleshooting] darian3:
For two weeks my phone (Mate 8 L29) is discharging quickly. Initially I thought it should be because of some applications and so I uninstall the main applications running in the background like facebook.

But that did not change anything. Yesterday I formatted my phone and switched from a B180 Ephemeral rom to the stock B560 (Ephemeral B180 -> Stock B180 -> Stock B560).

The battery was behaving rather well until it reached about 60%, at which time the charge literally collapsed. The battery has gone from 60% to 27% in a few minutes. Around the 30% I saw him lose 1% every 15 seconds! So I plugged in the phone and the ascent of the load was as fast as the fall between 30 to 60%. After 60% the battery seemed to recharge at a more normal rate.

Do you think it is the battery that is physically dead and I need to replace it or can it come from a bug in the battery display?

The phone is less than a year old, but I could not use the warranty since I installed a rom.

On the screenshot you can see the battery go from 60% to 30% then go up to 60%, all in just about 30mins and without using a greedy application like a video game.
[Mate 8 Q&A, Help & Troubleshooting] rhaspody:
you may need to replace your battery..

when exactly did it start.

Do you always charge up your phone A's soon as it starts discharging

Do you always plug in your phone while doing heavy gaming?
[Mate 8 Q&A, Help & Troubleshooting] darian3:
It started about two weeks ago.

It happened several times to play with the phone connected. In general I expect it to be under 20% to recharge it, sometimes I charge it before if I know I have a long day without access to a power outlet.

I understand the questions very well, but it sounds quick. That a battery is so worn out in a little less than a year.
[Mate 8 Q&A, Help & Troubleshooting] janrck:
Im having the same issue and In going to replace the battery today, I'll tell you the results

Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
[Mate 8 Q&A, Help & Troubleshooting] rhaspody:
Please do keep us posted in case this is a problem of Mate 8
[Mate 8 Q&A, Help & Troubleshooting] darian3:
Is it possible to make the message "your device has been unlocked" disappear ? That would allow me to try the guarantee.
[Mate 8 Q&A, Help & Troubleshooting] janrck:
I've change the battery and everything backs to normal. The battery life is huge again.
[Mate 8 Q&A, Help & Troubleshooting] Apad121:
Where did you go to change the battery, was it an official change? Did you lose your warranty? How much was it?

Thanks

Also how have you guys been charging your phones? Overnight? Fast charging overnight? Or slow charging overnight?
[Mate 8 Q&A, Help & Troubleshooting] janrck:
I changed the battery myself with a youtube tutorial, very easy:

https://youtu.be/b7f8fdYz5ig
[Mate 8 Q&A, Help & Troubleshooting] darian3:
I was charging my phone overnight wit fast charging. I know fast charging overnight is useless, but the official charger only do fast charging, so no choice.

I want to change my battery myself, like janrk, but first, just out of curiosity, im going to try the sellers warranty. I try to join Huawei, they just didnt answer.

A lot of chinese website sell "Official Mate 8 battery", but im not sure they are really official. I find 7 to 9€ battery on chinese web site, 12€ on Amazon (chinese seller), 25 to 35€ with european seller. That's only for the battery, i you didnt want to change the battery yourself its between 49 to 80€.
[Mate 8 Q&A, Help & Troubleshooting] janrck:
My battery cost me 13€, and is identical to the original battery
[Mate 8 Q&A, Help & Troubleshooting] darian3:
Where do you buy it ?
[Mate 8 Q&A, Help & Troubleshooting] darian3:
I contacted the after-sales service of Huwaei. They told me that it was necessary to cut the wifi and the mobile data when the phone is in charge. And that in general it was necessary to cut the wifi and the mobile data when one does not have the use of it. I deduce that they have poorly designed these elements of the phones, and that they cause it to overheat. This should reduce the battery life.

I asked them if it was possible to have a warranty. It is possible, but for this i must accept to send the phone to them for several weeks. Since I do not wish to have no phone for several weeks I will order a battery. Their after-sales service is really useless: /
[Mate 8 Q&A, Help & Troubleshooting] janrck:
Here https://www.spainsellers.com
[Mate 8 Q&A, Help & Troubleshooting] /dev/null_dd:
stupid thingy ...

almost same thing happend on me and i had to replace battery to solve it.

it took only 10 month to kill damn built-in battery.

i can't belive it. its just 10 month.

i never see like this.

most cheapest battery (made in china) was worked over 24 month.

:(
[Mate 8 Q&A, Help & Troubleshooting] darian3:
I just change the battery, is actually that fixes the problem. Now I'm not sure that the battery is necessarily bad at the base. I wonder if the design of the phone does not cause an overheating of the phone that is damaging the battery prematurely.
[Nexus 6 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
You're over thinking things. If I understand things correctly, you have the stock recovery installed? If so, sideload an OTA image from Google's developer pages, then reboot. Once rebooted, enter developer options and tick "Enable OEM Unlocking". After that unlock the bootloader and leave it unlocked. That will resolve the issue of the device not functioning correctly.

Afterward, restore TWRP then flash the flashable zip here, instead of building the ROM from source for a fix that Google is likely going to include in a future update.
[Nexus 6 Q&A, Help & Troubleshooting] kepan:
Thanks Strephon for your reply.

The recovery that I currently have only trusts OTA updates signed with test-keys. It is an AOSP recovery from own private build.

Unfortunately, I have already tried sideloading stock OTA update from Google page but it didn't work due to update signature check failure. Google's update is signed with their private release key.

Is it possible to change OTA signature on Google's stock OTA update file to be signed with private test-keys?

Would an installation of such an update restore the stock ROM successfully?
[Nexus 6 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
I'd ask what the heck you were thinking in locking the bootloader, but we already know the answer. I don't have an answer for you regarding switching keys. I know it's possible to re-sign apps, but an entire ROM? A pretty large undertaking.
[Nexus 6 Q&A, Help & Troubleshooting] Arju:
[MENTION=8085130]kepan[/MENTION] since you're able to get to bootloader menu, are you able to type the "fastboot OEM unlock" through computer? (I'm just trying to understand the situation).
[Nexus 6 Q&A, Help & Troubleshooting] Dopamin3:
Probably not because I would imagine "OEM unlocking" was disabled in developer options in the build he compiled.
[Nexus 6 Q&A, Help & Troubleshooting] Arju:
That's my guess too. If he can't use fastboot commands and does not have a custom recovery such as twrp, then he's toast. But the OP already knows that. Was just checking if he missed some small detail.
[Nexus 6 Q&A, Help & Troubleshooting] kepan:
I thought that by locking the bootloader I will have higher security as the new build would not be possible to be flashed unless 'Allow OEM unlock' option is enabled in the Developer Settings. I didn't know that the bootloader will reject my custom ROM. Now I think it may have been caused by Open GApps installation that broke the system partition integrity check.

I don't think that the entrie Google stock ROM needs to be re-signed. Looking at tools/releasetools/ota_from_target_files.py line 2130:

# Sign the generated zip package unless no_signing is specified.
if not OPTIONS.no_signing:
SignOutput(temp_zip_file.name, args[1])
temp_zip_file.close()

it seems that it should be possible to just repeat the signing part (copied above) with the testkeys on Google's OTA zip file. This way the included stock ROM should be intact. Only the zip file signature will be changed. I understand that only this zip file level signature is checked by the recovery during update from zip process.

I would be great if someone with recovery's OTA file update process experience could assess if this is a viable fix.

I tried that but I get remote error: Please check 'Allow OEM unlock' in Developer Settings. I am not able to boot the system to actually perform this action.

I was not explicitly changing anything related to OEM unlocking in the build. Whatever the default value for shamu AOSP build is was used.
[Nexus 6 Q&A, Help & Troubleshooting] Dopamin3:
...the default value is disabled. Meaning unless you go in and enable OEM unlocking, then you can't just unlock the bootloader. If you could you would simply go into bootloader mode, do "fastboot oem unlock" and flash a factory image. Because you didn't enable OEM unlocking then you're screwed.
[Nexus 6 Q&A, Help & Troubleshooting] kepan:
I managed to fix it :) by flashing modified Google OTA file from test-keys recovery.

I was doing AOSP build on Ubuntu thus the following commands are for Linux platform.

I am assuming that whoever ended up in my situation did the AOSP build at least once, have the build environment setup and is more or less familiar with the build procedure.

The commands below assume that the AOSP build output is placed in out directory of the AOSP working directory and that you didn't clean the build artifacts (SignApk.jar binary is built as part of the AOSP build).

If you have signed your AOSP private build with your own keys pair then the below procedure will still work for you. You just need to modify the signing command to use your private and public keys.

Unzip the official Google OTA file to a temporary directory in the root of AOSP working directory.

mkdir tmp
unzip shamu-ota-n6f26r-f3fd968c.zip -d tmp
cd tmp

Remove first line that checks if the currently installed build is not newer than the OTA build from META-INF/com/google/android/updater-script

The line that needs to be removed will look similar to

(!less_than_int(1487451871, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Sat Feb 18 21:04:31 UTC 2017) over newer build (" + getprop("ro.build.date") + ").");

Zip back the files. We instruct the command to place the output file in the parent directory.

zip -r9 ../update.zip *

Sign the new ZIP file with SignApk.jar using -w parameter (whole file signature) and private and public test-keys keys. The below command is exactly the same command as ota_from_target_files.py script is using. The paths are relative to the root of the AOSP working directory on your machine.

java -Xmx2048m -Djava.library.path=out/host/linux-x86/lib64 -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 tmp/update.zip tmp/update-signed.zip

Adb sideload the signed ZIP file from AOSP test-keys recovery.

First, boot to recovery by holding down Power + Volume Down buttons during boot until you get into bootloader menu. Once you are in the bootloader screen select Recovery option using Volume buttons. Confirm the selection by pressing the Power button.

In Recovery select Update from ADB using Volume buttons and press the Power button to start the ADB listener.

Then on your machine upload the signed update with:

adb sideload update-signed.zip

If you get the signature error and you are confident that you have signed the update with the correct key then try again (maybe the file was incorrectly transferred).
[Nexus 6 Q&A, Help & Troubleshooting] Arju:
Woah! That is nice. Glad it worked out for you. Would be nice if you can make an updated post on how to go about in case this happens with anyone else. Well done! :)
[Nexus 6 Q&A, Help & Troubleshooting] kepan:
Thanks.

I have updated my previous post with detailed steps, added [SOLVED] prefix to the topic's title and link to the fix in the first post.
[Nexus 6 Q&A, Help & Troubleshooting] saltsaint:
Just a tought - may it be possible, following this method, to modify an

older Google OTA

, to make the downgrade process easier?
[Nexus 6 Q&A, Help & Troubleshooting] kepan:
As long as it is a full OTA (not an incremental) and you have the private key corresponding to the recovery.

If you have an official recovery signed with Google release key then it will not work.
[Android General] viv_jen:
What is your software version?

Mine is TB3-850F_160412

i have a pending 51MB update ,do i complete all updates or ignore them and root?

Also whats the procedure to unroot if i want to get the updates later?
[Android General] Hemphiz:
Look for build number. It's usally best to determine things. I'm on TB3-850F_S100030_161209_ROW

I took the latest OTA before flashing twrp else ota will fail due to the recovery being modified. For unroot there's an option in Superssu to unroot. I would personally create a full backup via twrp before rooting, so you can revert to it if you wish
[Android General] nox13666:
this bricked my tablet
[Android General] Hemphiz:
Well you must've done something wrong. It's pretty much fool proof
[Android General] MotoJunkie01:
Great thread. OP's instructions & downloads work flawlessly. Thank you [MENTION=6939319]Hemphiz[/MENTION]
[Android General] MrStrange10:
Thanks for the guide
[Android General] Xecsc:
Thanks for the guide!

Everything works but when I reboot into recovery I just get the dead android with no command under him..

I tried two times with same result Fastboot reports twrp flashes ok

Any ideas?

Thanks
[Android General] MotoJunkie01:
Not to hijack the OP's thread but here are my thoughts. The dead Android indicates that TWRP did not successfully flash to your /recovery partition. Sounds like stock recovery is still installed. First, place a copy of twrp.img on your device's internal storage or on an external micro SD. Try this: instead of typing the command "fastboot flash recovery twrp.img", type " fastboot boot twrp.img" (assuming your twrp file is named twrp.img. If it isn't, rename it twrp.img for simplicity purposes). This command will temporarily boot your device into TWRP recovery. From the main menu on TWRP, select INSTALL. In the bottom right of the screen, select the option for "img" files. Navigate to where you stored "twrp.img" and select it. Install it to "RECOVERY" when prompted. Once it flashes, select REBOOT then select RECOVERY. Your device should now successfully boot into TWRP recovery.
[Android General] phreeker:
I was running into the same issue after flashing twrp.img via fastboot, it kept coming up with no command when booting into recovery. Followed MotoJunkies advice and booted into twrp.img instead of flashing and installed it that way, now my device is rooted. Thank you Hemphiz and MotoJunkie.
[Android General] Xecsc:
Thanks worked perfect!
[Android General] figgenhoffer:
this did not work for me. now my tablet is in boot loop. keeps going to team win. trying to trying to mount storage and then back to the regular boot. over and over.
[Android General] MotoJunkie01:
Hmmm. Did you execute "fastboot oem unlock" first to unlock your bootloader? It sounds as though you are saying TWRP installed correct? When you try to boot into the OS, you are getting reverted back to TWRP?
[Android General] figgenhoffer:
i did that. i had teamwin recovery. then installed the superuser.zip and it keeps looping
[Android General] MotoJunkie01:
I see. The superuser zip is likely the culprit. Which one did you use? Did you use the one in the link? Here is a link for the stock boot.img for this device. Install it in fastboot mode by typing "fastboot flash boot boot.img". Try booting after flashing the stock boot image and also try reinstalling the boot script.https://drive.google.com/file/d/0B7-zQU1VihD3ZGZBRzU1Nm1PYjA/view?usp=drivesdk

Note: you will need to rename the downloaded file to " boot.img"
[Android General] smouge:
Thanks for the guide. Tried to do this on the Lenovo TAB3 10 Business, but no success

I can connect using the tools and enter into fast boot

When I flash, it seems successful, but after shutdown, start with power, volume buttons, I don't see the TWRP, but instead a kind of test app

When i use the other method to boot into the twrp, the Lenovo, boots normal, not into TWRP

Any ideas?
[Android General] MotoJunkie01:
When you initially connect your Tab3 to PC and open a command window, did you execute both recognition tests? "adb devices" and "fastboot devices"? I am just curious as to whether your device is being recognized by both the fastboot and the adb platforms. Please try this and let me know.