Develop Bugs

[Q] Good ROM for changing screen dpi

Ok, I decided... I will root my Note2, but I would not like to lose much time in trying all the ROMs and comparing...
What I need is just:
- possibility to change dpi (with LCD resolution for example or in another way): this is my main purpose
- a very fast, stable and battery saving ROM, better light without all the Samsung "social things"... I do not want to risk or wait for updates to solve one problem or another.
Could you please suggest me?
Thank you so much.

You can change dpi on any rom
But there are problems I.e depending what you change it too some features wont fit and look right
Camera
Keyboard
Email
Snote
There is one rom thats light and about 300mb large what has sysrem dpi changed to 280 with all bits looking right
Look in android development section and youll find it cant remember name
If you dont mind loosing spen features and touchwiz extras like quick glance pick up to call and things like that then I would defo recommend p.a rom had paranoid android on my note 1 and loved it
Sent from my GT-N7100 using xda premium

There is an overview over all roms for this phone over at forum(.)xda-developers(.)com/showthread.php?t=1926506
Well you could try the ParanoidAndroid roms (which are CM10's, so no original Sammy software), which allow for DPI changes and a Tablet/Hybrid Tablet mode. There's one in the Android developement section by Utacka who publishes the releases on a nightly basis, there's also one in the Original Android developement section by imilka, those are released on a different schedule.
There is a rom called Hypernote, which is not CM10, but developed from original Samsung software. It has the stock DPI changed to

but... anyway, you are saying that I am going to lose some features like the s-pen...
That is really a pity!
Regarding other things... do you think customized ROMs are better than the really reliable Samsung one?
I am confused... but I got used to my 240dpi on Note1, and everything here seems too big without reasons

[Q] Paranoid Android 2.99 Beta

I just went from BAMF to Paranoid Android 4.2 and for the life of me I can't figure out why so many people are talking up this ROM, could someone please explain it to me because I need to be missing something.
The only thing that looked interesting was the UI features which do not work correctly. The Opaque Statusbar and Taskbar do not work. Randomly they will go back to solid black then never goes back to Opaque. The Tablet UI seems awesome but the Taskbar buttons are way to small. So I figured I would change the DPI but it makes the Statusbar clock huge and the notifications area pop-up moves half-way off the screen rendering it unusable.
So after those features are taking away there really is no custom / developer settings on the ROM so it's pretty much pointless.

A lot of people like a tablet UI but don't like the smaller DPI or visa/versa et cetera.

Jubakuba said:
A lot of people like a tablet UI but don't like the smaller DPI or visa/versa et cetera.
Click to expand...
Click to collapse
The Tablet UI is awesome but very poorly implemented it seems.

Shuino said:
So after those features are taking away there really is no custom / developer settings on the ROM so it's pretty much pointless.
Click to expand...
Click to collapse
I came from AOKP milestone 1 to PA 2.99.5 and while I like the 4.2 I'm thinking it might be time to go back to AOKP. I thought the Phablet UI was interesting but when I tried it... it didn't work correctly. I do like the per-app customization but I'd rather customize other areas of the phone with my time. Add I miss my integrated weather on the lockscreen.

illegalsmile said:
I came from AOKP milestone 1 to PA 2.99.5 and while I like the 4.2 I'm thinking it might be time to go back to AOKP. I thought the Phablet UI was interesting but when I tried it... it didn't work correctly. I do like the per-app customization but I'd rather customize other areas of the phone with my time. Add I miss my integrated weather on the lockscreen.
Click to expand...
Click to collapse
You are pretty much in the same boat am I. I was just hoping something happened during my install of Paranoid and that's why it wasn't working or features were missing or something. I'm glad I'm not the only one who thinks this ROM is defiantly lacking.
I am staying hopeful though. Once they get this ROM out of beta maybe Tablet UI will be working, and they will include some basic customization.

I do not see any problems with PA 2.99.5 whatsoever.. It works perfectly fine..smooth, good battery life, no lags, everything works as it should.. Once again, it is a matter of preference.. You putting up this thread was a matter of preference.. But once again, it is advisable that you do not complain by making a new thread.. Just post in the PA thread.. Molesarecoming is always open to constructive criticism..Once again, the word is "constructive criticism" the diversity of ROMs in the Galaxy Nexus community is what makes many stick with the nexus. so before bashing other ROMs, please just remember you not liking it, doesnt mean it's the same for others. If you hate it so much twitter it or fb it or something. >.<

Leemur89 said:
I do not see any problems with PA 2.99.5 whatsoever.. It works perfectly fine..smooth, good battery life, no lags, everything works as it should.. Once again, it is a matter of preference.. You putting up this thread was a matter of preference.. But once again, it is advisable that you do not complain by making a new thread.. Just post in the PA thread.. Molesarecoming is always open to constructive criticism..Once again, the word is "constructive criticism" the diversity of ROMs in the Galaxy Nexus community is what makes many stick with the nexus. so before bashing other ROMs, please just remember you not liking it, doesnt mean it's the same for others. If you hate it so much twitter it or fb it or something. >.<
Click to expand...
Click to collapse
I'm not bashing anyone work at all, honestly I just wanted to know if I was missing something from the ROM since so many seem to use it. I have used it for 2 days now and none of the UI tweaks are functional, or do not work properly or are just way to small with no functional way to increase size. But the ROM is smooth and quick with insane boot speed.

Here is info on PA 2.99+ in a nutshell. First and foremost, you all downtalking tabletui need to realize that it does not actually exist in android 4.2, the paranoidandroid team found it deactivated by google in the code for 4.2 and they spent their time making it available again, it is in no way a finished product, if you want to see it work good then download a version of PA with an android 4.1x base ( i.e. PA 2.54 or before). Now onto people that cannot see the big deal, well anyone that tried the pre 4.2 PA knows that there is more customization available in PA than any other rom put together. Now PA 2.99+ are all AOSP based instead of CM based so they basically are building this rom from scratch to improve speed, performance and battery life for everyone, this means that a lot is not even integrated back into the rom yet. Simply trying out the newest PA will not give you a feel for why it is hands down the best rom out there. As for transparency, that only works on the homescreen and in order to properly utilize it you must A. be using a compatible launcher which has the homescreen backgrounds drawn correctly ( i.e. Apex, Stock or Holo etc, NOVA does not work) B. Choose a correct transparent hexcode or slide the transparency bar to where you would like it for that said Launcher in the "apps" section of paranoid preferences. I am on 2.99 Beta 5 and have full transparency with no issues that you speak of (Photo included as proof), in fact, Beta 5 has added almost everything I want back into the rom and fully functional, I can hardly wait for v3.0, seriously, I cannot see ever using another rom after using paranoidandroid, it just has the edge on everything else out there. AOKP and CM have nothing on it especially when it's at 100% again, which will be in the next couple weeks at the rate it's awesome devs work at!

tabUI is not existant in 4.2, what you see right now is raw honeycomb. if you want to see how good it was install 2.54, thats still based on 4.1. but right now i got to make my hands dirty with this. i know that on xda most people do not understand the difference between developing and kanging, and they wonder "why's this rom slower than others" but someones gotta do the dirty work and im okay if crackflashers avoid ours. they avoid cm for the same reason.
as for hybrid engine, i dont think you have understood it yet. it works flawless and it gives you more customization than all roms on xda combined, IF you can handle it. yes, you are able to make a button pink in this and that rom, but hybrid can transform thousands of apps and components to the better, with practical implications that are unheard of. the apps that are running on your huge 720p screen were not optimized for it, they're in the same layout that applies to pocketwatches or stone age miniature phones like the htc wildfire.
as for opacity, no app, obviously, draws underneath the bars - why would it. the launcher can do it, but again - not all do. nova has even a bug that offsets the wallpapers which leaves a black gap. our launcher works, apex works, holo works and perhaps a bunch of others. no rom does it differently, simply because its impossible.
the real difference is that we are producing features that push androids boundaries, we are sick of a homogen rom culture that hasnt really moved one inch for a couple of years now. all these roms are the same, do you realize that? kanging has produced one grey mass and nothing stands out. when we are done with our beta we will of course bring in all the essential features aswell, but new features have greater priority. and these blow everthing related to it clean out of the water.
compare build.prop hacks with hybrid engine, its like night and day. this is quite possibly the biggest rom scene improvement android has ever had.
compare rom scene color tweaks with per-app-color, its like night and day. normal roms are static, they give you one color and thats that. our colors shift from app to app.
compare extended desktop (which also came from us) with per-app-fullscreen
compare our recents with clearall implementations,
we had the most versatile toggles on android in 4.1 (right now we're implementing a new panel which will come in beta6)
etc.
but you got to understand that this stuff takes alot of time. i know i could just rename an open source rom, call myself "founder," post in 30 device forums and make craploads of money here on xda, but i chose not to and im happy i found a few guys that think in the same way. im content with the few people that use PA and the support i get from those, i dont see myself competing with any other rom for that matter. i dont feel like i have to stop all my work now just because this and that rom has a minor option that we dont have at the moment.

molesarecoming said:
tabUI is not existant in 4.2, what you see right now is raw honeycomb. if you want to see how good it was install 2.54, thats still based on 4.1. but right now i got to make my hands dirty with this. i know that on xda most people do not understand the difference between developing and kanging, and they wonder "why's this rom slower than others" but someones gotta do the dirty work and im okay if crackflashers avoid ours. they avoid cm for the same reason.
as for hybrid engine, i dont think you have understood it yet. it works flawless and it gives you more customization than all roms on xda combined, IF you can handle it. yes, you are able to make a button pink in this and that rom, but hybrid can transform thousands of apps and components to the better, with practical implications that are unheard of. the apps that are running on your huge 720p screen were not optimized for it, they're in the same layout that applies to pocketwatches or stone age miniature phones like the htc wildfire.
as for opacity, no app, obviously, draws underneath the bars - why would it. the launcher can do it, but again - not all do. nova has even a bug that offsets the wallpapers which leaves a black gap. our launcher works, apex works, holo works and perhaps a bunch of others. no rom does it differently, simply because its impossible.
the real difference is that we are producing features that push androids boundaries, we are sick of a homogen rom culture that hasnt really moved one inch for a couple of years now. all these roms are the same, do you realize that? kanging has produced one grey mass and nothing stands out. when we are done with our beta we will of course bring in all the essential features aswell, but new features have greater priority. and these blow everthing related to it clean out of the water.
compare build.prop hacks with hybrid engine, its like night and day. this is quite possibly the biggest rom scene improvement android has ever had.
compare rom scene color tweaks with per-app-color, its like night and day. normal roms are static, they give you one color and thats that. our colors shift from app to app.
compare extended desktop (which also came from us) with per-app-fullscreen
compare our recents with clearall implementations,
we had the most versatile toggles on android in 4.1 (right now we're implementing a new panel which will come in beta6)
etc.
but you got to understand that this stuff takes alot of time. i know i could just rename an open source rom, call myself "founder," post in 30 device forums and make craploads of money here on xda, but i chose not to and im happy i found a few guys that think in the same way. im content with the few people that use PA and the support i get from those, i dont see myself competing with any other rom for that matter. i dont feel like i have to stop all my work now just because this and that rom has a minor option that we dont have at the moment.
Click to expand...
Click to collapse
Wonderfully said.
Sent from my Galaxy Nexus

PA 2.54 on epic 4g touch
I just flashed to this rom yesterday and really like it so far. I am interested in flashing to the newest 2.99 version. Where I can get the correct download for my phone, and do I need to update my recovery and if so, where do I get the link for that?
Thanks

btvolta said:
I just flashed to this rom yesterday and really like it so far. I am interested in flashing to the newest 2.99 version. Where I can get the correct download for my phone, and do I need to update my recovery and if so, where do I get the link for that?
Thanks
Click to expand...
Click to collapse
I think the new 4.2 based PA roms might only be available for the Nexus series phones and tablets currently since the developers have started over building it from the ground up using AOSP source instead of CyanogenMod. I am not certain if the code is out there for other devs to build on their particular devices yet though.

[Q] How to set screen resolution (density?)

So, I have been using SlimBean 4.2.1 betas/RC's for a while, and like a lot about it, but have some minor issues that make me want to switch to a different team's 4.2.1 that doesn't have those issues until the actual release.
Problem is, I really love the amount of real estate you get with SlimBean. I loaded up LiquidSmooth but it appears that from the UI, one cannot adjust the display resolution (in SB, it is System Settings=> Ass => Interface => General => LCD density).
I am guessing this setting lives under the hood. Anyone?
TIA
Sconnie

SconnieRoadie said:
So, I have been using SlimBean 4.2.1 betas/RC's for a while, and like a lot about it, but have some minor issues that make me want to switch to a different team's 4.2.1 that doesn't have those issues until the actual release.
Problem is, I really love the amount of real estate you get with SlimBean. I loaded up LiquidSmooth but it appears that from the UI, one cannot adjust the display resolution (in SB, it is System Settings=> Ass => Interface => General => LCD density).
I am guessing this setting lives under the hood. Anyone?
TIA
Sconnie
Click to expand...
Click to collapse
Can be done using Rom Tool box> Build prop editor.. rf.so.lcd_density=320 being stock, some drop to 241ish. (wrong ones will cause black screen at reboot) Some apps may not work correctly either. But that's easy way to do it.. (or you can edit the build prop via Root explorer (just mount as R/W

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.

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.