yashsingh1/xdaforums huggingface dataset:
[Android Software Development] sirovai:
Hi, i've change the DPI with textdroider app then i lose compatibility with Amazon. After that i found this thread :highfive:

Ran your programme and applied changes with the flashable zip.

It seems all perfect but Amazon is still not compatible. I've also clean play store data.

Can you help me?

Thanks

EDIT: wipe cache and dalvik after repeat procedure with "online" modify and all its perfect!

Good Work!
[Android Software Development] jgruberman:
Oddly enough, I used this tool, the phone rebooted, cleared cache and dalvik, rebooted again, and no change... any thoughts?
[Android Software Development] hamsteyr:
No changes in terms of phone DPI, or play store compatibility?

What version of android are you running, what rom and what device?
[Android Software Development] jgruberman:
No changes anywhere, yet the build.prop shows 480 as the density...

Android 4.3

Galaxy Note 3

FireNoteMJ5 Deodex V6x
[Android Software Development] hamsteyr:
480 is the default density for the Note 3 if I'm not mistaken. Changing it to values lower should work just fine. I used it on my GNote3 with X-Note on 4.4 and it seems to be fine.

If it doesn't... then it could possibly be a property of the ROM maybe. I'm not entirely sure.
[Android Software Development] jgruberman:
I may not be understanding it correctly to begin with. So bringing it from 480 to say 320 will make the icons/text smaller? The smaller the density, the smaller the stuff on the screen?
[Android Software Development] hamsteyr:
That is correct sir. Throwing values down will make it smaller, as I'm running my Note 3 on 320.
[Android Software Development] jgruberman:
So TBH, I just may have misunderstood or just straight up not had a clue :) I'm trying to bring it to 320 now and see what happens.

Side question: I had a ROM that had a DPI of 290. If I set it to that for the actual screen size, what standard size should the play store be? The next closest above?(320) or the next closest below?(240)?
[Android Software Development] hamsteyr:
@Chevyguy85 Try doing a Play Store and Framework Wipe again, alongside another Dalvik-Cache wipe. I find that sometimes for whatever reason doing it manually the second time around makes it work.
[Android Software Development] hamsteyr:
Guys, for those who are still having Force closes, check out the latest version that I have just released. I switched to a new technique in terms of building the modified APKs, and I've tried it out on the latest Gapps, NO FORCE CLOSES and working PERFECTLY :D

with that said, yes, v1.1 is out for downloads, download it, try it and let me know how it goes :3

Enjoy.
[Android Software Development] Chevyguy85:
Re: [TOOL] Google Play DPI Fix (Custom DPI, Modded GSF, GB, ICS, JB) - v1.1 (4/2/13)

Nope no dice. Thanks for the effort though.

Sent from HTC's "too hard to implement ICS" Inspire 4G running JB
[Android Software Development] tjsas1:
Hi I am having Error retrieving information from server[RH-01]
[Android Software Development] hamsteyr:
@Chevyguy85 Try the latest version, see if that fixes it for you

@tjsas1 Click on Retry, and it should work. That usually happens to me everytime after I've run the tool. If not, you may have to wipe Play Store and Google Services Framework again, and remove your google account and readd it.
[Android Software Development] galonpzw:
I got it too but only once, after clicking OK it never appear. Did you wipe cache and dalvik? Try it, and if not working try clearing Google Play data.

@hamsteyr Great work, all working4me :)

ps. what is that Performance Control on the screenshot?
[Android Software Development] tjsas1:
Yes I did wipe both cach and dalvik. I 'll try clearing the Google Play data if it will work for me.

Thanks! Will give feed ASAP
[Android Software Development] jajosh66:
You truly tried...

I tried using v1.1, but it's still force closing. I wiped cache and dalvik You really tried though. I give you your efforts.:good::good:
[Android Software Development] hamsteyr:
._. Argh. I really thought the latest version would fix all of this.

May I know the Device, ROM, Android version and Gapps version (if applicable) ?
[Android Software Development] TheSchatz:
Just putting this out there, but after a "failed" attempt (force closes etc.) with 1.0a, I reflashed gapps, wiped cache and dalvik, and fixed permissions.

