Database Develop

[MOD/HOW-TO] Remove hard key vibes via android.policy.jar

I thought I'd offer my solution to disabling the hard key vibrations on the Atrix since other people might find this useful. This method differs from the other solutions in that it doesn't tamper with your Silent Mode vibrations (like StreakVibrations does) and it's code based, so it shouldn't tamper with any themes you have installed (like the framework-res.apk method). It is firmware dependent though since it's a code modification.
You'll need an android.policy.jar modified for your firmware.
What I'm doing is I'm modifying the method called performHapticFeedbackLw, and telling it to skip triggering the vibrate pattern for all effects (there are 5) except for keyboard taps. Long press vibe, virtual key vibe, safe mode disabled vibe, and safe mode enabled vibe will no longer trigger... Incidentally, does anyone know what safe mode on this phone refers to?
To use the file, you need to be on Bell, Telstra, GingerBlur, Gladiatrix or stock ATT 1.8.3 firmware, and be deodexed. Can you copy the file to your phone without being deodexed? I don't know. I'm a programmer, but an Android newbie so just to be safe it's best if you're deodexed.
Before you try anything, obviously make sure you are backed up. At least copy your existing android.policy.jar so that you can restore it if necessary.
All you need to do is either:
a) Run the novibes.bat script packaged in the zip. There are a couple prerequisites:
1. Make sure to set your USB connection to "None" on your phone.
2. On your phone, go to Settings > Applications > Development and make sure USB debugging is turned on.
3. Plug your phone into your PC and let it install any necessary drivers.
4. Then you can run novibes.bat.
or
b) Follow the steps outlined below to do it manually:
1. Replace /system/framework/android.policy.jar with the one that I've attached.
2. Make sure the permissions of the file are set to rw-r--r-- (thanks for reminding me, Meloy and for correcting, natboy!). The easiest way is to use Root Explorer, long press the file, choose permissions, and set owner: read/write, group:read, others:read. Otherwise, use Terminal and type "chmod 644 /system/framework/android.policy.jar" without the quotations.
3. Reboot.
For those not on stock Bell, I'd be willing to modify your android.policy.jar and post it here if you provide somewhere for me to download it, and specify what firmware it comes from. It's quite quick to do once you're set up so I don't mind. Alternatively, make the change yourself:
1. Download baksmali and smali (both .jars and scripts, total 4 files).
2. Copy /system/framework/ from your phone to your computer.
3. Copy all the files from step 1 to the framework directory from step 2 on your computer.
4. Unzip android.policy.jar and copy its classes.dex file to the framework directory on your computer.
5. From the command line, navigate to the framework directory and run "./baksmali classes.dex". It will create a directory named "out".
6. Open "out/com/android/internal/policy/impl/PhoneWindowManager.smali" in a text editor.
7. Search for a method called "performHapticFeedbackLw". Go to near the bottom of that method, and you will see the Dalvik bytecode representation of a switch statement:
Code:
.sparse-switch
0x0 -> :sswitch_27 #This is for long press vibe
0x1 -> :sswitch_35 #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :sswitch_3b #This is for safemode disabled vibe
0x2711 -> :sswitch_3e #This is for safemode enabled vibe
.end sparse-switch
8. Here's an example of how you might want it to change. Basically you want to replace the original goto labels with one that causes the method to step out without triggering a vibe, and that notifies the calling method there was no vibe by returning false. The label to use is called ":cond_1d":
Code:
.sparse-switch
0x0 -> :cond_1d #This is for long press vibe
0x1 -> :cond_1d #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :cond_1d #This is for safemode disabled vibe
0x2711 -> :cond_1d #This is for safemode enabled vibe
.end sparse-switch
9. From the command line in the framework directory, run "./smali -o classes.dex out". You now have a new classes.dex that has your modification.
10. Zip up the classes.dex with the META-INF directory from your original android.policy.jar. Rename the zip to android.policy.jar.
11. Copy the new file to your phone and reboot.
12. At this point you should be done.

Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App

