Develop Bugs

[Q] Most ROMS wont boot after setting LCD Density to 180 or less!?!?

Ive so far tries 5 roms including all MIUI 2.3 roms here. I used Blade buddy and LCD Density apps from the Market. After changing the setting the phone goes in to a boot loop cycle. It used to work fine previously but not with the new roms. Whats wrong?? Cyonegen roms seem to work fine.

Ducalion said:
Ive so far tries 5 roms including all MIUI 2.3 roms here. I used Blade buddy and LCD Density apps from the Market. After changing the setting the phone goes in to a boot loop cycle. It used to work fine previously but not with the new roms. Whats wrong?? Cyonegen roms seem to work fine.
Click to expand...
Click to collapse
MIUI Rom only work with LCD Density = 240, don't change to any others value

Ducalion said:
Ive so far tries 5 roms including all MIUI 2.3 roms here. I used Blade buddy and LCD Density apps from the Market. After changing the setting the phone goes in to a boot loop cycle. It used to work fine previously but not with the new roms. Whats wrong?? Cyonegen roms seem to work fine.
Click to expand...
Click to collapse
MIUI refuses to work when you mess with the pixel density. It's always been like that. It shares many iOS qualities lol.
If you want to have an MIUI-like experience on your phone with smaller pixel density, I suggest you flash GBX, then slap on a theme. Then download and set GO SMS as your default SMS client. Oh and Youlu Address Book as your default Dialer and Contact List.

GoCkillaz said:
MIUI refuses to work when you mess with the pixel density. It's always been like that. It shares many iOS qualities lol.
If you want to have an MIUI-like experience on your phone with smaller pixel density, I suggest you flash GBX, then slap on a theme. Then download and set GO SMS as your default SMS client. Oh and Youlu Address Book as your default Dialer and Contact List.
Click to expand...
Click to collapse
I like GBX and Im now on Ultimate Droid (which runs fine at 200dpi!) and some other good roms here. But all of them have a bluetooth high drain bug. So Im checking out each rom as they come out to find one to stay with. Also I want to set the LCD density to 180. I have done this on many 2.2 MIUI roms. but not the new 2.3s....

Use 183 it works

Ducalion said:
I like GBX and Im now on Ultimate Droid (which runs fine at 200dpi!) and some other good roms here. But all of them have a bluetooth high drain bug. So Im checking out each rom as they come out to find one to stay with. Also I want to set the LCD density to 180. I have done this on many 2.2 MIUI roms. but not the new 2.3s....
Click to expand...
Click to collapse
flash a newer kernel and voila bt bugs are gone.

I use Typhoon with 167 and it works a treat!

Frameworks dpi's and kernals?

Im curently running jellybam 6.7 and i was wondering if anybody can give me as much info as possible on what exactly frameworks and dpi are and what exactly they do. Im also wondering about the kernals i kno there are other compatable kernals that could be flashed with jellybam but i honestly know nothing about them or wat it changrs. Im a noob to most of this and im just trying to make sure i completely avaoid bricking my phone. Any help or info would be much appreciated.
Sent from my SPH-L710 using xda app-developers app

