Related
This question is directed to anyone who knows the inner workings of the vending.apk and the android market itself. Through another post about density settings, it seems pretty apparent that, while having density set at 161 allows all the apps in the market to show up, there are still plenty of apps that won't actually RUN unless you are set at 160/159. So it turns into a Catch 22 situation. I know I have used device spoofing via an altered build.prop (or an apk that does the same) for getting apps to appear that are 'proprietary' to other, specific devices, but I'm wondering if it MIGHT be possible to spoof the market into reading our Nooks at being 161 devices, while we are actually at 160 while within our rom (I'm on CM7). This has probably been proposed somewhere else, but I couldn't locate a thread...Anyone have any input about this possibility? If something like this is NOT possible, please let the users know also, if you have a minute. Thanks for looking...(Idea..could we get a secondary "market161" .apk created that we could use indepedently of the one in the latest Gapps to achieve the desired effect?)
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
My Density is set at 200 and everything works just fine (including both Market and Maps).
Mine is set at 240 (need new glasses?) and everything seems to be ok
Trust me...there are enough that don't run at 200....otherwise I wouldn't have bothered posting. 160 seems to be magic for compatibility/scaling, and 160+X gets best market access.
Sent from my PC36100
ganovim said:
Mine is set at 240 (need new glasses?) and everything seems to be ok
Click to expand...
Click to collapse
I actually would assume the 240 would work.. since it's 1 of the 3 native android app densities that devs mass market through compatibility mode to ensure mucho marketshare (120,160,240)..but the icons and such at 240 are just too huge ...can't do it...reminds me of those physical phones with humongous buttons that people have in their house. When I see someone using a new tablet, like take the Galaxy, I can tell pretty much immediately whether they're running stock from the look of their homescreen...Huge, ghastly, labeled icons +(bloatware)=someone not using their device to the full potential, and that makes my inner nerd sad. Nope, even if I go blind I won't do 240....if only because "it just LOOKS stock. The same reason SPB mobile lasted about a week on my nook.
Sent from my PC36100
Sent from my PC36100
FrasierCrane said:
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
Click to expand...
Click to collapse
Thanks...this is exactly what kind of info I needed...new project...sigh..will give it a shot after work tonight...Thanks.
Sent from my PC36100
Sent from my PC36100
FrasierCrane said:
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
Click to expand...
Click to collapse
BTW..Is Tasker's U.I. still absolutely archaic? I love all the possibilities from the app.. but it's such a nightmare to use. Is there any other 1 out there that might be easier on the brain?
Sent from my PC36100
mazook98 said:
I actually would assume the 240 would work.. since it's 1 of the 3 native android app densities that devs mass market through compatibility mode to ensure mucho marketshare (120,160,240)..but the icons and such at 240 are just too huge ...can't do it...reminds me of those physical phones with humongous buttons that people have in their house. When I see someone using a new tablet, like take the Galaxy, I can tell pretty much immediately whether they're running stock from the look of their homescreen...Huge, ghastly, labeled icons +(bloatware)=someone not using their device to the full potential, and that makes my inner nerd sad. Nope, even if I go blind I won't do 240....if only because "it just LOOKS stock. The same reason SPB mobile lasted about a week on my nook.
Sent from my PC36100
Click to expand...
Click to collapse
You're really making me want to track you down so I can change your density settings just to mess with you
Sent from my SAMSUNG-SGH-I897 using Tapatalk
wretchedlocket said:
You're really making me want to track you down so I can change your density settings just to mess with you
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
It would be SO on....
Sent from my Nook Color (zoom2) using Tapatalk
mazook98 said:
BTW..Is Tasker's U.I. still absolutely archaic? I love all the possibilities from the app.. but it's such a nightmare to use. Is there any other 1 out there that might be easier on the brain?
Sent from my PC36100
Click to expand...
Click to collapse
It's a pain sometimes, since everything is buried under submenus. I don't think there's anything else comparable, though.
The reason I have the density set at 161 isn't because apps are filtered. It was due to a bug in the Market apk and the Maps apk. Maps 5.1.x would crash on startup on tablets with LCD density 160. Google has fixed this with the most recent version. Unfortunately, Google has not fixed the Market yet. Tablets+160 causes the "my apps" list to not populate.
dalingrin said:
The reason I have the density set at 161 isn't because apps are filtered. It was due to a bug in the Market apk and the Maps apk. Maps 5.1.x would crash on startup on tablets with LCD density 160. Google has fixed this with the most recent version. Unfortunately, Google has not fixed the Market yet. Tablets+160 causes the "my apps" list to not populate.
Click to expand...
Click to collapse
Thanks so much for saving me from making this a bigger issue than it is...I don't need " my apps " to populate since I'm tethered to my Evo about 95% of the time, where they naturally all populate ...I'll just bump it down to 160 permanently, and if ever it becomes something I absolutely need, Ill just bump it back....Thanks for all your amazing work..Donation on the way when I get home from work.
Sent from my PC36100
Maybe im the only one, but whats the visual difference between 160 and 161? why is 160 better?
john10101 said:
Maybe im the only one, but whats the visual difference between 160 and 161? why is 160 better?
Click to expand...
Click to collapse
There are just some apps that wont run / scale correctly unless its at 160... they will just hang and load 4 ever or force close unless they are set at 1 of the 3 native densities for android application development... at least that's what I can glean.. no difference though in appearance, unless you're a cyborg.
Sent from my PC36100
oh this is why my app list wouldnt populate. it doesnt bother me most of the time. everyone seems to have their dpi set for so low. i have mine at 132.33 if i remember it right. can't be any bigger than 140 for sure.
can anyone give me an example of an app that crashes or does not show up on the market due to density conflicts?
the reason i ask is because i run hyperdroid on my HD2 at the default 167. this setting is just plain awesome compared to the 240. i have never had an issue with apps not showing up or crashes / anything due to resolution at this size.
or is this one of the default dev res' and i'm just talking nonsense.
let me know so i can test on my hd2.
pxldtz said:
can anyone give me an example of an app that crashes or does not show up on the market due to density conflicts?
the reason i ask is because i run hyperdroid on my HD2 at the default 167. this setting is just plain awesome compared to the 240. i have never had an issue with apps not showing up or crashes / anything due to resolution at this size.
or is this one of the default dev res' and i'm just talking nonsense.
let me know so i can test on my hd2.
Click to expand...
Click to collapse
Here's one...Try "Fruit Slice" at 161....then try it at others if you want...then run it at 160.
Sent from my PC36100
1) The haptic feedback on pressing the Home button feels ever so slightly delayed compared to how it was original in GB and the other GB ROMs. Could be in my head. Anyone else experiencing this and if so, know how to fix it?
2) Apex launcher that is included in the ROM seems cool but to put widgets on the home screen it says I need to install it as a system app or have root or something. I have root of course - how do I get it as a system app?
3) When I try to install the Chrome beta browser it's giving me "Error - Error processing purchase" dialog. Any ideas on how to fix this? When google searching this problem it seems like it might be on Google's end and I should just wait it out.
4) People in the dev forum are talking about some multi-dpi fix. I didn't run that since I have no clue what that is or what they're talking about.
5) Also people are saying that the VM heap is wrong or something on this build. I have no idea what that is or how it will effect me.
Okay I think that is all for now. Thanks!
Fappa said:
1) The haptic feedback on pressing the Home button feels ever so slightly delayed compared to how it was original in GB and the other GB ROMs. Could be in my head. Anyone else experiencing this and if so, know how to fix it?
Click to expand...
Click to collapse
Might be a little delayed, it's a leaked release, so anything is possible. I haven't noticed it. Don't think you're going to fix it.
Fappa said:
2) Apex launcher that is included in the ROM seems cool but to put widgets on the home screen it says I need to install it as a system app or have root or something. I have root of course - how do I get it as a system app?
Click to expand...
Click to collapse
You move the apk to system/app using Root Explorer or another file manager that has access to the root directory.
Fappa said:
3) When I try to install the Chrome beta browser it's giving me "Error - Error processing purchase" dialog. Any ideas on how to fix this? When google searching this problem it seems like it might be on Google's end and I should just wait it out.
Click to expand...
Click to collapse
Sorry, installation was fine for me. Have you tried installing from the website and pushing to your phone instead of directly on your phone.
Fappa said:
4) People in the dev forum are talking about some multi-dpi fix. I didn't run that since I have no clue what that is or what they're talking about.
Click to expand...
Click to collapse
Multi-DPI fix are for people who are running their phones with a DPI (Dots Per Inch) that is different from the stock 320 DPI. A lot of people use an LCD Density of 240 which causes some poorly (read Samsung TouchWiz apps) written apps to scale badly on screen, like the dialer. If you aren't changing your DPI then you don't have to worry about the fix. They won't hurt anything, but they're not needed for you.
Fappa said:
5) Also people are saying that the VM heap is wrong or something on this build. I have no idea what that is or how it will effect me.
Click to expand...
Click to collapse
I'm the wrong person to give details on how the VM Heap works, but the stock ICS leak uses 256 and people have claimed performance improvements by reducing the VM Heap to 128 or 64. I've got it at 128 and it seems to have improved performance, but I cannot say for sure.
You can change LCD Density and VM Heap with apps like ROM Toolbox. You can also move Apex to system/app with ROM Toolbox. It's a rather useful app.
Fappa said:
Okay I think that is all for now. Thanks!
Click to expand...
Click to collapse
Hope this helps.
Fappa said:
2) Apex launcher that is included in the ROM seems cool but to put widgets on the home screen it says I need to install it as a system app or have root or something. I have root of course - how do I get it as a system app?
Click to expand...
Click to collapse
If you have titanium backup you go to backup/restore tab and locate Apex launcher. Long press on it and at the bottom you will see "convert to system app".
Sent from my SAMSUNG-SGH-I717 using xda premium
Coffinfeeder said:
If you have titanium backup you go to backup/restore tab and locate Apex launcher. Long press on it and at the bottom you will see "convert to system app".
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Sheesh, if you want to do things the easy way...
lactardjosh said:
Sheesh, if you want to do things the easy way...
Click to expand...
Click to collapse
Haha
Sent from my SAMSUNG-SGH-I717 using xda premium
This is my first post here.
I recently switched from iPhone to Note 2. I was very drawn towards a large screen with lots of real estate. The note 2 out of the box didn't do it for me. However, I read the discussions about the international version and people changing the DPI with ROMs and other methods and figured if they could do it, so could I.
After waiting 5 weeks for my pre-order to arrive, then a week for the developers to provide a root option, I finally have my wish. Here is how I did it.
1. Root
2. Install a custom launcher (I installed nova, which works for me.) Set it as default
3. Install a new keyboard and set it as default
4. Install LCD Resolution from play store. I found nowhere that discussed this option, but I tested on a GS3, GS1, and Droid Charge and it worked better than the other DPI changers.
5. Set PPI to 240 in LCD Resolution. Uncheck Always Set on Boot until you know it will be stable. This caught me in a boot loop on the GS3. The only other res I tried was 160 and it failed.
6. Reboot.
It should work great. There are a few things to note:
1. The camera looks bad. I have not replaced it with a new one yet. - Please post any suggestions.
2. The calculator and dialer dont look amazing but are usable.
3. Email in portrait doesn't use the whole screen. I use it in landscape and it great.
4. Clock does not work, but can be replaced easily. I have not found a new alarm to use yet. - Please post any suggestions.
If you get another DPI to work well, let us know.
Otherwise, this is a great mod if you need more real estate on your new screen without loosing any of the s-pen or other stock functionality.
Thanks to those of you who helped root...
hmm, doesn't seem to work for me. The prompt in the app to reboot doesn't do anything.
Can we see some screen caps?
just do it manually it doesnt cause boot loops. You can change it to any DPI you want.
Use root explorer
navigate to "System/Build props"
Hold down "build props"
choose "open with"
then choose "text editor"
scroll down a few lines look for "ro.sf.lcd_density=320"
Change the 320 to whatever you want, I use 240.
click "save and exit",
reboot your device,
profit.
Why would you want to change it if it makes stuff look bad?
you can also edit the build.prop via rom toolbox really easily and the results are attached. 240dpi is first 320dpi is second.
Your Samsung keyboard will also crash at 240dpi but you can replace it with this one made by bala_gamer http://forum.xda-developers.com/attachment.php?attachmentid=1501015&d=1353535434
blackbass595 said:
Why would you want to change it if it makes stuff look bad?
Click to expand...
Click to collapse
I haven't done it yet but a lower dpi would be great on this phone. It would let you take more advantage of such a large screen real estate.
guthrien said:
I haven't done it yet but a lower dpi would be great on this phone. It would let you take more advantage of such a large screen real estate.
Click to expand...
Click to collapse
maybe but i just dont wont to change something that breaks other things. to each his own though.
blackbass595 said:
maybe but i just dont wont to change something that breaks other things. to each his own though.
Click to expand...
Click to collapse
It doesn't really break anything from what I've noticed, just makes a few things appear a bit differently, but still fully functional. It's worth a shot if you're interested in doing it, and you can always change back if you find it unmanagable. Personally, a per app dpi would be ideal, because you don't always prefer every app to be at 240 dpi. But I really like it, especially with the on screen nav buttons, which even those make some apps SLIGHTLY off, but still plenty usable, and worth the small inconvenience. To each their own though.
Sent from my SCH-I605 using xda premium
sleevasteve said:
It doesn't really break anything from what I've noticed, just makes a few things appear a bit differently, but still fully functional. It's worth a shot if you're interested in doing it, and you can always change back if you find it unmanagable. Personally, a per app dpi would be ideal, because you don't always prefer every app to be at 240 dpi. But I really like it, especially with the on screen nav buttons, which even those make some apps SLIGHTLY off, but still plenty usable, and worth the small inconvenience. To each their own though.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Where did you get the nav keys?
Thanks.
Sent from my SCH-I605 using Tapatalk 2
leyvatron said:
Where did you get the nav keys?
Thanks.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=35037379
Sent from my SCH-I605 using xda premium
Mibuix0r said:
you can also edit the build.prop via rom toolbox really easily and the results are attached. 240dpi is first 320dpi is second.
Your Samsung keyboard will also crash at 240dpi but you can replace it with this one made by bala_gamer http://forum.xda-developers.com/attachment.php?attachmentid=1501015&d=1353535434
Click to expand...
Click to collapse
Is there anyway I can get the steps to you method I tried using the apps but it didn't work and now I got a white line at the top of the screen. Am flashing back to stock root to see if it will remove it. I also tried root explore but would lose the multi window edit option. Now am going for ROM tool box. Any pointers would be great.
dandel0074 said:
Is there anyway I can get the steps to you method I tried using the apps but it didn't work and now I got a white line at the top of the screen. Am flashing back to stock root to see if it will remove it. I also tried root explore but would lose the multi window edit option. Now am going for ROM tool box. Any pointers would be great.
Click to expand...
Click to collapse
The white line is probably the miui battery bar, see if its on in settings> custom settings> battery bar settings. As far as the dpi, just use a root explorer to go into system>Apps>build.prop, then long press build.prop and open in text editor and change the line with "screen/lcd density" and change the value to 240(or whatever you want). Hit menu and save/exit then reboot. You are correct that you lose the edit function in multi windows, but you can always change back to edit your apps, then switch back. The change only takes 10 seconds.
Sent from my SCH-I605 using xda premium
sleevasteve said:
http://forum.xda-developers.com/showthread.php?p=35037379
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Cant get it to work.
What am I doing wrong? Do I have to be 240 dpi?
Root explorer > edit prop > scroll to bottom and add > qemu.hw.mainkeys=0 > and save
Sent from my SCH-I605 using Tapatalk 2
leyvatron said:
Cant get it to work.
What am I doing wrong? Do I have to be 240 dpi?
Root explorer > edit prop > scroll to bottom and add > qemu.hw.mainkeys=0 > and save
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Now reboot. You don't have to be at any certain dpi.
Sent from my SCH-I605 using xda premium
Why you would want to is easy. Ever used a tablet and seen tablet mode on apps? Stock DPI prevents apps from entering tablet mode and that was one feature I was looking very forward to with such a big screen.
leyvatron said:
Cant get it to work.
What am I doing wrong? Do I have to be 240 dpi?
Root explorer > edit prop > scroll to bottom and add > qemu.hw.mainkeys=0 > and save
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I couldn't get that to work either. I think it ma be a touchwiz conflict.
Just experienced my 2nd screen/sleep of death today, and unfortunately I'm thinking it's from the dpi. Going to change and will report back if I discover otherwise. I'll also leave my nav bar on, just to eliminate that variable. Bummer...I really hope we can incorporate a per app dpi on this phone at some point, maybe paranoid android(as long as it's reasonably compatible with the s-pen).
I also noticed my "android system" under battery was going through the roof. It was going over the screen %, but now that I changed the dpi back, it's already back under.
Sent from my SCH-I605 using xda premium
I get a error in root explorer when trying to edit the dpi in the build.prop
It will not let me change the setting to 240...any ideas? yes im rooted, root permissions granted for root explorer...etc.
droidstyle said:
I get a error in root explorer when trying to edit the dpi in the build.prop
It will not let me change the setting to 240...any ideas? yes im rooted, root permissions granted for root explorer...etc.
Click to expand...
Click to collapse
Make sure to use text editor or something similar. I had to long press it and "open with" for it to let me edit anything.
Sent from my SCH-I605 using xda premium
Change Pixel Density for Galaxy Note 3 and Recommended DPI Settings for System Apps.
Requires Root!
Works on any Rom!
With the Note 3 Packing a 1920x1080 resolution, the first thing I did when I got the phone was work on taking advantage of the real estate the screen has to offer. Many of the Pixel density settings from the Note 2 work on the Note 3, but keep in mind the formula changed with the new screen size and resolution change. I'm just going to call it "Preferred DPI" as most will agree, its a comfortable viewing option.
The easiest way I have found is to change the overall layout from 480 to 320, then going in and tweaking some individual apps.
Overall most of the apps will function as normal, however some system apps will not look right, especially the Dialer and Camera/Gallery views.
Note 2:
Factory DPI: 320
Preferred DPI: 240
Note 3
Factory DPI: 480
Preferred DPI: 320
To change all apps and programs to be viewed in 320 mode is to modify the build.prop settings.
There are multiple ways to do this, but the easiest I have found is to download Rom Toolbox. The Lite version will allow you to easily edit the app. Support your devs, buy pro or donate and give credit to these app & rom creators.
Rom Toolbox Lite Rom Toolbox Pro
Step 1: Changing phone pixel density from 480 to 320
Open Rom Toolbox
Go to the Performance Tab
Select the build.prop Editor
Click the Magnifying Glass to search
Type in "Density"
Click on the ro.sf.lcd_density
Change the Property Value from 480 to 320
Click YES on reboot prompt
Step 2: Download and Install Xposed Framework and App Settings Module
Without rewriting guides that are already available, you can read the general guides here on how to install Xposed Framework.
Guide by Max from High on Android
Download Xposed Framework by Xda Developer rovo89
Download Xposed App Settings Module by rovo89 & Tunstwenty
You will need to install Xposed Framework, and the Xposed App Settings Module by clicking on the above threads. The threads are maintained and updated regularly. Xposed has the ability to update itself, and also provides updates to the modules, which is a great feature.
Once these are installed you can then begin to change apps back to 480 DPI if they don't look right.
Step 3:Recommended Apps to Revert to Stock Density
You can change any app you wish, but the ones that I recommend to keep at stock DPI mainly due to cropping issues are the dialer, contacts, camera, and gallery.
I am currently running Jellybombed Rom, so you may see some extra apps in screenshots, as well as blue text.
I also ran this on the stock rooted Samsung Rom, and the Rooted Deodexed rom before going to Jellybomb.
These are my personal preferences, and im sure I have more than I need selected, but I wanted to make sure all elements worked.
Camera for example has many sub apps such as editing and trimming.
Contacts has 4 tabs for Phone, Groups, Favorites, Contacts
Phone has 4 tabs for Keypad, Logs, Favorites, Contacts.
Bolded are the most essential, the non bolded are personal preference. Feel free to add your own.
com.arcsoft.picmovie
com.arcsoft.picturesbest.app
com.android.app.popupcalculator Calculator
com.sec.android.app.camera Camera
com.sec.factory.camera Camera
com.sec.android.app.collage Samsung Gallery
com.sec.phone - Phone
com.android.contacts - Contacts
com.android.providers.telephony
com.arcsoft.picaction.app
com.arcsoft.demo.piclear
com.sec.android.gallery3d Alternate Gallery
com.google.android.gallery3d Alternate Gallery
com.lidroid.sgs.secretcode
com.android.mms - Texting
com.android.phone - Phone Dialer
com.sec.sprextension.phoneinfo
com.sec.android.mimage.photoretouching
com.sec.android.filter
com.samsung.everglades.video - Samsung Video App
com.sec.yosemite.phone
com.lifevibes.trimapp
com.sec.android.app.storycam
com.sec.android.app.videoplayer - Samsung Default Video Player
com.android.vpndialogs
ma.wanam.xposed
com.google.android.youtube
I have not had any issues with the Android Market, and DPI settings yet, however there is a module called Play Store Fixes you can run within Xposed.
The launcher I use is ADW Launcher
The current Rom used in the screenshots is Jellybomb Domination
Support Josh Beach & kevinrocksman
This is so necessary for the note 3. Thanks for the post!!
Awesome job.
Any clue what app the pen input app is? The one you activate by clicking the pen square over inputs?
It looks like it follows the app's dpi, but wondering if that can be pegged at 480 for every app?
320 feels a tinge too small. Any idea what other settings could be used easily that aren't so small?
I just went in and changed a bunch to make it better. Thanks for the suggestion.
Do you know which is the lockscreen?
Any idea what program the sview case window is under?
Sent from my SM-N900P using xda app-developers app
Jbroad572 said:
Any idea what program the sview case window is under?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
It's not a particular program, from what I've read you would have to leave the system at 480 and individually change apps to 320 to keep the S View Window working properly :\
datajosh said:
It's not a particular program, from what I've read you would have to leave the system at 480 and individually change apps to 320 to keep the S View Window working properly :\
Click to expand...
Click to collapse
Im going back to stock deodexed this weekend to test out some things.
I had some issues with editing pictures ( mainly getting the redeye tool to work with pinch to zoom) so Im going to go back to "as close to stock" as possible to rule out any theme/app settings from Jellybombed.
Ill try to play with the factory apps a bit to get a better list.
Im one of those .. "as soon as i get a phone I root, change dpi, then freeze or remove every system app with "samsung" or "sprint" on it.. and this time around its knox to add to the list.
Then again thats what I done with hundreds of computers for the last 15 or so years, so the habit kind of carries on =)
Not a fan of bloatware =)
rawdikrik said:
320 feels a tinge too small. Any idea what other settings could be used easily that aren't so small?
Click to expand...
Click to collapse
I would love to see more screenshots. I had rooted and went to 240dpi on my original note, and love the way that looks. Still on the fence with rooting my note 3. Haven't read enough about knox, even though I know there are ways to root without tripping knox now. But I m itching to change my dpi
Thanks for the guide. I put mine at 370 dpi, which looks good for me, without being too tiny
Sent from my SM-N900P using Tapatalk
anyone tried changing DPI to "Android System" and "System UI"? I had this changed on my Note 2 (to 240) so that the settings and overall UI was smaller. I tried changing it on the Note 3 to different DPI to test out but it seem sto leave a small border right under the status bar. I tried 320, 350, 370, 400 .. I'm using Nova Launcher btw. (JellyBombed ROM)
onebelo said:
anyone tried changing DPI to "Android System" and "System UI"? I had this changed on my Note 2 (to 240) so that the settings and overall UI was smaller. I tried changing it on the Note 3 to different DPI to test out but it seem sto leave a small border right under the status bar. I tried 320, 350, 370, 400 .. I'm using Nova Launcher btw. (JellyBombed ROM)
Click to expand...
Click to collapse
Hmm surprised since your running Nova. . I thought only stock launcher did that. .
Speaking of which. . Anyone thinking about redoing the stock launcher to handle the better dpi?
Sent from my SM-N900P using Xparent Purple Tapatalk 2
cherylbaker said:
Hmm surprised since your running Nova. . I thought only stock launcher did that. .
Speaking of which. . Anyone thinking about redoing the stock launcher to handle the better dpi?
Sent from my SM-N900P using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
yea specially since it looked fine on the note2. Perhaps it's the higher res of the note3?
Does the lockscreen have a separate package? Or is it part of a larger package?
Im trying to change the phone dialer back to stock, but despite the changes it stays the same at 370. What am I doing wrong?
badnews640 said:
Im trying to change the phone dialer back to stock, but despite the changes it stays the same at 370. What am I doing wrong?
Click to expand...
Click to collapse
Try checking all 3 of these settings to 480
com.android.providers.telephony
com.sec.phone
com.android.phone
You can set them manually to 480 (stock)
If you set your overall DPI to something like 370 you need to make those apps bigger individually to 480
cherylbaker said:
Hmm surprised since your running Nova. . I thought only stock launcher did that. .
Speaking of which. . Anyone thinking about redoing the stock launcher to handle the better dpi?
Sent from my SM-N900P using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
I use a scaleable launcher ( ADW EX) for that reason.
In the past when I tried to modify the stock launcher or system UI, it would cause all kinds of force closes..
The primary reasons i believe is due to how Touchwiz integrates its widgets- like clock for example
Changing just systemUI or Launcher but not changing all the other components manually that are linked to it can trigger "Unfortunately System UI Has stopped Working" errors.
The keyboard is another one thats tied in, as well as the lockscreen.
I haven't gotten around to trying to do all of that, or learning how to yet.. which is why i made the guide with the already available apps.
By changing the overall system UI and using a different launcher, you can have the smaller slim status bar, without having everything else break, since all of the DPIs match. Then finding different processes to tweak with "App Settings" allows you to experiment safely without risking breaking everything.
One super annoying issue i had back when I did DPI tweaking on my Note 2 was if you didnt flash a replacement keyboard in recovery, you would have to setup android by continously tapping the error message all the way through phone setup until you could get to the settings screen to change the samsung keyboard to a different one. Samsung's keyboard dosen't like dpi changes on the note 2. But so far no issues personally with the note 3.
chaosrecords said:
Try checking all 3 of these settings to 480
com.android.providers.telephony
com.sec.phone
com.android.phone
You can set them manually to 480 (stock)
If you set your overall DPI to something like 370 you need to make those apps bigger individually to 480
Click to expand...
Click to collapse
Along with a hunch, I found another thread that stated to change contacts and contact storage as well as dialer storage. That fixed it.
http://forum.xda-developers.com/showthread.php?t=2440365
Quick question can u provide more detailed instructions to reverting those apps u listed back to stock dpi...I try to do it through xposed app settings but the corrections aren't taking
Sent from my SM-N900P using Tapatalk
---------- Post added at 08:14 PM ---------- Previous post was at 07:36 PM ----------
lunchboxVA said:
Quick question can u provide more detailed instructions to reverting those apps u listed back to stock dpi...I try to do it through xposed app settings but the corrections aren't taking
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Nvm phone dpi and contacts dpi both have to be changed at the same time
Sent from my SM-N900P using Tapatalk
Does anybody else have an issue when they change there dpi where whatsapp wallpaper changes to a standard white background?
Any way around it?
its annoying and i have been researching for days and cant seem to find anything to fix it.
Hi all,
I have found a way to change the dpi without root, just using adb and cmd and it worked like a charm...well, almost. There are a couple of UI glitches that appear when you reduce (or increase for that matter) the dpi.
Firstly, the icons on the home screen mess up, but that's not SUCH an issue as you can install another launcher or in my case, find an icon pack that doesn't show the mess up quite as much (my preferable choice because you see the icons set in different areas of the UI, such as the notifications shade and recents menu, settings, etc.)
Secondly, and the most annoying, is the crop function messes up in the weirdest way. Whether it be when changing wallpaper or trying to crop a picture in CamScanner, the image you choose appears zoomed in and there is no way to zoom out or even move the image around, only zoom in further.
Now, my question is, has anyone managed to find a suitable dpi that MIUI does not have a problem with, or are there some standard dpi's MIUI uses apart from 480? Or has anyone found a way around any of these issues (or any other issues they may have encountered when changing the dpi)? Last but not least, is there a custom version of MIUI out there, or a rom that has it's visuals (and camera app) but custom tailored to suit various dpi's and other modifications?
I really cannot live with the stock dpi of 480, it's like using a phone made for old people, waaaay too large EVERYTHING on a large screen, I want to see more on a large screen. But I also am not yet prepared to go off MIUI as I really like their UI, visually, and I know any other rom will lose a lot of camera quality amoungst some other things like battery life, etc.
Thanks guys in advance for any advice.
Use 400 DPI ..There is no issue ..I am using it from 1Month
Sent from my Redmi Note 3 using XDA-Developers mobile app
Anands3 said:
Use 400 DPI ..There is no issue ..I am using it from 1Month
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Which method?
Sent from my kenzo using XDA-Developers mobile app
Textdroider App from play store
Sent from my Redmi Note 3 using XDA-Developers mobile app
If the original one is 386 I think 400 is kinda useless... Or did you mean 300?
Original is 403dpi if I'm not mistaken. I set mine to 375 and it's absolutely perfect..
Default density is 480.
Code:
[email protected]:/ $ wm density
Physical density: 480
Zak108 said:
Hi all,
I have found a way to change the dpi without root, just using adb and cmd and it worked like a charm...well, almost. There are a couple of UI glitches that appear when you reduce (or increase for that matter) the dpi.
Firstly, the icons on the home screen mess up, but that's not SUCH an issue as you can install another launcher or in my case, find an icon pack that doesn't show the mess up quite as much (my preferable choice because you see the icons set in different areas of the UI, such as the notifications shade and recents menu, settings, etc.)
Secondly, and the most annoying, is the crop function messes up in the weirdest way. Whether it be when changing wallpaper or trying to crop a picture in CamScanner, the image you choose appears zoomed in and there is no way to zoom out or even move the image around, only zoom in further.
Now, my question is, has anyone managed to find a suitable dpi that MIUI does not have a problem with, or are there some standard dpi's MIUI uses apart from 480? Or has anyone found a way around any of these issues (or any other issues they may have encountered when changing the dpi)? Last but not least, is there a custom version of MIUI out there, or a rom that has it's visuals (and camera app) but custom tailored to suit various dpi's and other modifications?
I really cannot live with the stock dpi of 480, it's like using a phone made for old people, waaaay too large EVERYTHING on a large screen, I want to see more on a large screen. But I also am not yet prepared to go off MIUI as I really like their UI, visually, and I know any other rom will lose a lot of camera quality amoungst some other things like battery life, etc.
Thanks guys in advance for any advice.
Click to expand...
Click to collapse
Is it possible to change the density using terminal emulator directly on phone? Or do I need to have PC?
GarbeVR said:
If the original one is 386 I think 400 is kinda useless... Or did you mean 300?
Click to expand...
Click to collapse
No, the original is 480, which is too large...where did you get the number 386 from? perhaps it is another one of their phone's stock DPI, which means MIUI might not warp on this DPI value? Will check it out, but any information you have, please let me know
h4gH said:
Is it possible to change the density using terminal emulator directly on phone? Or do I need to have PC?
Click to expand...
Click to collapse
Not sure about that, I only tried it from the pc, sorry.
Zak108 said:
Not sure about that, I only tried it from the pc, sorry.
Click to expand...
Click to collapse
OK will try at home then.
Just to be sure - phone has to be in FASTBOOT mode to accept ADB commands from PC right?
used some of the suggested DPI's but...
so, thanks guys, used some of the suggested DPI values, 386 and 375, and mostly everything works fine....except still some small issues with the icons and the cropping. try and set a wallpaper for a whatsapp group for example, photo shows as zoomed in and cannot zoom out to choose a crop of the WHOLE image like I used to....have attached some screenshots of what happens to my icons....is this possibly because I am not rooted that the DPI value is not getting set in to the system correctly? Is anyone who is rooted facing the same issues or not?
might convince me to root, this is the first device i have managed to be happy without rooting lol
h4gH said:
OK will try at home then.
Just to be sure - phone has to be in FASTBOOT mode to accept ADB commands from PC right?
Click to expand...
Click to collapse
No, no need....as long as you have ADB drivers installed and you are launching the CMD from within the ADB folder, it will work. Oh and of course USB debugging enabled and the first time it tried to access the phone for ADB details, you will need to allow it to by hitting remember and ok on the phone
h4gH said:
Is it possible to change the density using terminal emulator directly on phone? Or do I need to have PC?
Click to expand...
Click to collapse
Yes. I do bellow commands with Terminal Emulador on Android. My Device is Kenzo with MIUI 8:
su
wm density 400
The value you change to your preferred
Enviado de meu Redmi Note 3 usando Tapatalk
Zak108 said:
so, thanks guys, used some of the suggested DPI values, 386 and 375, and mostly everything works fine....except still some small issues with the icons and the cropping. try and set a wallpaper for a whatsapp group for example, photo shows as zoomed in and cannot zoom out to choose a crop of the WHOLE image like I used to....have attached some screenshots of what happens to my icons....is this possibly because I am not rooted that the DPI value is not getting set in to the system correctly? Is anyone who is rooted facing the same issues or not?
might convince me to root, this is the first device i have managed to be happy without rooting lol
Click to expand...
Click to collapse
Which theme is this?
BlueJeans said:
Which theme is this?
Click to expand...
Click to collapse
Roger Rabbit...I think at the time of the screenshots I was using a different theme for the status bar, but can't remember as I am now using Eureka 8 Pro. Roger Rabbit is the base theme though, quite like the grey simplicity.
GarbeVR said:
If the original one is 386 I think 400 is kinda useless... Or did you mean 300?
Click to expand...
Click to collapse
The original isn't near 386. I went down to 380 and everything it far smaller than a 6 dpi difference. I'd say stock is closer to 430 - 450
Yes man, you was right the original DPI is 440, the app textdroiderDPI was showing me an incorrect value of 386 (maybe a little bug...).
Setting it on 440 with LeDpiChanger gave me a full stock MIUI size
Stock is 480DPI, changers give bad result...just root and change build.prop ro.sf.lcd_density=
Denis:) said:
Stock is 480DPI, changers give bad result...just root and change build.prop ro.sf.lcd_density=
Click to expand...
Click to collapse
Thank you sir, this works for me on MIUI 8.1.1.0 global stable, change my screen density to 420. Icons are perfect.