n1ckr0th said:
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.

bearsfan172 said:
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
Click to expand...
Click to collapse
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.

n1ckr0th said:
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
Click to expand...
Click to collapse
Yes, this would work perfectly fine on ATT. You can either follow the instructions I provided, or if you like you can post /system/framework/android.policy.jar from your phone somewhere and pm me the link so I can download it and I'll do it for you. Also mention what firmware you're on. I just don't want to download hundreds of MB of firmwares which is why I didn't set one up for all the ATT firmwares.
That other method requires editing a file that is guaranteed to change with any theme you install. That means anytime you change themes you'll need to edit that .apk yourself, or wait for someone to bring the change over. android.policy.jar is unlikely to change for themes.

Ok, I've posted a version for ATT 1.8.3 that was given to me by n1ckr0th.
n1ckr0th, let me know whether it works fine or not. There should be no problem, it looked just like the other 2 versions I modified.
Incidentally, he's using GingerBlur 3.5 so anyone on stock be careful (ie. copy your original file to somewhere else on your phone). It shouldn't matter at all because from what I see, there aren't any resources to modify in android.policy.jar so GingerBlur's should be the same as stock. At any rate, it won't brick your phone if you put the wrong one on. I put Telstra's on my phone by accident and it just messed up the the graphics on screen (maybe because the addresses were all wrong for my phone). You can still use adb, or sshdroid to copy and replace with your original android.policy.jar.

please delete

meloy said:
Don't use this on AT&T 1.83!
After the replace and reboot my phone was really laggy and some applications doesn't start anymore (camera, contacs for example). After i have replaced it with the original file i have still the same problem.
My phone config:
- SBF 1.83
- rooted (GingerBreak 1.20)
- sideloading enabled (GladEnabler)
- GladiAtrix 3 b0.2 ROM
- LauncherPRO
- GingerBread Theme only
Click to expand...
Click to collapse
What? That can't be right, if you still have the same problem after copying the original file, that means that you must have done something wrong. It's a single file change, provided you returned the file to the original, it will be back to the way it was. How did you copy the file? And also, are you deodexed? As mentioned in the original post, you have to be deodexed, because I don't know the results of using it on a non-deodexed system. Your posted config makes it sound like you might not be.

Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.

meloy said:
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
Click to expand...
Click to collapse
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?

maledyris said:
Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.

meloy said:
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
Click to expand...
Click to collapse
Interesting, that never occurred to me. I usually go into terminal and type in reboot to reboot my phone. I think I'll add that to my phone too...

maledyris said:
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.

n1ckr0th said:
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
Click to expand...
Click to collapse
Hmm, how far does it get? Do you at least get to the boot animation? I notice that it may sit at the boot animation for a really long time after changing a file sometimes. Probably updating the cache or something. It's odd that it wouldn't work for you considering it's your file and it worked for meloy. How did you copy the file over?
If you try again, delete the original file, so you can be sure it's no longer there, then try the copy again.

I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?

I have no problems with this mod. It works all fine.

Been waiting on this mod. Streakvibrations has me missing my notification vibes. Thank you

It gave me a red light on boot, stuck at Motorola logo for infinity. I booted into recovery and reflashed gb 3.5 to fix it. Ill try your idea of deleting it then moving the new one.
Sent from my MB860 using XDA App
EDIT: still didnt boot, had to flash again..

I'm getting the flashing red light and rebooting as well. I can't get into CWM though, going to have to flash a SBF. Only think I can think of is maybe the Dalvik cache needs to be wiped before rebooting?
Edit: I'm on an AT&T phone and used GB to deodex as well.. maybe it's not catching all the files..