Roni P. said:
Im curently running jellybam 6.7 and i was wondering if anybody can give me as much info as possible on what exactly frameworks and dpi are and what exactly they do. Im also wondering about the kernals i kno there are other compatable kernals that could be flashed with jellybam but i honestly know nothing about them or wat it changrs. Im a noob to most of this and im just trying to make sure i completely avaoid bricking my phone. Any help or info would be much appreciated.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I have more experience with messing with DPIs than I do with kernels, so I'll let someone else answer your question about kernels.
DPI normally stands for Dots per Inch. When it comes to printer, the higher the dpi the smaller the dots and, therefore, the higher "resolution" you get. For Android, though, DPI talks more about the pixel density (I think it's Density Pixel Index, I could be wrong, though). If you really want to get into Android uses this value in their code, the first comment in this post does a good job (IMO) of showing where it comes into play. After all that, the basic correlation is this: lowering the DPI will shrink your icons/apps/etc and effect the way certain apps appear on your phone. The stock GS3 setting for DPI is 320.
The reason people (like myself, running 241 dpi) choose lower DPIs is that certain apps (like calendar, Hulu, Netflix, etc.) have better interfaces on tablets than they do on phones, so we want to "force" them to think our GS3 is a tablet. The "official" way of doing this is by modifying the build.prop file. There's a semi-guide here that you can follow. The main problem with changing this value is that the Google Play Store looks at it to verify your phone. If the phone type does not match the the DPI value, you won't be able to download any apps! There are various fixes to this, but my preferred choice is just to download and install a modified Play Store which allows multi-DPI. Here is the thread for the one that I use (see post #2 for downloads).
Some ROMs also allow you to change the DPI "on the fly" without having to modify the build.prop. I'm currently running LiquidSmooth and in my Settings --> Interface --> LCD Density looks like this. It also has steps that you need to take to make your Play Store work. Having the multi-DPI play store that I linked previously will prevent you from havign to do the "clean up" work, but it doesn't hurt to follow the steps.
Now that you know a bit more about that, there are ways to get the advantage of a lower DPI on certain apps without havinn to mess with the build.prop or a Multi-DPI play store. ParanoidAndroid is a ROM that has "per-app DPI settings" built into it. Some other ROMs have the "Xposed DPI application," which serves a similar purpose. Per-app DPI systems like these two can "force" any app to see your device at a DPI that is not the current System DPI. For instance, I can have my system DPI as standard (320), but when I run Hulu, it sees my device as 241 DPI, so the layout will be similar to what I would see on my tablet (which I prefer for Hulu). This is nice because if you mess up a setting for an app, you can just revert the changes and clear the app cache and it'll be good to go again.
Hopefully this is a good primer to see the purpose of DPI and how it's used to customize your experience with your phone.

Let me talk about frameworks and kernels now...
A kernel is the powerhouse of an OS altogether. It is this layer that provides all interfacing with hardware that the OS can then use to implement things like network toggles and such
Everything is defined in the kernel...if something is not defined there, then you cannot use it
This is the reason why building newer roms (from source and not yet supported officially) is difficult because you gotta build the kernel from the ground up. You gotta implement things like Wifi, Power management (voltages, CPU, and proper shutdown and booting up sequences), 4G (if applicable), and 3G
So in summary, the kernel is what provides the software (in this case the Android OS) access to hardware components through this intermediate layer
Now the reason people flash other kernels is because some may manage power better (resulting in better battery life), may implement more features (have more CPU governors or IO schedulers), or provide some extra quality (could be something important like 4G or something as aesthetic as enabling boot animations)
Now frameworks. Each proprietary interface has its own frameworks. AOSP is normally not mentioned when discussing frameworks because it is the "vanilla" or "stock" interface provided by google straight from the original AOSP source that all other proprietary frameworks are built on top of
HTC has its own interface, so does Motorola, Samsung, and LG
HTC's interface is called Sense, Samsungs is called Touchwiz and LG's is called LG UI (very creative, i know ), and i believe, but I may be mistaken, that Motorals interface is called MotoBlur
And each of these proprietary interfaces is primarily defined in the frameworks-res.apk and SystemUI.apk. It is these additions (addition being used in reference to what Google provides) that give each interface its unique spin on things. This is what causes the weather to animate on an HTC phone as soon as you unlock it, what gives the apps a different icon and more features, what changes the icons for the different things in the status bar, what shows recent apps and quicksettings when you slide down the status bar. In touchwiz its the same thing, different icons and other proprietary features like multiview and a more unique keyboard
Basically, the "frameworks" that you keep hearing about is what defines a proprietary interface. It is because of these interfaces that you cannot install proprietary apps or enable proprietary features on AOSP. These things are dependent on the frameworks of their respective interfaces and since AOSP has a different frameworks, then you'll just get FCs and such.
Now I'm not saying its impossible to port proprietary features over to AOSP. It can be done. But its extremely difficult because first you need to track down where exactly these features are defined, and then condense them into either a standalone app, or a series of standalone apps that will behave the same way.

Thanks guys... So now where does the exposed settings come into play? Is it honestly worth messing with or is going to open a whole new world like rooting rooting my phone? Lol
Sent from my SPH-L710 using xda app-developers app

Roni P. said:
Thanks guys... So now where does the exposed settings come into play? Is it honestly worth messing with or is going to open a whole new world like rooting rooting my phone? Lol
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I touched upon this in my reply.
Now that you know a bit more about that, there are ways to get the advantage of a lower DPI on certain apps without havinn to mess with the build.prop or a Multi-DPI play store. ParanoidAndroid is a ROM that has "per-app DPI settings" built into it. Some other ROMs have the "Xposed DPI application," which serves a similar purpose. Per-app DPI systems like these two can "force" any app to see your device at a DPI that is not the current System DPI. For instance, I can have my system DPI as standard (320), but when I run Hulu, it sees my device as 241 DPI, so the layout will be similar to what I would see on my tablet (which I prefer for Hulu). This is nice because if you mess up a setting for an app, you can just revert the changes and clear the app cache and it'll be good to go again.
Click to expand...
Click to collapse
So basically, the Xposed DPI application allows you to control the DPI on a per-app basis. You can tell Hulu to use 241 dpi and Netflix to use 190 DPI (or whatever you want), even if you have your phone's "default" to be the standard 320 DPI.
In terms of functionality, it'll affect different apps in different ways. A lot of the time, apps won't change at all. Some will stop working, so you'll just have to revert the settings and clear cache and you'll be good to go. It's really up to you which apps you want to modify. A lot of people don't mess with this stuff for fear of breaking things, but Xposed shouldn't have "lasting" effects.
Back when I was using ParanoidAndroid, I had toyed with the idea with creating a Thread in the General forum about which apps look best with modified DPIs. I eventually gave up the idea (was a huge effort while I was creating screenshots of each app before and after), but it might be good to start one up now that XPosed is being included in a lot more ROMs. Meh, maybe once I have a bit of free time.

[Q] Unable to change DPI

Hi guys, here's my issue with my Nexus.
It started maybe last night when I updated to the newest stable release of SlimRom 4.4.4 Build 7
After I updated, all seemed fine, but the icons in the global menu, and in my notifications were suddenly enlarged and made out of whack.
I then tried changing my DPI to slightly higher to fix the issue, through Textroider DPI. Now, the app made my DPI way too high, even though I had set it for something like 230 (originally 220)
I tried reverting to my original DPI which was 220, and according to the app, it is currently at 220...even though it isn't. Even in the build.prop it says my DPI is 220, but on the screen there is zero change. re-flashing the rom worked once, but eventually it stopped working. Currently, my screen looks as if it's running a tablet DPI of 300 or so.
Long story short, I am unable to change my DPI, even though in my build.prop it says my DPI is 220.

Is it only happening with that specific ROM?
Send from GN running ParanoidAndroid2.57 Jellybean 4.1.2 w/Tablet Mode

isajoo said:
Is it only happening with that specific ROM?
Send from GN running ParanoidAndroid2.57 Jellybean 4.1.2 w/Tablet Mode
Click to expand...
Click to collapse
I've used SlimRom for heck knows how long since I got my GNex. I have not tried flashing any other ROM, only the previous version of the ROM (4.4.2 Build 5)
The keyboard appears to be completely normal as if it was in 220 dpi, but the the rest of the interface including all the apps believe that it's in a high DPI.
I'm downloading another ROM as we speak and then flashing it to see if it fixes anything.
I hope you can at least get some idea of the problem I'm describing, as I lack the power to post a screenshot

considering buying - 2 questions

Hello,
I've never bothered with Samsung phones (my gf uses out of the box), and apologies if these have been answered but I've not found them when searching
1) Is it possible to install stock AOSP on the phone? or something as far away as the laggy TouchWhiz I've experienced on her Galaxy phones (I've seen http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176 but can't watch at work - is it stock Android or stock Samsung firmware?)
2) if not, is it possible to set the DPI to be higher through adb (shell wm density) - I like high pixel density to stop people reading over my shoulder, fitting as much on the screen as possible, etc

