Database Develop

Changing the DPI to 440 breaks the phone app.

When i changed my phone' DPI to 440 it broke the default dialer app, like the arrows were missplaced. Is there any way to fix this ?

How did you change your density? If you just did this via ADB, you may experience some oddities - I had some issues with the Play Store.
If you are rooted, I would recommend adding the following build.prop entry:
ro.sf.lcd_density=440

brooksilg said:
How did you change your density? If you just did this via ADB, you may experience some oddities - I had some issues with the Play Store.
If you are rooted, I would recommend adding the following build.prop entry:
ro.sf.lcd_density=440
Click to expand...
Click to collapse
this method might also create issue with some apps and with play store. I would prefer changing density via local.prop method but sadly that won't work on user-release roms.

abhibnl said:
this method might also create issue with some apps and with play store. I would prefer changing density via local.prop method but sadly that won't work on user-release roms.
Click to expand...
Click to collapse
The thing is I'm not rooted and I did it via ADB is there anyother way to solve it ?

anshmiester78900 said:
The thing is I'm not rooted and I did it via ADB is there anyother way to solve it ?
Click to expand...
Click to collapse
Unfortunately, since you are not rooted, ADB wm density command is the only option you have. I'll search on my own and hope to find a method but i know wm density is the only one possible for non-root users.

abhibnl said:
this method might also create issue with some apps and with play store. I would prefer changing density via local.prop method but sadly that won't work on user-release roms.
Click to expand...
Click to collapse
I can confirm that some build prop edit apps can break things. I've been applying build.prop tweaks using FX file manager without any problems.
Sent from my ONEPLUS A3000 using Tapatalk

anshmiester78900 said:
When i changed my phone' DPI to 440 it broke the default dialer app, like the arrows were missplaced. Is there any way to fix this ?
Click to expand...
Click to collapse
I'm at 420 and have zero issues. I changed mine the same way you did, via adb...

k.s.deviate said:
I'm at 420 and have zero issues. I changed mine the same way you did, via adb...
Click to expand...
Click to collapse
You mean there are no graphical glitches at 420 in the phone app ?

anshmiester78900 said:
You mean there are no graphical glitches at 420 in the phone app ?
Click to expand...
Click to collapse
That's is correct. I was using the default dialer with no issues, I'm now using the Google dialer and also have zero issues.

k.s.deviate said:
That's is correct. I was using the default dialer with no issues, I'm now using the Google dialer and also have zero issues.
Click to expand...
Click to collapse
I'm not able to find the google dialer on playstore. Did you download it from somewhere else?

anshmiester78900 said:
I'm not able to find the google dialer on playstore. Did you download it from somewhere else?
Click to expand...
Click to collapse
Google blocked it from all devices except Nexus devices, so you won't find it there. They also blocked being able to install the apk alone so I installed it using the aroma open Gapps zip. You need to install the framework and the dialer.

That's why I aaalways say again and again:
DON'T use global DPI change!
Use Xposed module "App Settings" and customize the DPI only for those apps for which you need it.

k.s.deviate said:
Google blocked it from all devices except Nexus devices, so you won't find it there. They also blocked being able to install the apk alone so I installed it using the aroma open Gapps zip. You need to install the framework and the dialer.
Click to expand...
Click to collapse
Ohk thanks for the info mate

anshmiester78900 said:
When i changed my phone' DPI to 440 it broke the default dialer app, like the arrows were missplaced. Is there any way to fix this ?
Click to expand...
Click to collapse
Changing DPI (with adb or editing build.prop) also causes green photos when you are in HQ mode (stock camera)

Zalpa said:
Changing DPI (with adb or editing build.prop) also causes green photos when you are in HQ mode (stock camera)
Click to expand...
Click to collapse
This does not happen in my case. I have no adverse effects from changing my dpi globally.

[Magisk][Module] iOS10 emoji font