lurchbyrep said:
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
Click to expand...
Click to collapse
Are you on stock 1.83? Now that we know that android.policy.jar has some mods built into it for Gingerblur pseudo rom, the att 1.83 file I posted probably isn't ideal for stock users.
If you're on stock, maybe you could post your android.policy.jar somewhere and pm me the link to download. Then I could put together a pure stock att one when I get home.
Sent from my MB860 using XDA App

[SOLVED] Apps not showing up in the Market.

To get missing ("incompatible") apps to show up in the Market you will need to edit your build.prop.
You will need root (unlock your bootloader at htcdev.com) and Root Explorer (can do it through adb but Root Explorer is easier).
Open Root Explorer and go to /system and find build.prop. Long press on it and choose Open in Text Editor. Find these lines
ro.product.model=PH39100
ro.aa.modelid=PH3910000
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
and change them to
ro.product.model=HTC Pyramid
ro.aa.modelid=PG5811000
ro.product.brand=htc_wwe
ro.product.name=htc_pyramid
ro.product.device=pyramid
ro.product.board=pyramid
Press the Menu key, Save and Exit. Reboot.
I'm on RumRaider Beta 10 so I'll upload my build.prop if you want to just copy/paste it over your current one.
http://www.multiupload.com/YAMH40C8LW
EDIT:
Apparently, modifying this line
ro.product.device=holiday
Click to expand...
Click to collapse
Is causing issues with the camera making it take shots/recocrd in blue. So, I recommend still following the directions above, but only modify ro.product.device=holiday when you need to update/download apps and once done, change it back to ro.product.device=holiday to use the camera again.

Do not use these settings if you own a rogers/Bell HTC raider! Changing them will turn all of your X710a's pictures/video blue! I can not speak for other versions of the raider but the x710a is affected. I just figured this out after playing with all the settings in the camera app, and I even contemplated calling HTC!!! I had to revert the values back to original to get the camera to work normally.

Hmm, I noticed that issue to but just thought it was the Rom. That's interesting. Anyways, I fiddled around with the settings and discovered that it was this line that messing up the camera
ro.product.device=pyramid
So I'd recommend the switching this back to 'holiday' and when you need/want to download (or update) an app, simply switch this back to 'pyramid' and when your done restore it back to holiday.

What are the apps that we are expected to gain? Can you give us an idea what we are missing out on?
You can't know your limits until you exceed them.

The apps I gained were GTA3, Order and Chaos Online, Snapdragon GameCommand, and Desert Winds.

has anyone tried playing order and chaos after changing the file name back to correct the camera issue? I have read elsewhere that the game will give you issues on rooted devices

Spartoi said:
To get missing ("incompatible") apps to show up in the Market you will need to edit your build.prop.
You will need root (unlock your bootloader at htcdev.com) and Root Explorer (can do it through adb but Root Explorer is easier).
Open Root Explorer and go to /system and find build.prop. Long press on it and choose Open in Text Editor. Find these lines
ro.product.model=PH39100
ro.aa.modelid=PH3910000
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
and change them to
ro.product.model=HTC Pyramid
ro.aa.modelid=PG5811000
ro.product.brand=htc_wwe
ro.product.name=htc_pyramid
ro.product.device=pyramid
ro.product.board=pyramid
Press the Menu key, Save and Exit. Reboot.
I'm on RumRaider Beta 10 so I'll upload my build.prop if you want to just copy/paste it over your current one.
http://www.multiupload.com/YAMH40C8LW
EDIT:
Apparently, modifying this line
Is causing issues with the camera making it take shots/recocrd in blue. So, I recommend still following the directions above, but only modify ro.product.device=holiday when you need to update/download apps and once done, change it back to ro.product.device=holiday to use the camera again.
Click to expand...
Click to collapse
This method doesn't seem to work anymore.. in the play store it will still list it as incompatible.. unless there is something else needed to be done?

[Q&A] [ROM][GPL]Clean_Cm_7.2[26-05-2014]