Since then everything works fine, and my DPI is set just as I wanted at 300. Those having issues may want to try it, though it may be defeating the purpose of the mods this tool makes...
[Android Software Development] galonpzw:
Guys test v.1.1. This works like charm to me
[Android Software Development] Chevyguy85:
That last try yesterday was with the latest version 1.1. Same result as 1.0a a couple hours before that.
[Android Software Development] frickinjerms:
"Error Hit" using 1.1 on my evo 4g (ipod replacement)

got to "pushing modified APKs into /system" and that popped up..

i have ro.secure=1 in default.prop in my ramdisk soooo maybe thats why?

and the modded build.prop still had my dpi at 240 so i maunally changed it then pushed all the files to their respective directories in my device thru recovery and then wiped dalvik and cache andddd bootloop haha craaaaap

and pushing the originals it made to my device didn't fix it.. ::confused:

nor did a factory reset haha time to reflash *facepalm* i doubt its your app at this point. my bad
[Android Software Development] galonpzw:
Did u turn this on ?

" Root Access set to 'Apps and ADB' in Developer Options on certain devices "

I've update CM10.1 to today nightly, and DPI go back to default.. i use app to change and its working without problems.

Galaxy S2 CM10.1 Dorimanx Kernel

Guys check this : http://xdaforums.com/showthread.php?t=1839871
[Android Software Development] hamsteyr:
@frickenjerms As galonpzw said, it's more likely that you didn't turn on the root access.

You're getting a boot loop because you manually pushed in build.prop without setting it's permissions. After pushing it in you need to do this:

adb shell

su

chmod 644 system/build.prop

Bootloops are caused by incorrect permissions of build.prop :|

Try this again and tell me how it goes
[Android Software Development] hamsteyr:
As for those people still getting force close errors, I'll do more extensive testing to see what's going on.

@Chevyguy85 Copy Pasta from a different post,

May I know the Device, ROM, Android version and Gapps version (if applicable) ?
[Android Software Development] Chevyguy85:
Inspire 4g (desire HD equivalent) running Jellytime R30, Android 4.1.2, and Play version 3.10.10 if I'm looking in the right place. When I did it with v1.0a it did replace the files as I checked the modified date on the phone so I know it's at least doing what it's supposed to do in that sense.

Also as a side note on both v1.0a and v1.1 it never completed the process the first time. It would get to the step of sending the files back to the phone and just sit there. Force closed the program and re-ran it and both times it worked fine. Don't think this hurts anything just figured I'd put that out there. Also I don't think my phone plays nice with dpi changes anymore as I haven't been able to change for quite a while now so it's probably more of a hardware vs your software.
[Android Software Development] hamsteyr:
Interesting, mostly because I have tried this on an actual DHD and it works just fine, running Jellytime as well.