iOS10 Emoji font
Changes the default emoji font to the iOS10 Emoji for various android devices.
This module also changes the system font configuration so the font pack is loaded first.
Preview of all the iOS10 emojis included in this module:
*Click on the picture for a high resolution image.
Prerequisites
Magisk v13.1 or higher
Note: Tested on the Oneplus x running various android 6 and 7 roms with Magisk v13.1 &v13.3. Your mileage may vary.
How to download & install this module
Option 1
Inside Magisk manager app go to the "Downloads" section.
You can find "iOS10 emoji font" listed their.
Click on the download button (down arrow) and then click on "install".
Wait a few seconds for the download & installing to finish.
After installing click on "reboot". Your device should reboot.
Option 2 (when option 1 fails for some reason)
Download the zip file manually here from my personal google drive
Inside Magisk manager app go to the "Modules" section.
At the bottom of the page click one the "+" icon.
Navigate to the downloaded zip file and click on it.
Wait a few seconds for the installing to finish.
After installing click on "reboot". Your device should reboot.
How it works
Replaces the default emoji font (NotoColorEmoji.tff) with the iOS10 variant.
Links
Magisk forum
Magisk manager app
Manual zip download version 5 & 6
Discussion on XDA
Bug report
Github
Donate
Change Log
version 7.1
* oops.. fixed typo on the HTC font file
version 7
* New emoji font
* Fix for samsung & HTC roms.
* Template V4
version 6
* Saftey net breaks in magisk v13 beta so this is a temp fix by disabeling the post fs data script.
* Disabled post-fs-data script
* Disabled Dynamic fonts.xml
* Disabled Dynamic fallback_fonts.xml
version 5
* Added post-fs-data script
* Dynamic fonts.xml
* Dynamic fallback_fonts.xml
version 4
* Updated font file
* Some typo's fixed
* Updated support links
version 3
* Updated module for magisk v11.6
version 2
* Name updated
* Description added
* Added Donate link
version 1
* Initial Release

Using sed to patch fonts.xml is much better than replacing it. :good:

I'm sure I'm missing something incredibly simple, but I can't figure out how to download this.
Sent from my LG V20 using XDA Labs

NickWhit1992 said:
I'm sure I'm missing something incredibly simple, but I can't figure out how to download this.
Click to expand...
Click to collapse
Inside Magisk manager app go to Downloads. You can find it there.
Sent from my OnePlus3 using XDA Labs

AdrianM said:
Inside Magisk manager app go to Downloads. You can find it there.
Click to expand...
Click to collapse
Thanks, it never occurred to me to check there, most of the modules I use aren't in the repo.
Sent from my LG V20 using XDA Labs

NickWhit1992 said:
Thanks, it never occurred to me to check there, most of the modules I use aren't in the repo.
Sent from my LG V20 using XDA Labs
Click to expand...
Click to collapse
I added a section in the original post how to install this module from the Magisk manager app.
Thanks for your feedback.

My magisk manager seems to FC when downloading . Is there anyhere i can download this manually ?

harrez said:
My magisk manager seems to FC when downloading . Is there anyhere i can download this manually ?
Click to expand...
Click to collapse
I have a link to the zip file. Its on google drive. https://drive.google.com/drive/folders/0BzOEHiXH09zFTnVKNjAtZUVlR3c?usp=sharing
I will add this link also to the post.
I don't know why your magisk manager FC when its downloading. Do you have enough storage left because the zip is pretty large 20MB.
But thanks for your feedback.

Jplwolters said:
I have a link to the zip file. Its on google drive. https://drive.google.com/drive/folders/0BzOEHiXH09zFTnVKNjAtZUVlR3c?usp=sharing
I will add this link also to the post.
I don't know why your magisk manager FC when its downloading. Do you have enough storage left because the zip is pretty large 20MB.
But thanks for your feedback.
Click to expand...
Click to collapse
thank you so much . it seems like My magisk manager has some problem with it . now it is working as usual .

Everythings working fine. Thank you!

Will it work with gboard?
Sent from my LenovoA3300-HV using XDA Labs

psychoela said:
Will it work with gboard?
Sent from my LenovoA3300-HV using XDA Labs
Click to expand...
Click to collapse
Yes, it works with gboard. If the emoji's aren't showing after installation clear the data of your gboard app in order to show the emoji's. I use gboard myself and they work fine.