Q&A for [ROM][GPL]Clean_Cm_7.2[26-05-2014]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Possible bug
First of all: Awesome ROM! Never knew CM 7.2 could be this fast and stable!
Second: I've possibly found two bugs:
1, Entering "Settings/CyanogenMod Settings/Lockscreen settings/Delay and timeout" always cause a FC.
Always.
Have tried rebooting and shutting down but the FC remain.
2, Power button does not activate lockscreen, it only shuts the screen off. Pressing power button again or home button will go directly to home screen. The only way to activate lockscreen is to let screen timeout.
Have tried different screen locks but nothing makes power button behave differently.
I've searched around in setting for a way around this but so far unsuccessfull.
Maybe the two issues are related.
And now some requests:
* A big button keyboard? Stock was good with big buttons for my sausage fingers.
* Ability to easily add foreign language keyboards (not system language) and dictionaries.
* Remove delete thread confirmation in messages.
* Remove confirmation when enabling storage by USB connection.
* Ability to easily add sounds without trying to find the setting for each event. Still haven't found out how to change the alarm sound...

I'm not really sure what is causing your problems as I never faced these issues. My suggestion is the following.
1. Reboot to recovery
2. Format system
3. Wipe data&factory reset
4. Install Rom
5. Reboot
6. Reboot again
I take it, that you did not change the Rom package?
Wunder_luftmjuk said:
* A big button keyboard? Stock was good with big buttons for my sausage fingers.
* Ability to easily add foreign language keyboards (not system language) and dictionaries.
Click to expand...
Click to collapse
I left it to the user to download and choose a keyboard on their own. There are plenty in the playstore
* Remove delete thread confirmation in messages.
Click to expand...
Click to collapse
Hm, not really something I would personally enjoy, but maybe
* Remove confirmation when enabling storage by USB connection.
Click to expand...
Click to collapse
Trust me, I tried that one, but couldn't get it to work. I even tried copying the function of the xposed module..
* Ability to easily add sounds without trying to find the setting for each event. Still haven't found out how to change the alarm sound...
Click to expand...
Click to collapse
This is fairly easy, just drop the sounds into /system/media/audio/alarms
Our create a folder structure like media/sounds/alarms on your sdcard.
I hope that helps.

Sorted
Wooaarr said:
I'm not really sure what is causing your problems as I never faced these issues. My suggestion is the following.
1. Reboot to recovery
2. Format system
3. Wipe data&factory reset
4. Install Rom
5. Reboot
6. Reboot again
I take it, that you did not change the Rom package?
I left it to the user to download and choose a keyboard on their own. There are plenty in the playstore
Hm, not really something I would personally enjoy, but maybe
Trust me, I tried that one, but couldn't get it to work. I even tried copying the function of the xposed module..
This is fairly easy, just drop the sounds into /system/media/audio/alarms
Our create a folder structure like media/sounds/alarms on your sdcard.
I hope that helps.
Click to expand...
Click to collapse
Thank you for the help!
The "Delay and timeout" setting kept getting FC, until I went into security setting and disabled all security (pattern, pin, e.t.c.).
After that there was no more FC, and I could change the settings in "Delay and timeout". This also fixed the other "bug" which was power button not locking screen. Subsequently I could again change back security settings to pattern.
The other things I can live with! :laugh:
B.t.w. do you know any kernel that supports adaptive undervolting/overvolting combined with underclocking/overclocking? Also, is there any better governor than "ondemand"?
Suggestions for task killers? Many recommend Greenify but it won't run on android 2.3.x.
My aim is to have maximum battery life when on standby, while still having good performance in times of need.
Thanks again!

