I am on stock rom, using SuperSU 2.66. I have tried using texdroider_dpi and one other app but they cannot change my dpi. It says it sets but then I reboot and I'm stuck on 560 dpi. I changed dpi in adb but some elements don't work such as my Swiftkey, the little blue diamonds for top devs in play store.
I assume this is a SuperSU issue but these DPI apps have worked since I first rooted this phone back in November. Only the current update has broken this.
Has this happened to anyone else?
Sent from my Nexus 6P using Tapatalk
italianstallion11 said:
I am on stock rom, using SuperSU 2.66. I have tried using texdroider_dpi and one other app but they cannot change my dpi. It says it sets but then I reboot and I'm stuck on 560 dpi. I changed dpi in adb but some elements don't work such as my Swiftkey, the little blue diamonds for top devs in play store.
I assume this is a SuperSU issue but these DPI apps have worked since I first rooted this phone back in November. Only the current update has broken this.
Has this happened to anyone else?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Texdroider works fine for me on su 2.66 with cataclysm and franco kernel, what rom are you using? maybe try reflashing.
Related
Hey all,
Was looking to get some help with my Nexus 7. Recently, certain apps in the Play Store do not show up in searches. When I link to them directly from the internet I get the "not compatible with your device" message. And, for the life of me, I cannot figure out why.
I am rooted, running the latest stock JB, and stock recovery. I have my DPI set to 175.
I thought that if I restored my device to stock, re-rooted that would fix it. Well, it did. For a while. I was able to get my apps installed, but now when trying to update, same thing occurs, I get the same compatibility problems. Is there some way around the device check in Play Store?
Any ideas or assistance will be greatly appreciated!!
Never tried it myself, but with the app Lucky Patcher, you can patch play store. Google for it.
This is what happen when you change dpi... If you want to stay with this dpi you have to flash a multi dpi play store GO HERE
Phone: GT-I9100P
Kernel: Dorimanx >Development Thread< >Help Thread<
ROM: 4.2.1 Vanilla RootBox >Development Thread< >Help Thread<
Tablet: Nexus 7
Kernel: M-Kernel+
ROM: 4.2.1 Vanilla RootBox
Nico_60 said:
This is what happen when you change dpi... If you want to stay with this dpi you have to flash a multi dpi play store GO HERE
Click to expand...
Click to collapse
Awesome! worked perfectly! Thanks!
http://forum.xda-developers.com/showthread.php?p=37326035
may work, I havnt tried yet, will soon...
Sent from my Nexus 7 using xda premium
Hi, im very new at this, and I was wondering if there was any way that I can install the new releases of Omega Rom without loosing my data like, i install only rom, and rest of the apps and setting stay the same? Is that possible? Because everytime I flash a new version I loose my dpi setting at Texdroider DPI and in Xposed Framwork - App Settings and the whole app Xposed get removed aswell..
I don't think you can.
Sent from my SM-G900F using XDA Free mobile app
Ohh.. It's kinda annoying to have to reinstall Xposed and change dpi on 8 apps every single time I update my ROM :-\
Bump need more input to be sure if I'm just not an idiot.
Rooted & stock 6p owners, please check if this app is available on Play Store? [Poll]
Hello,
Here is the Play Store link:
https://play.google.com/store/apps/details?id=com.billguard.android
From your 6p, please let me know if this app is available to you and if you're full stock (unrooted) or rooted. Please respond to the poll in this thread.
Why?
I currently have six active rooted phones (6p, N6 and a few Samsungs), five can download and install the app. On my rooted 6p, PlayStore shows that the app is not available. I contacted support, they keep blaming root, despite my data showing that other rooted phones can download and install the app just fine.
On my 6p, I am rooted using the stock image with no mods to the build.prop. I would like to know if you are rooted, can or cannot download the app, or if you're stock, can or cannot download the app.
BTW, I know I can simply use the .apk from one of my other phones to install on my 6p.
Thank you.
Fine on my rooted 6p, Xposed too. I didn't install it, but the listing shows in Google Play.
Do you have a modified DPI/build.prop or anything?
fury683 said:
Fine on my rooted 6p, Xposed too. I didn't install it, but the listing shows in Google Play.
Do you have a modified DPI/build.prop or anything?
Click to expand...
Click to collapse
snovvman said:
On my 6p, I am rooted using the stock image with no mods to the build.prop.
Click to expand...
Click to collapse
Strange... now I'm lost as to why my Play Store says it's not available... Thanks for the report.
Contacted BillGuard, they say "Nexus 5p is not supported"
I contacted BillGuard with this question and they said they do not support Nexus 6p. I was surprised and asked why. They said "the screen size of Nexus 6p is larger than other screens". This makes no sense to me, but that was the response from the support rep or whoever responded to the email.
My phone is not rooted but I have changed the DPI via adb. I thought this was the reason, but I don't know if the Play Store decides compatibility, and if it is based on DPI (rather than phone models). I will try to change the DPI later and check.
Rooted, Xposed, stock image / kernel, and it was available for me. Downloaded and everything
jparnell8839 said:
Rooted, Xposed, stock image / kernel, and it was available for me. Downloaded and everything
Click to expand...
Click to collapse
Have you changed your DPI or is it stock?
It says my device isn't compatible, but I'm running a custom ROM and am using a custom DPI (440).
Root and works for me. I'm also on the pure nexus rom if that may help with anything.
6p, rooted, stock ROM, multiple xposed mods and it's available for download for me as well. Stock DPI settings as well. Strange.
xudox said:
They said "the screen size of Nexus 6p is larger than other screens". This makes no sense to me, but that was the response from the support rep or whoever responded to the email.
Click to expand...
Click to collapse
The devs of Thomas Was Alone will tell you the same thing. When they released the game, the "X-Large" or "Large" screen size didn't exist or Google redid the specs for app screen sizes, so they haven't updated it since. It's rather frustrating because the game ran fine on my Galaxy S4, I just want to play it on my big shiny 6P now.
So it all boils down to the dev hasn't taken the time to test how the app looks on a larger screen and hasn't published it with the new screen guidelines.
rooted chroma, google play web page shows that is available for me.
When I started the thread, I had previously modified the DPI, but later returned it to stock. The app was still unavailable. I later flashed a new stock build, the app reappeared in Playstore. Changed DPI again, and after two reboots, the app disappeared. Thereafter, the app never reappeared, even when I returned to stock DPI. Lastly, I cleared Playstore data--the app came back. Now all is well.
So the brief version of what I just articulated: You need stock DPI. If you previously changed the DPI and returned to stock, clear data on Playstore....
As much as I would like to run a different DPI, enough apps disappear that makes it not worth the trouble. Custom Playstore builds are possible but it's a pain. There is an Xposed module, but it does not work with MM.
Rooted, running pure Nexus and custom dpi (520), unavailable for me.
Rooted stock
xudox said:
Have you changed your DPI or is it stock?
Click to expand...
Click to collapse
Stock DPI. The only thing I've changed away from pure stock is root, Xposed, APM+, Snapprefs.
snovvman said:
When I started the thread, I had previously modified the DPI, but later returned it to stock. The app was still unavailable. I later flashed a new stock build, the app reappeared in Playstore. Changed DPI again, and after two reboots, the app disappeared. Thereafter, the app never reappeared, even when I returned to stock DPI. Lastly, I cleared Playstore data--the app came back. Now all is well.
So the brief version of what I just articulated: You need stock DPI. If you previously changed the DPI and returned to stock, clear data on Playstore....
As much as I would like to run a different DPI, enough apps disappear that makes it not worth the trouble. Custom Playstore builds are possible but it's a pain. There is an Xposed module, but it does not work with MM.
Click to expand...
Click to collapse
I can confirm this is working. I changed DPI back to stock, waited for a day or two and cleared Play Store data and now BillGuard is available for download. I don't know why app developers would put a hard dependency on DPIs.
As the title says, not just the launcher but the whole system.
I think you'd have to flash the xposed framework and use unicon to theme it, or you can apply the themes from the galaxy themes store, which also change the icons system wide.
Hope I helped!
I am interested in this too. Samsung has the worst icons and kid-like colors. Coming from HTC, I can't stand the TouchWiz theme. I was forced to install Nova launcher, but I would like settings to be themed aswell. I saw a screenshot of someone's modified settings theme and I think he, too, claimed he used Xposed. I have Xposed installed, but I don't know what to search for in Xposed to have my settings change color. He had a 'double row' mod that also changed the skin. Anyone know how?
Ugh. I don't wanna root my phone.
FuryFlames said:
Ugh. I don't wanna root my phone.
Click to expand...
Click to collapse
There is no way I would ever use a phone with no root. AdAway is something I cannot live without. Why don't you like root?
Sent from my SM-G935F using Tapatalk
schn1tt3r said:
There is no way I would ever use a phone with no root. AdAway is something I cannot live without. Why don't you like root?
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Cause of Knox and I used to go crazy with rooting and custom ROMs and kernels on my nexus 4 but all it did for me was introduce bugs and reduce performance. Besides, how would I even root without losingh everything I have atm? It'd be such a huge pain.
Yeah I wouldn't mess with kernel modifications. I just root stock for AdAway or use the most stable ROM nothing too crazy.
Sent from my SM-G935F using Tapatalk
schn1tt3r said:
Yeah I wouldn't mess with kernel modifications. I just root stock for AdAway or use the most stable ROM nothing too crazy.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
I even used to overclock and underclock, undervolt and download tons of Adreno GPU drivers.....I was crazy back then
FuryFlames said:
Cause of Knox and I used to go crazy with rooting and custom ROMs and kernels on my nexus 4 but all it did for me was introduce bugs and reduce performance. Besides, how would I even root without losingh everything I have atm? It'd be such a huge pain.
Click to expand...
Click to collapse
What do you mean by "losing everything you have atm"? CF-Autoroot doesn't require wiping anything, only flash custom ROMs do.
Im stock 7.1.1 rooted and unlocked with the v5 and v6 flashable zips for Pixel features and the pixel home button animation. Before I rooted snapchat was fine but now its saying my login temporarily failed, like it would do if I had xposed framework. ANyone else have this problem or know a solution?
U will have to unroot and log in to Snapchat then re flash SuperSU
Sent from my Pixel XL using Tapatalk
scoot0073 said:
U will have to unroot and log in to Snapchat then re flash SuperSU
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
How do I temporarily unroot without erasing data or system?
Also, I tried the full unroot option if SuperSU and my device wouldn't boot and got stuck on Google splash screen until I flashed root again. When I did the unroot option, after the initial "your device can't be trusted" screen, another one of the same kind popped up but this time in RED letters and said my device was corrupted and that's when it stuck on the Google screen so I rerooted it
Have u tried Googling it ?
Like How to unroot using SuperSU
Maybe there's something that u missed. I never personally tried unroot through SuperSU but I have read many peeps doing it that way.
Sent from my Pixel XL using Tapatalk
scoot0073 said:
Have u tried Googling it ?
Like How to unroot using SuperSU
Maybe there's something that u missed. I never personally tried unroot through SuperSU but I have read many peeps doing it that way.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes I've tried and that's what got me jammed up
Oic .. well idk sorry I wasn't much help. Good luck
Sent from my Pixel XL using Tapatalk