Jplwolters said:
Yes, it works with gboard. If the emoji's aren't showing after installation clear the data of your gboard app in order to show the emoji's. I use gboard myself and they work fine.
Click to expand...
Click to collapse
not work here,i already clear cache data gboard then reboot,still emoji not changed
Sent from my Nexus 6 using XDA Labs

psychoela said:
not work here,i already clear cache data gboard then reboot,still emoji not changed
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
You have to "clear data" from your keyboard app and not "clear cache". After you pressed this reboot your device and set up your keyboard again to your preferences. Setting up your preferences takes at most a minute.
I'll wait for your response.

Jplwolters said:
You have to "clear data" from your keyboard app and not "clear cache". After you pressed this reboot your device and set up your keyboard again to your preferences. Setting up your preferences takes at most a minute.
I'll wait for your response.
Click to expand...
Click to collapse
yes,i clear cache and data then reboot still same
Sent from my Nexus 6 using XDA Labs

psychoela said:
yes,i clear cache and data then reboot still same
Click to expand...
Click to collapse
Sent from my Nexus 6 using XDA Labs

On my S7 Edge the clockfont changed on my lockscreen its bigger and bold is there no way to change that ?

Iradj said:
On my S7 Edge the clockfont changed on my lockscreen its bigger and bold is there no way to change that ?
Click to expand...
Click to collapse
Yes. Reboot for a second​ time. This should fit it

Jplwolters said:
Yes. Reboot for a second​ time. This should fit it
Click to expand...
Click to collapse
Thanks Mate it worked

psychoela said:
yes,i clear cache and data then reboot still same
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Strange. I checked this on other phones and it works just fine.
Can you uninstall and reinstall this module from the magisk manager app.
Can I ask you some questions:
Where did you download this module?
Do you have other (fond)mods? Can you name them.
What phone & rom are you using?
Can you look if there is a file in /system/fonts/NotoColorEmoji.tff and is this file 19.72 MB
Thanks. I'm looking into this. And trying to reproduce this situation.

[Module] Systemless Substratum (Legacy/Layers Mode)

v2 Uploaded. Now includes uninstaller in the .zip file under "uninstaller" directory. This can be flashed in TWRP so it removes both the module
and everything Substratum writes in data (/data/system/theme and /data/resource-cache) hence providing you with a total clean slate in case
anything goes wrong. This is your reset button.
Of course you will have to reinstall the module before applying any new theme configuration. Failure to do so, Substratum WILL write in /system.
Uninstaller also available as a separate attachment on this post.
So this is the result of updating my device to Nougat and hating with a passion the white notifications which I find entirely unusable
The only way to theme the notifications is using a Substratum theme. If you're using a custom ROM with OMS support you're good to go
but for the rest of us with stock/TW etc ROMs you can only use Substratum Legacy mode on rooted devices which taints the system partition.
This module allows the use of Substratum themes in Legacy mode, without writing anything in /system.
Instructions:
1. Install module in Magisk and reboot.
2. Apply any Substratum theme.
3. Reboot.
In case of reflashing your ROM, as long as you don't wipe the data partition, the moment you reinstall Magisk, your theme will be automatically re-enabled.
Until the module is in the magisk repo, you can download the .zip and install from Magisk manager.
Github:https://github.com/Nodens-/systemless-substratum-legacy
This has only been tested on my own device, (Samsung S6 Edge+ 928F) running Stock Nougat.
It should work with any ROM and Themes which support the Legacy mode.

Deleted

Will it work in lineage os

user2k10 said:
Would this work on TW MM 6.01?
Sent from my SM-N910F using XDA Labs
Click to expand...
Click to collapse
Has not been tested but it should.
Adhil Rahman said:
Will it work in lineage os
Click to expand...
Click to collapse
Also not tested. If Lineage supports the Legacy mode then yes.
Basic rule of thumb. If Legacy mode works on your rom, this will allow you to use it without writing to /system.