If it's having problems pushing it into the device, it's most likely that the program was unable to get adb root access onto your device. Manually pushing in the new APKs and the build.prop would work (you need to then change the build.prop permissions to 644 or you'll get a boot loop)

I really don't know if it's anything to do with your hardware as much as it may have to do with the software. As I know it, it's usually always the software that causes these kind of problems. The only last resort thing I can suggest is the following:

- Reflash the latest gapps if possible

- Go into Settings -> Apps and Force Close and Clear data for both Google Play Store and Google Services Framework

- Go into Settings -> Accounts and remove your Google Account

- Run the application (noting any errors that may happen, if unable to push the files back into the device, you may have to do so manually, feel free to ask if unsure how to properly)

- Once Rebooted into recovery, Wipe the Dalvik-Cache and Cache, then reboot the device.

I have noticed that somehow this app works best on fresh installs with no Google Accounts attached, and Play Store hasn't been launched (right after first boot), but I may be wrong in this. I was getting some errors as well when running with an existing google account, though not all the time.
[Android Software Development] Chevyguy85:
Okay then my phone just hates me...fail. I'll have to try the clean install if I ever decide to update to Jellytime R5 or whatever is out when I get around to updating again.
[Android Software Development] hamsteyr:
Yep, I just got the notification of Jellytime 4.2 :P Let me know how it goes when you do.

Also, another strange thing, some roms HATE having their Play Store and Framework modified. Really unsure why. Just like how I was working on my APK Batch Installer yesterday, and I realised a specific rom HATED its app data restored via adb, where I have used countless and they're perfectly fine.

Android is such a vast and varying ecosystem that it's really hard to tell when things will play along with each other and when they won't :\
[Android Software Development] hamsteyr:
haha, not a problem.

Standard size for play store is what your phone's original setting is, in this case 480 DPI. In general, there haven't been any issues with people setting it to other values, i.e. 320 dpi, but I like to stay on the safe side of things.
[Android Software Development] jgruberman:
Makes sense, thanks!

What happens when there are comaptibility issues with apps? For example, my Gallery only shows about half the pictures, but I can scroll just fine... it just only uses the top half of the screen for displaying pictures.. if that makes sense.
[Android Software Development] hamsteyr:
It means that your ROM wasn't built with Mutli DPI Compatibility in mind. You could look for multi dpi versions of that application, or you could try using AOSP gallery instead. :)
[Android Software Development] hysterisis:
Applications Incompatible

Hi,

I would like to thank you for the great tool that you have created for the community. It is extremely useful for Samsung users who otherwise would have to live with the higher DPIs. After my recent factory reset to CM11 M6 snapshot (using ART) on my Galaxy S2, I updated the DPI to 200 using the DPI Fix tool. The DPI has got updated to 200, but the applications have started showing up as incompatible.

After flashing the recovery zip, I had cleared my cache and dalvik cache.

Request your help.
[Android Software Development] Kord:
Also have this problem, but on MultiDPI PlayStore.

Seems that Google updated something that crashes this workaround.

Regards :good:
[Android Software Development] yoyo81:
Nexus 5, 4.4.2 No Connection

I've attempted to run the tool on my Nexus 5 running kitkat 4.4.2 and version 1.4.2 of this tool. Upon clearing caches and rebooting, Google Play Store shows "no connection" with a retry button. Clicking the retry button doesn't do anything. The Google Play settings pop up, but the error message stays. My current DPI setting is @ 350. No amount of coaxing allows a connection to occur, and I have to restore from backup to get a working Play Store back. Here are my steps:

1. Enable usb debugging

2. Run your tool

3. Reboot into recovery

4. Clear Dalvik/system caches

5. Reboot into system

6. Click Google Play Store

At this point I get the no connection message with the retry button.

Steps I've tried to get it working

1. Clear data/cache for Google Play Store

2. Clear data/cache for Google Services Framework

3. Attempt to restore to Originals using your tool (no change in behavior)

Finally, I restored from backup. Thinking it was a fluke, I repeated this entire process with the same results. Any ideas? Thanks.
[Android Software Development] hamsteyr:
It may be updates on Google's end that is causing this. I'll look into it.
[Android Software Development] yoyo81:
thanks! Let me know if there's anything I can do.
[Android Software Development] hello00:
true..im not getting no connectivity on play store..4.4.3
[Android Software Development] F4M0U569:
Hi, any news?
[Android Software Development] hamsteyr:
Sorry for the delay, I haven't had much time to look into it just yet, work has been pounding down quite hard these few days. :\
[Android Software Development] hello00:
np take ur time
[Android Software Development] ghpk:
Earlier this tool helped me edit the DPI,

Tried last night and ran into Same problem playstore fails to connect.

Running Nexus ported 4.2.2 ROM on MTK6577 512MB RAM Based device

had playstore 4.8.20 and edited only playstore DPI, keeping device DPI same as before.

first it gave some error about vending.apk not present, etc etc, then i clicked cancelled still it proceeds and upon reboot after clearing dalvik the playstore erros starts.

I am also see syncing error and wi-fi icon is not getting blue however apps do have connectivity using same wi-fi.

Can this be related to editing of "Google Service Framework APK" by the tool cause only two files are edited and playstore.apk should not affect wi-fi connectivity.

Tried clearing data of playstore & Google Service Framework APK but still issues.

Then I found my full titanium backup from last week, and restored playstore and Google Service Framework APK without DATA.

rebooted to recovery, and cleared cache partition and dalvik cache

rebooted

and oopssss still can't connect to playstore via WI-FI or 3G.

So I am quite sure it can be a messed up build.prop.

will be restoring it tonight and update you guys here.

Edit:

I am sure the issue caused due to truncated build.prop after I ran this tool, compared the build.prop

and it was truncated after modding.

tried restoring previous version of playstore and GSF & build.prop , didn't helped.

phone is not syncing either.

These problems should come up with just DPI edit, but I am sure I've not installed or moded any files

in last 24 hours since when these problems came up.

anyway as phone is still working I am able to backup my user data and would re-flash tonight ;)
[Android Software Development] negativman:
The program has stopped working. As I understand it with access to the CM11 has changed. The program asks for the driver and ADB, although it's all there on the computer, and the system is not reset! I also use Win7.
[Android Software Development] frozen01:
i use this and change dpi