nsitajes said:
Hello,
I've never bothered with Samsung phones (my gf uses out of the box), and apologies if these have been answered but I've not found them when searching
1) Is it possible to install stock AOSP on the phone? or something as far away as the laggy TouchWhiz I've experienced on her Galaxy phones (I've seen http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176 but can't watch at work - is it stock Android or stock Samsung firmware?)
2) if not, is it possible to set the DPI to be higher through adb (shell wm density) - I like high pixel density to stop people reading over my shoulder, fitting as much on the screen as possible, etc
Click to expand...
Click to collapse
Eventually we'll have TWRP and an AOSP ROM to flash but not right now. The link you point to will install the latest stock ROM (TouchWiz).
If you root this device you can change the DPI like you could with any other rooted device.

nsitajes said:
Hello,
I've never bothered with Samsung phones (my gf uses out of the box), and apologies if these have been answered but I've not found them when searching
1) Is it possible to install stock AOSP on the phone? or something as far away as the laggy TouchWhiz I've experienced on her Galaxy phones (I've seen http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176 but can't watch at work - is it stock Android or stock Samsung firmware?)
2) if not, is it possible to set the DPI to be higher through adb (shell wm density) - I like high pixel density to stop people reading over my shoulder, fitting as much on the screen as possible, etc
Click to expand...
Click to collapse
While I didn't notice much lag with the phones launcher out of the box (other than their magazine feed screen which I disabled) I installed Google Launcher on the phone and while not a true AOSP experience it improved some lag points I didn't really notice before, but noticed after I switched to it.