Wunder_luftmjuk said:
Thank you for the help!
The "Delay and timeout" setting kept getting FC, until I went into security setting and disabled all security (pattern, pin, e.t.c.).
After that there was no more FC, and I could change the settings in "Delay and timeout". This also fixed the other "bug" which was power button not locking screen. Subsequently I could again change back security settings to pattern.
Click to expand...
Click to collapse
I will dig out my old mini and see if I can reproduce that bug. I never used any security pattern, so that might be the reason I never had any trouble.
B.t.w. do you know any kernel that supports adaptive undervolting/overvolting combined with underclocking/overclocking? Also, is there any better governor than "ondemand"?
Suggestions for task killers? Many recommend Greenify but it won't run on android 2.3.x.
Click to expand...
Click to collapse
I don't think that there is a kernel that supports custom uv for the galaxy mini. However I found that the ondemand governor works very well. I could never really complain leaving it on 600 mhz. I have to admit though that it is an old phone, so don't expect any wonders .
My battery backup was always a minimum of 2 days, but I don't do any gaming. I used my phone as a phone... ( And a bit of music and internet).
Taskkillers are generally a bad idea, as they will just cause a cat and mouse game between them and a dodgy app. I'm not sure if the xposed module (I think the name is something with service disable) was backported to gingerbread. Anyway I never used it and if you want to try something maybe go for "auto start disabler free" from the playstore. That is what I used.
I hope this helps to enjoy your mini a bit more

New bug
OK I guess I have to play around with settings and apps to see how battery life can be extended.
B.t.w. I found a new bug: Camera shutter sound can't be disabled. Even when turned off in CM settings the camera will still play the click.

This is the best rom i have been used
its light, fast, and very stable.
thats what i want

I have 2 questions,,is this rom for galaxy mini gt-s5570..and can i flash over jellybean rom with full wipes,or do i have to revert to stock first?

blueangel4ever said:
I have 2 questions,,is this rom for galaxy mini gt-s5570..and can i flash over jellybean rom with full wipes,or do i have to revert to stock first?
Click to expand...
Click to collapse
you can just wipe and then flash this rom..
i'm from jelly bean rom too, and i'd do that

Damn man! Your ROM is completely stable, really like it a lot .. I personally recommended this theme http://forum.xda-developers.com/showthread.php?t=1499191 to you guys cause it is looks PERFECT to combine with the HOLO Launcher by Mobint, if you guys confront with lagging issue, just use this setting (Setting > CyanogenMod setting > Performance > CPU Setting & select Governors choose to PERFORMANCE and set MAX CPU Frequency to 806 MHz & reboot

ICS Theme that I found
This theme i found on xda is a great companion with this rom and HOLO Launcher

Bootsplash
Can I flash a "bootsplash.zip" in this ROM?

Make a backup first and then try...
Next time try to ask in a nice way and I might test it for you...

Wooaar? Its seems I can't flash the "bootanimation.zip" [installation aborted]
S5 bootanimation that I dig from xda website
you should reconsidered to place back the GINGERBREAD "Zombie ART" picture as it will brings an original ROM feels ... and sorry for asking that way the other day, it was a joke, sorry dude .. btw you did really a good job

Since when is a boot animation flashable anyway? You should just put it into system/media.
But I also deleted the script that executes the boot animation from /bin, so you would have to replace that as well.
I will not put the zombie art back in, as it is of no use, but just steals space.

Already tried to put it at system/media, but didn't works .. tell me about the script please? how to replace it
and take a look at this dude http://forum.xda-developers.com/showthread.php?t=2708316

This is indeed a flashable zip. Two things come to my mind.
1. Your recovery simply doesn't like the zip. Which version are you using?
2. Your zip is broken. Maybe the download did not finish?
In either way you have to replace the bootanimation binary in /bin. You can grab it from any rom, replace it and give it the proper permissions. Our you wait till I come back home and upload it for you.

I use yagya CWM 5.0.2.8 Touch recovery and indeed I finished the download 100% using IDM .. really hope you can help me .. thanks btw

Ok, as I have no power for today and my laptop is empty I quickly patched something up in my phone. I'm not sure if that is going to work...
Give it a shot and let me know.
Flash via recovery.