but i have problem how fix this ?

and how edit dpi in apps ?
[Android Software Development] hamsteyr:
That's caused not by my app, but rather the widget not being able to scale properly. Nothing I can do to fix that. This app doesn't do per DPI scaling. Its all global.
[Android Software Development] frozen01:
Can fix this file for 380 and 400 Dpi ?

http://www.mediafire.com/download/dwxf2ea9adg8ijy/a.zip
[Android Software Development] WNSTNSNRS:
Thanks!

Sent from my Nexus 5

ROM: ParanoidAndroid

Kernel: franco.Kernel

Capacity: 16gb
[Android Software Development] WNSTNSNRS:
After using this app. No more dpi issues. But after a few hours or minutes or after a several reboots. It's reverting back to default. Why is it like that?
[Android Software Development] hamsteyr:
Could be another app that's setting it back to the default settings.
[Android Software Development] integramodder:
Is there a modern solution for this problem for those running 4.4.4? Um on Mahdi ROM and experiencing the play store filtration issue a lot more lately...
[Android Software Development] hamsteyr:
You could install Xposed Framework if you wish, that's one of the ways. They have a play store patcher I believe there.
[Android Software Development] negativman:
My question so no one answered. The program has stopped working! It does not work with firmware 4.4.x?
[Android Software Development] hamsteyr:
Sorry for late reply, have really been busy these past months. May be a thing with the ROM that you're using it on. I haven't had the time to test it out on all devices, or on the latest play store revisions.
[Android Software Development] negativman:
When the program issues this window. As I said before all the drivers on your computer are and all permissions are given.
[Android Software Development] hamsteyr:
may just be a matter of ADB version not being updated to support 4.4

I'll try to publish a test version with newer ADB for you guys to try out to see if it works.
[Android Software Development] negativman:
Is there any news?
[Android Software Development] t3chwizard:
Works fine for me on 4.4.4 although the process doesn't do anything for me because I still can't download apps afterward that I couldn't before.

---------- Post added at 03:10 PM ---------- Previous post was at 03:08 PM ----------

For anyone who is interested or not. Please sign my petition for Google to allow us to download apps with custom DPI on our devices. Here is the link to the petition https://www.change.org/p/google-inc...app-on-the-play-store-regardless-of-their-dpi
[Android Software Development] hamsteyr:
My apologies. Between work and travels, I haven't had much time to sit down and make the necessary changes and checks. I'll try and get onto it as soon as I can.
[Android Software Development] integramodder:
Not to rain on your parade hamsteyr, but MyLifeRocks10 has an alternate solution that is working. It does require downloading his play store app, but it allowed me to download apps that were otherwise said to be incompatible with my device. Maybe you guys could tag team the problem and make a better solution.
[Android Software Development] hamsteyr:
No issue, I do base most of what this app does on his work, though mine obviously does it on the fly rather than needing to side load a lot of it. Either way, until I find a good fix for this, I've reverted to using the Xposed App with Play Store Fixes that does the job just fine :)