Nodens said:
Has not been tested but it should.
Also not tested. If Lineage supports the Legacy mode then yes.
Basic rule of thumb. If Legacy mode works on your rom, this will allow you to use it without writing to /system.
Click to expand...
Click to collapse
Shows invalid zip format when flashing in twrp

Adhil Rahman said:
Shows invalid zip format when flashing in twrp
Click to expand...
Click to collapse
Hold on I'll attach tested .zip file on OP to simplify things.

Nodens said:
Hold on I'll attach tested .zip file on OP to simplify things.
Click to expand...
Click to collapse
Working perfectly.thanks for the module.now i dont have to reinstall themes after every firmware update.thank you very much.does it cause any problems to the changes that happens after firmware update

None whatsoever. Enjoy

Adhil Rahman said:
Shows invalid zip format when flashing in twrp
Click to expand...
Click to collapse
If you download the ZIP from GitHub, it creates duplicate empty folders. If you remove them, it'll work.
Sent from my Nexus 5X using XDA Labs

May I ask if this module will bring anything more than the Beta version of Substratum here ?
The Beta allows modification without root.

lahceneamine said:
May I ask if this module will bring anything more than the Beta version of Substratum here ?
The Beta allows modification without root.
Click to expand...
Click to collapse
Actually it has nothing to do with the beta functionality which allows you to theme NON-SYSTEM apps without root. You can't theme the notifications with the beta for example.
The module allows you to theme everything you can theme in Legacy mode. But without writing in system partition.

Nodens said:
Actually it has nothing to do with the beta functionality which allows you to theme NON-SYSTEM apps without root. You can't theme the notifications with the beta for example.
The module allows you to theme everything you can theme in Legacy mode. But without writing in system partition.
Click to expand...
Click to collapse
Thank You.
I'm gonna try it then

This module breaks SafetyNet Check in my phone ...

What about Xperia 7.0 devices

Will this work on TW Nougat ? THank you!

Kris Chen said:
This module breaks SafetyNet Check in my phone ...
Click to expand...
Click to collapse
Try using the module to theme apps then after reboot go back to core only mode, reboot and check SafetyNet again.

ytheekshana said:
What about Xperia 7.0 devices
Click to expand...
Click to collapse
Yes it should work.
lonton said:
Will this work on TW Nougat ? THank you!
Click to expand...
Click to collapse
As posted in OP, I specifically made and tested this on TW Nougat.

In the Oneplus 3 stock oos rom i can use substratum in legacy mode, with this i will be able to use themes on settings or android system?

I can confirm it working with LOS 14.1 with Substratum in legacy mode on OP3T with theme Swift Black. I had to choose "v7.1 OMS" in Swift Black's settings.
My notifications are beautifully black now.

couldn't get it to work in a custom stock TW MM 6.0.1 rom for my Note 4. i installed the module, substratum theme engine from the play store and a couple of themes. selected the system ui to be themed, but after a reboot there was no change. the rom is deodexed with a permissive kernel so i don't know what else could be the problem.

[Module] Camera2API enabler

Since Google Camera with HDR+ was ported already, it requires that camera2api to be enabled.
This is done by editing build.prop to add or enable "persist.camera.HAL3.enabled=1".
Note:
This mod only adds camera2api support in the build.prop systemlessly. This does not guarantee modded google camera hdr+ will work on your device.
Axon 7 Users:
Here's a working GCAM that works on my device. However, I don't see any difference with my stock cam hdr. I just use this for slowmo, panorama, photosphere and lens blur effects.
MGCB_7.0H_C2API_Mid_v.3.6_AllinOne_Full_Manual.apk
Requirements:
Android 5.0 & up
Magisk v15
~2014+ Snapdragon SoCs
Instruction:
Add the zip in Magisk Manager -> Modules and reboot.
Or you could also flash it in your custom recovery, TWRP etc.
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled=1". Check attached screenshot for example.
Or
2. Install Camera2 Probe from playstore to check your device's camera capabilities.
UPDATES:
9-15-17:
-added v1400 template
-added camera2api with slowmo fix for Axon 7 users. (I can't guarantee slowmo on other models will work since I used my device's media_profiles.xml file.)
01-25-18
-updated to v1500 template for C2API - Download this file if you only want the HAL3 enabled.
-updated to v1500 template for C2API+slowmo+ (credits to @j1505243)
Credits:
- BSG (4pda)
- @j1505243