Changing resolution on V30B (D855)

Hi guys !
Here is the thing. I used to change the resolution of my G3 (D855 - 16GB) on stock to 1080P, and it was amazing.
Since Marshmallow, there's a few problem if you do that. Let me explain :
I managed to lower the resolution of the rom with ADB to 1080p, everything was right, but the DPI was too big, obviously ! So i lowered it to 540, the limit of LG apps, and everything was fine, but the problem is, it's still too big. It's one of the problems of the G3 that i can't stand. The DPI is too big, even in stock 1440P. I tried different things, to lower the DPI under 540, and here is the results :
1 ) Lower the DPI of the rom under 540 : Force close on LG Apps
2) Lower the DPI of the rom under 540 and use App Settings to put all the LG Apps at 540 DPI, it somehow worked but there was a lot of incompatibilites that were not in Lollipop. That was what i used to do on my Lollipop Rom.
3) Leave the DPI to 540 but change all the daily used apps to a DPI under 540 : It worked too, but the System UI was still too big.
4) Same as 3, but change the DPI of SystemUI under 540 : It worked too, but everytime i call was received, i couldn't answer because of force closes.
So here's my question. Can someone help me to figure how to lower the DPI of SystemUI and getting the phone to still work ? Or share with me another method to do it, ideas that i can try, etc, i'm open to suggestions !
Thanks !

Actually, I used to go through the same steps as you described, on Lollipop. I got everything to work, with 1080p and dpi around 440 I believe. My experience was, that App Settings would pretty much fix any misbehaving app after the dpi change, including the call/message apps. The only thing that continued being weird was the default LG home screen, which still had blank, broken icons and widgets so I had to replace it with Nova Launcher, which worked like a charm. This was about half a year ago, and when I done it on my phone, I repeated the same process on my friend's G3 (same ROM, same process).
My G3 would work fine for a while, but eventually, at some point during the 3rd or 4th system restart, it would always get bricked, stuck on the LG logo while booting. Always had to restore my backup., try again, but to no avail.
My friend's G3, on the other hand worked just fine ever since, which I can't quite wrap my head around, since it's the same phone, with the same ROM and the same procedure.
So I would also like to know if it's possible to create a stable 1080p system with MM now. As to your call problem, does it force close even though you applied the fix to it in App Settings?

I also replaced my launcher by Nova Launcher, on stock or modified, i prefer Nova Launcher, a lot more options to customize it.
I'm actually using a modified 1080P Marhsmallow Rom, but it's not stock, it is on AICP (based on CM13 MM i think), and it is working fine, but it's not stock. The camera is not as good as stock.
I dont know why your phone had this problem though, i never had this on mine.
I'll try again the same steps that i described, on the fulmics marhsmallow rom, that is eventually coming in a few days.
For the phone force close problem, i tried multiple things, and it didn't work with a custom DPI set with app settings on the phone APP. That's why i tried to put the whole system at 540 DPI and my personal apps at 400. And as described in my first post, it worked good, but systemUI was too big.
Maybe i can try differents xposed modules to customize the SystemUI to make it smaller without modidyfing the DPI of the whole app?...

Bump... Is really no one interested by downgrading the resolution of the G3?... You should at least try, it is good for gaming and fluidity.

Lymnoreia said:
Bump... Is really no one interested by downgrading the resolution of the G3?... You should at least try, it is good for gaming and fluidity.
Click to expand...
Click to collapse
If you put "Game optimizer" setting ON, then all games are run in 1080p.
You can find it under "Battery & power saving" option.
Therefore, there is no reason to downscale resolution on Marshmallow

Same here. Just flashed Fulmics 3.1.... Set my DPI to 540 but still find the UI too big unlike when I was on Ti-x lollipop. I browse facebook regularly and the chatheads are way too big for a 540 DPI, heck, it's even smaller when I was on lollipop with the same DPI. It's kinda annoying considering how big the G3's screen is... big UI just waste space. I'm loving the new marshmallow rom but this one is really a nuisance.