Wooaarr said:
Ok, as I have no power for today and my laptop is empty I quickly patched something up in my phone. I'm not sure if that is going to work...
Give it a shot and let me know.
Flash via recovery.
Click to expand...
Click to collapse
Installation complete but still blank screen & about the binary you ask me to grab it on another rom, you mean any rom?? including other phone rom?? as I do not download any custom rom for Galaxy Mini other than yours & my internet is not as fast as light tho, could you upload the binary script?? then replace it using root explorer right? then what is the proper permission to put on that binary script later?

Changed DPI and now phone stuck

Folks
I'm rooted and running Shamu 3.97. I used ADB to wrongly change my DPI. I ran the command
adb shell wm density 560480 (was using up arrows and by mistake didn't clear out the 560 before inputting 480)
Immediately, the phone rebooted and is stuck at the boot - little circles going around but doesn't move beyond that. Is there a battery pull that can be done on this device and what's my resolution? Do I have to somehow get into recovery and change the DPI to native 493?
Thx

You dont change DPi in bootloader or recovery, you need to edit it in build.prop or you can download dpi changer from play store

I got access to recovery but cannot boot the phone up since it just gets stuck on the rotating color circles. Any way to edit build.prop from recovery? I can see my Internal storage on my computer but can't find the build.prop file anywhere

did u do a backup on ur phone before dpi change? it could be u changed to the wrong dpi. Worst case scenario is flash back stock rom ...

sam008 said:
I got access to recovery but cannot boot the phone up since it just gets stuck on the rotating color circles. Any way to edit build.prop from recovery? I can see my Internal storage on my computer but can't find the build.prop file anywhere
Click to expand...
Click to collapse
Just re-flash the rom
Sent from my Nexus 6 using XDA Free mobile app

Weird display bugs but only in a few apps. Probably DPI-related (rooted stock)

Dear helpful XDA-devs,
I ran into some weird display bugs which I did not experienced before. I've had the N5 and other phones and did often change my dpi without any side effect. However when I did it with my new Nexus 6 now I discovered some icons in the Play Store and "Locus Maps", for example, being oversized (see attachments).
What I did was to try to change my DPI using "Texdroider DPI" which let to an instant bootloop. So I reflashed /system from the stock image. Then I used the Nexus Root Toolkit to change the dpi via adb, what I thought worked perfectly back then (I changed it from default 560 to 530 in the end but tried a few other values as well). However, now I discovered these weird display issues in these two and one or two other apps. Any ideas what might be the reason, if it is DPI related at all, or if it worked fine when you did it yourself? Changing it back to default now does not solve the issue for me now, of course.
I'm on MOB30I, by the way. And I use TWRP+SuperSU on it. I did allow TWRP to make the /system partition writable to prevent Android from replacing TWRP. Might that be a reason why the adb-DPI-change let to bugs? Thanks for the help! :good:

To prevent people messing with the dpi many apps and Google are hard coding the sizes into the apks. I would just leave the dpi stock

zelendel said:
To prevent people messing with the dpi many apps and Google are hard coding the sizes into the apks. I would just leave the dpi stock
Click to expand...
Click to collapse
Thanks for your input. I just decides to reflash /system again (overwriting it via fastboot). But the problem persists!? How is this possible? Reflashing /system should reset DPI changes, right? Man, do I really have to reinstall all of Android? .. :crying:

karlo12 said:
Thanks for your input. I just decides to reflash /system again (overwriting it via fastboot). But the problem persists!? How is this possible? Reflashing /system should reset DPI changes, right? Man, do I really have to reinstall all of Android? .. :crying:
Click to expand...
Click to collapse
No not completely. That maybe your best bet. Also could try deleting the cache files.

You need to also change the dpi in build.prop, or you'll get those large icons.
Or if you want to go back to the old dpi, just do what you did in NRT, but change it to 560 this time.

change it in your build.prop file, then reboot for it to take affect. anyways, you will probably see other bugs with the dpi changed properly(but maybe not).