Noob question: how do I check in terminal if it's already enabled because in rom included?

vergilbt said:
Noob question: how do I check in terminal if it's already enabled because in rom included?
Click to expand...
Click to collapse
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled 1"

Like this?

vergilbt said:
Like this?
Click to expand...
Click to collapse
Yes.

Unfortunately it did not activate manuals comtrole on my p8lite with Los 13

youwi said:
Unfortunately it did not activate manuals comtrole on my p8lite with Los 13
Click to expand...
Click to collapse
I think this is for snapdragon devices only.

otaconremo said:
I think this is for snapdragon devices only.
Click to expand...
Click to collapse
Yes, and from SD 820+ right?

otaconremo said:
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled 1"
Click to expand...
Click to collapse
I have a G5 which supports it and if I try the command above it does not show the "persist.camera.HAL3.enabled" property. So can we assume that property is specifically to indicate the magisk module is working?
I used this app to check if it was supported already Camea 2 Probe on the play store.

ok how to disable this and revert back to stock ?
causing problem ...
Sent from my ONEPLUS A3003 using XDA Labs

Not working on lenovo zuk z2..... Snapdragon 820

I think the OP should mention that this module is for SD820+ .

Thanks for the effort but still nothing for XZ

josephnero said:
Thanks for the effort but still nothing for XZ
Click to expand...
Click to collapse
Works on my XZ

What is the benefit of getting this mod?

otaconremo said:
Since Google Camera with HDR+ was ported already, it requires that camera2api to be enabled.
This is done by editing build.prop to add or enable "persist.camera.HAL3.enabled=1".
Requirements:
Magisk v13
Instruction:
Add the zip in Magisk Manager -> Modules and reboot.
Or you could also flash it in your custom recovery, TWRP etc.
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled 1"
Click to expand...
Click to collapse
Flashed it on my Lenovo Zuk Z2
Snapdragon 820.
Unfortunately didn't work.
Got really excited for it.
Am i missing anything?

Very noob question is this work on mtk devices

sifatrhmn said:
ok how to disable this and revert back to stock ?
causing problem ...
Sent from my ONEPLUS A3003 using XDA Labs
Click to expand...
Click to collapse
Remove the module in the Magisk Manager app and reboot.

Ariac Konrel said:
Remove the module in the Magisk Manager app and reboot.
Click to expand...
Click to collapse
it doesn't work with my rom like that..
i have to dirty flash the rom again to solve it ..
Sent from my ONEPLUS A3003 using XDA Labs

CStadler said:
What is the benefit of getting this mod?
Click to expand...
Click to collapse
same question, I see no difference on photos.

Substratum Themes Disable Themselves

Android System and SystemUI overlays disable itself in every reboot and don't work properly in the first place! In my S8+ everything works fine. The theme is compatible with both. What is going on?

charackthe said:
Android System and SystemUI overlays disable itself in every reboot and don't work properly in the first place! In my S8+ everything works fine. The theme is compatible with both. What is going on?
Click to expand...
Click to collapse
Did you disable com.samsung.android.themestore and com.samsung.android.themecenter ?
Try disabling those and reinstall the overlays again.
Also, are you on Nougat or Oreo?

Ripthulhu said:
Did you disable com.samsung.android.themestore and com.samsung.android.themecenter ?
Try disabling those and reinstall the overlays again.
Also, are you on Nougat or Oreo?
Click to expand...
Click to collapse
On Oreo and no I haven't disabled Samsung's native theming application. I only switched it to the default theme and thought I'd be fine. I'm going to try this in a moment.

My work around is don not set the display to adaptive mode so that themes will stick.
Sent from my [device_name] using XDA-Developers Legacy app