Develop Bugs

[Q] Change DPI on stock

I'm running stock 4.1.1, it's odexed and rooted.
I'm wanting to change my DPI to 200 maybe, but it seems I need a deodexed ROM to do that. I really can't be bothered reflashing and I don't have enough data to download a new rom anyway.
So is there any way to change it?

Check in my signature.
You can set any dpi with that guide.
Just you need to use a custom keyboard.
this is XXXDDDAAA

Your sig is actually what made me want to do it. The guide confused me though. What modules do I need to use and where from? And I have to download like 10 modified apps don't I?

If you want 240dpi then you have to download the modified keyboard and I recommend launcher as well.
If not 240dpi then you have to use a custom keyboard and again I recommend launcher as well. You have to disable the stock ones.
Now some apps don't work nice on a specific dpi. You have to use xposed app settings and make them run in 320dpi.
You have to download xposed framework and download the 3 modules listed in the guide.
this is XXXDDDAAA

[Q] Similar ROM to Slimbean (small size) but without its own Gapps?

So the thing I enjoy most about slimbean is the "night" setting and the smaller sizes.
Correct me if i'm wrong, but the part that determines the general sizes is the LCD density, and for slim its at 245.
Are there any ROMs that also use the same LCD density (if that is what's causing the small size)?
I'm mainly wondering because it uses its own Gapps package so that it could do this night mode where everything is black.
But I want to use the new gmail and other gapps that just came out more than I want night mode

You don't have to use the SlimBean GApps with the Slim ROMs, but have a look at CarbonROM (has Dark Carbon settings and you can change LCD density).
http://goo.im/devs/carbon

noother84 said:
You don't have to use the SlimBean GApps with the Slim ROMs, but have a look at CarbonROM (has Dark Carbon settings and you can change LCD density).
http://goo.im/devs/carbon
Click to expand...
Click to collapse
I use LiquidSmooth (what Carbon is based off of) and used to use their method to change the DPI. But recently, I've discovered the XPosed Per-App DPI settings included in the Rom. With it I can manually adjust the DPI of any program to make it whatever I want. The thing I like about this is that I don't have to mess with the Play Store (no more errors when trying to download apps). That, and some apps don't play well with a modified dpi on our phone.
I can go through and make google calendar 240 dpi and see how it functions, then change it to 190 an see how it works. I change Nova's setting to make the launcher look more like Slim Rom's (the Rom that made me fall in love with switching the DPI). It works really well and is worth a test drive, in my opinion.

topherk said:
I use LiquidSmooth (what Carbon is based off of) and used to use their method to change the DPI. But recently, I've discovered the XPosed Per-App DPI settings included in the Rom. With it I can manually adjust the DPI of any program to make it whatever I want. The thing I like about this is that I don't have to mess with the Play Store (no more errors when trying to download apps). That, and some apps don't play well with a modified dpi on our phone.
I can go through and make google calendar 240 dpi and see how it functions, then change it to 190 an see how it works. I change Nova's setting to make the launcher look more like Slim Rom's (the Rom that made me fall in love with switching the DPI). It works really well and is worth a test drive, in my opinion.
Click to expand...
Click to collapse
So I tried to install it, and I got this assert failed problem, which links to this solution. Did you flash the odex, deodex, or 3rd rom? I'm just confused, since I would have to install a gapps for the 4.1.2 JB. did you do any of that?
edit - my broadband is mc3

halodos said:
So I tried to install it, and I got this assert failed problem, which links to this solution. Did you flash the odex, deodex, or 3rd rom? I'm just confused, since I would have to install a gapps for the 4.1.2 JB. did you do any of that?
edit - my broadband is mc3
Click to expand...
Click to collapse
Not sure what you are doing but t he main post has all the info u need. Liquid smooth is 4.2.2. Gapps is in the main post as well.
http://forum.xda-developers.com/showthread.php?t=2148306
Sent from my blue galaxy

No, you need to read the guys post again. He says to update your bootloader to MD4 to fix it, not to flash one of the stock roms.

CNexus said:
No, you need to read the guys post again. He says to update your bootloader to MD4 to fix it, not to flash one of the stock roms.
Click to expand...
Click to collapse
miller710 said:
Not sure what you are doing but t he main post has all the info u need. Liquid smooth is 4.2.2. Gapps is in the main post as well.
http://forum.xda-developers.com/showthread.php?t=2148306
Sent from my blue galaxy
Click to expand...
Click to collapse
Ok, I found the Freeza stuff I should flash. Thanks again; my bad it took so long
http://forum.xda-developers.com/showpost.php?p=41640211&postcount=1937

Xperia S, 4.1.2, FW 6.2.b.1.96 : Changing the LCD DPI ?

Hello,
A great colleague of mine who also owns a xperia S like me
loaded SlimNasomi rom (I think 4.2.2) and did change lcd DPI.
Screen displays more info and icons are smaller. Look nice.
Is it a way to do it with official 6.2.b.1.96 rom ?
I found a thread on a forum about root'ing the phone and
updating a file build.prop in /system, updating ro.sf.lcd_density
I even found an app 'Google Play DPI Fix Tool'
Did anyone already try to play with LCD DPI's ?
Thanks. Cheers from Belgium,
Thierry

I use Texdroider DPI - it worked on stock JB, rooted.

switzerland92 said:
I use Texdroider DPI - it worked on stock JB, rooted.
Click to expand...
Click to collapse
Can I ask you how does it works?

cabi.costa said:
Can I ask you how does it works?
Click to expand...
Click to collapse
It changes build.prop to desired dpi. I use it because it's faster and it really works. I tried on stock ROM, OpenSEMC and letama's AOSP 4.3.

And what is the range of values to stay in to avoid an endless bootloop?

yes that's the question, What value did you use for. in .200 fw i used a lcd density changer soft (don't remember the name) and guess what i got endless loop. I used 244 or something like that.