Also, that capitalised massive link. hahaha.
[Android Software Development] t3chwizard:
Why don't you sign this petition, and if it works none of these hacks will be necessary anymore. https://www.change.org/p/google-inc...app-on-the-play-store-regardless-of-their-dpi
[Android Software Development] hamsteyr:
Well, sounds like a good idea (and I see that you're the petition organiser) but i'm not sure how well it'll be heeded. Either way it does save a lot of hassle if it doesn't have to be worried about anymore. Not really sure why they have these in place though. Would it not be easier to identify things by their class? Or maybe a lot of applications on the play store are broken at different DPIs, hence this move would create more problems than it solves, as it would inadvertedly cause some users to drop bad reviews for apps that don't scale their UI properly mostly because it wasn't designed for their devices?

I don't know man, it's a lot to think about :/
[Android Software Development] t3chwizard:
Half of the apps that are said to "not work" work fine. Google needs to find a better system of organization for deeming apps not compatible with devices. They should give the consumers the choice to have their filter in place or not, why should they limit our app selection if we don't care about apps not being compatible. At this point I am willing to take the risk. Because these restrictions annoy the crap out of me.
[Android Software Development] integramodder:
Signed.
[Android Software Development] gd6noob:
This is a good tool.. I can finally have access to all apps after changing the DPI...

Quick question... Do I need to use the tool everytime I change to another DPI or use it once and then I can change it manually via build.prop?
[Android Software Development] gd6noob:
TTT
[Android Software Development] cc546:
Not working. Now I am getting FCs, even after reverting to original. Fixing permissions didn't help.
[Android Software Development] hamsteyr:
There are quite a bit of incompatibility issues with this tool and newer versions of android. If you're using 5.0 and above, I don't recommend using it, not until a newer version is out.
[Android Software Development] cc546:
I am using 4.4.2. I tried reinstalling gapps, but I still cannot open Play Store. Is there anyway to fix this without wiping data??
[Android Software Development] hamsteyr:
Hmmn that's very weird then. Try pushing the backups back in or reflashing a Gapps package.

What I think is going on is that for some reason, the permissions for the new files aren't set correctly, and it's causing this to happen, and the fix permissions script doesn't always fix this (in fact it bricked my OPO on android 5.0)

Try that. Sorry for the inconvenience. :/
[Android Software Development] cc546:
No it's my fault for not having a nandroid backup. Anyway for some reason after I deleted the Phonesky.apk in priv-app play store is working again...Weird. Thanks for your help.
[Android Software Development] hamsteyr:
I forgot that they made that change as well post kitkat. Some system apps are no longer kept in /system/app but some in /system/priv-app. The conflict of having the same of two apks, one in each may have been what caused it.
[Android Software Development] t3chwizard:
I posted this a while back but the changes Google has made in Lollipop along with the DPI problem are annoying me now. Please sign my petition https://www.change.org/p/google-inc...app-on-the-play-store-regardless-of-their-dpi. I want this issue resolved because all these DPI fixes are very tedious and if Google would just fix it on the server side we wouldn't have to do all this stuff.
[Android Software Development] negativman:
Will optimization for CM12 ?
[Android Software Development] Chevyguy85:
Yeah I will. Not exactly hopeful as it's been a problem even before JB, oh well, even after almost 2 years on a touchscreen I still can't type so smaller keys is probably not a good thing.
[Android Software Development] hamsteyr:
Lol, hahaha, but real estate is always nice :P You could probably get away with still typing in a smaller dpi heh
[Android Software Development] Tungstwenty:
Hi all,

I landed on this thread after seeing the article on the portal.

I just wanted to let everyone know that there's an alternate way to achieve custom DPI (which by no means depreciates the approach of the OP).

The main idea is to use Xposed, which is a framework that allows developers to create all kinds mods without ever touching the original apks.

One of the existing mods (for which I'm a co-author) is precisely a configurator for the settings that each individual app will use when running. It is therefore possible to change the DPI on a per-app basis, to your liking, and if you don't change the one for Play / GSF then it will be "stock DPI" for the market purposes.

A downside, at least for now, is that you'll need to configure each app individually. Bulk changes are still on the todo list.

With that respect, and from what I can see, the OP's approach is much more practical - just patch the 2 apks and you can then change the DPI system-wide. On the other hand, some apps won't render properly in different DPIs (e.g. some Samsung stock apps, launcher, ...)

Here are the links for those interested in giving this a try:

http://xdaforums.com/showthread.php?t=2012770

Thread created by pulser_g2 discussing the various existing mods. On the 3rd post there is a link to a repository he set up so each author can post mods and updates himself.

http://xdaforums.com/showthread.php?t=1574401

The framework required for the mods to run. This needs to be installed once with root, after that it's no longer required not even for the mods. (no support for GB)

http://www.villainrom.co.uk/forum/microdownloads/xposed-app-settings.5/viewfile

The particular mod I mentioned earlier that allows you to customize apps' DPI, among other settings.

Cheers,

TT
[Android Software Development] deathtech:
I get the error "adbd cannot run in production builds"

:( This saddens me.