I usually use 240 and I didn't have any problems with that dpi.
It is standard Android dpi so most apps work just fine. Stock ROM look good but it has some minor offsets (gradient in notification bar as far as I remember).

I have been talking about this in the themes section in an old thread. I keep seeing people have issues with the dpi apps. I personally just edit build prop manually as it is not hard. I use Anttek explorer for my file browsing and edits. I would also suggest you try Xposed framework and per app dpi module. The magic LCD number is 192 for tablet mode. If you set home to 160 it goes into tablet mode but the status bar will not combine at the bottom. There is also another xposed module that forces tablet mode and works well but is still buggy. You also loose small apps.
There is a way to force tablet mode with out the dpi change but I have to figure out how to do that and even then not sure it will actually work. Need to ask some smali experts to help me.

... and what about if in endless bootloop ? ... :crying:

You must make backup before any modifcations

Yea it is a great idea to have a backup when messing with the system. If something goes wrong you can just go back to where you started.

[Q]Minimal DPI for stock rom

hey does anyone know what is the minimal dpi for stock base roms before system apps FCs? I'm unable to test it myself right know. Thx

530 DPI is the lowest setting without some FC and LG app icon glitching.

[Q] [REQ][HOW TO?] How to theme a system app?

I just recently switched my stock rom to be deodexed and I'm now looking at the possibility of theming and mods for my rom.
I already have a little experience modding the signal icons on a different Android device, and I've already downloaded a mod from this forum that turns part of the stock dialer to a holo dark/material theme, but I want to do more with it.
So far I can't seem to find a good tutorial on how to properly mod system files, especially knowing that the stock rom on the Moto G is a Motorola variant of Android KitKat, and not AOSP or similar, although it's close enough that I figure some mods might work since many Xposed modules for AOSP work fine on my stock rom.
Would it be safe to look for a tutorial based on AOSP 4.4.4, or does anyone know a good place to learn the proper way to modify and theme a Motorola stock rom?

chuman72486 said:
I just recently switched my stock rom to be deodexed and I'm now looking at the possibility of theming and mods for my rom.
I already have a little experience modding the signal icons on a different Android device, and I've already downloaded a mod from this forum that turns part of the stock dialer to a holo dark/material theme, but I want to do more with it.
So far I can't seem to find a good tutorial on how to properly mod system files, especially knowing that the stock rom on the Moto G is a Motorola variant of Android KitKat, and not AOSP or similar, although it's close enough that I figure some mods might work since many Xposed modules for AOSP work fine on my stock rom.
Would it be safe to look for a tutorial based on AOSP 4.4.4, or does anyone know a good place to learn the proper way to modify and theme a Motorola stock rom?
Click to expand...
Click to collapse
get apktool
with this decompile your apks you want to theme/mod
hapy theming! (there plenty of tutorials of how to edit images or the .9 patch files. with gimp etc.. just search )
after that recompile, if you just have edited some images (ressources) pull them afterwards from the new COMPILED apk out in a folder.
take the original apk & open with 7zip & pull the edited stuff into the right directions.
if you have done some advanced modification such as in values folder, you need after the new apk is compiled, open it with 7zip & pull from the original app the meta-inf folder into the new compiled one (singing) after tthat replace it on that phone