I sucessfully installed jellybean but I can't seem to change the lcd density..
I have in my build.prop ro.sf.lcd_density=160 and nothing happens.. I still have it set to the original, 240.
I noticed theres a new options in jellybean's build.prop ro.sf.override_null_lcd_density=1, I commented this out and also set it to 0, but still no go.
Any ideas? I've tried various apps and they all have no effect
uh, I may be wrong, but how is you changing a setting going to have a physical change on the hardware that's in your tablet?
incarceration said:
uh, I may be wrong, but how is you changing a setting going to have a physical change on the hardware that's in your tablet?
Click to expand...
Click to collapse
It's NOT a physical change - Changing the LCD DPI Density has been a method used on most versions of Android for years. What rock have YOU been under?
Yep. Same here. Can't find a way to get 160 back to life.
This is pretty much a worst thing Asus could do to us. Or is it JB thing?
Don't know, but i'll try to find a solution to this as i just can't look at 240 density after using 160 for so long.
Oversized icons are really not nice :cyclops:
Hmm this might have something to do with my sensitivity issues too. Before in a certain game I could rapidly tap a button and it would go through. Now on JB it's not registering my rapid taps and I have to tap slower. Looking all over the place for a solution!
Alitheia said:
Hmm this might have something to do with my sensitivity issues too. Before in a certain game I could rapidly tap a button and it would go through. Now on JB it's not registering my rapid taps and I have to tap slower. Looking all over the place for a solution!
Click to expand...
Click to collapse
I'm on CM 10(JB 4.1.1.) and DPI change works through the build.prop without any problems. I wonder if Asus did something to block this in latest update..
Could it be related to the kernel not supporting it?
I mean, they probably changed kernel, so maybe they didn't include this in the final release.
Why is beyond me and my understanding of their logic.
I hope this is not the case.
hm.. this is hard to get used to 240 again. i hope theres a way around this
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Don't try the LCD app.
I'm softbrick right now.
I too dislike the hugh icons.
Sent from my HTC PH39100 using xda premium
jaxboater said:
Don't try the LCD app.
I'm softbrick right now.
I too dislike the hugh icons.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Thanks for taking a risk and let us know.
So this option is off, too.
Yeah this DPI is a bit of a shock
dirran said:
Yeah this DPI is a bit of a shock
Click to expand...
Click to collapse
Could you please explain me-a-noob, what's so shocking about the different DPI? I thought the DPI by default remained "at its best setting". Apparently it is not...
Why would ASUS set the DPI in a way, which would not use the full potential of the screen?
iritoi said:
Why would ASUS set the DPI in a way, which would not use the full potential of the screen?
Click to expand...
Click to collapse
I don't know, but they did it .
I miss my 200 DPI. It would be a real shame when there's no way to change the DPI.
iritoi said:
Could you please explain me-a-noob, what's so shocking about the different DPI? I thought the DPI by default remained "at its best setting". Apparently it is not...
Why would ASUS set the DPI in a way, which would not use the full potential of the screen?
Click to expand...
Click to collapse
It tricks Android into making each pixel smaller. Which means all your icons, text, etc shrink on the screen. This gives you more room on your screen and makes mostly everything look a hell of a lot better. If you do a search for DPI on the general forum, you will find a thread about DPI with screen shots that show you the difference.
phree1 said:
It tricks Android into making each pixel smaller. Which means all your icons, text, etc shrink on the screen. This gives you more room on your screen and makes mostly everything look a hell of a lot better. If you do a search for DPI on the general forum, you will find a thread about DPI with screen shots that show you the difference.
Click to expand...
Click to collapse
Same boat. This really sucks. The DPI change is so abrupt, it almost makes me want to downgrade.
spinaldex said:
Same boat. This really sucks. The DPI change is so abrupt, it almost makes me want to downgrade.
Click to expand...
Click to collapse
Why not just try out a custom Rom? At the Moment Baked BlackBean 4 and unofficial CM10 10/1 versions work very well and give you all kinds of settings and tweaks to work with as well as theme chooser. The only thing that isn't working (well or at all) is GPS and I expect that will be fixed in short order, now that the official TF700 JB update is out.
okantomi said:
Why not just try out a custom Rom? At the Moment Baked BlackBean 4 and unofficial CM10 10/1 versions work very well and give you all kinds of settings and tweaks to work with as well as theme chooser. The only thing that isn't working (well or at all) is GPS and I expect that will be fixed in short order, now that the official TF700 JB update is out.
Click to expand...
Click to collapse
Don't get me wrong, I used CM9 on my TF101 and use it on my phone, BUT I like a stable ROM with barely any noticable issues as I really do use just about everything on my devices, including the GPS. For now, until the custom roms make a bit more headway, I'm not going to switch.
Any luck?
Bump on this topic, no go on lcd mods in build.prop
REALLY would like to go back to 160...i may downgrade if there is no workaround...
I can also confirm lcd changer apps dont work either, got soft brick with one and the others didnt change anything
Agreed, any news?
Has anyone contacted Asus about it and asked?
Or, has anyone tested DPI changes on other Jelly Bean devices such as the Nexus 7 and seen if it works there (which would indicate Asus intentionally disabled it)?
spinaldex said:
Agreed, any news?
Has anyone contacted Asus about it and asked?
Or, has anyone tested DPI changes on other Jelly Bean devices such as the Nexus 7 and seen if it works there (which would indicate Asus intentionally disabled it)?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1922747
That proves that ASUS disabled it I'm still unable to unlock.. I need to switch to custom roms soon; I can't stand the default dpi
Related
Any brave dev out there care to port the Touchwiz calculator and dialer for 190 screen density. Infuse is begging to be run at that dpi, just that those stock app do not scale at all.
Thanks in advance.
Yes this would be much appreciated
Is the 190 DPI really that much better? I have not tried it yet. What is stock?
crawlgsx said:
Is the 190 DPI really that much better? I have not tried it yet. What is stock?
Click to expand...
Click to collapse
It IS , stock is 240 ...
190 is Infuse Heaven.
rraquib said:
190 is Infuse Heaven.
Click to expand...
Click to collapse
Guess I need to get off my butt and try it then :-D
I actually have mine at 200 and love it.most apps are.coded to use only 160, 180, 200, and 240 led density. However, Ymmv
.
crawlgsx said:
Guess I need to get off my butt and try it then :-D
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App
I would even settle for 200 but the DIaler looks terrible . Oh well.
h8rift said:
I actually have mine at 200 and love it.most apps are.coded to use only 160, 180, 200, and 240 led density. However, Ymmv
.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
rraquib said:
190 is Infuse Heaven.
Click to expand...
Click to collapse
care to elaborate on how you did that?
I assume it is in the build.prop but I have never edited it myself
There are apps in the market that can do this for you. As for myself, I used root explorer to edit my buildprop. Look for the line with lcd_density, change the value from 240 to 190. Save and reboot.
rraquib said:
There are apps in the market that can do this for you. As for myself, I used root explorer to edit my buildprop. Look for the line with lcd_density, change the value from 240 to 190. Save and reboot.
Click to expand...
Click to collapse
I bought root explorer, changed the lcd_density in build.prop file and now my dialer is shifted to the left. Pretty much everything shifted a little to the left. I love it this way but what did you do to fix the shifting issue?
TIA.
NVM, I was being idiot and did not read that you created this thread to find answers to that.
I noticed that even the apps drawer opens in the top left corner and spacing around it is wasted. I think you have to find all the lcd_density tags and change the values for everything?
S2K_MoZo said:
I bought root explorer, changed the lcd_density in build.prop file and now my dialer is shifted to the left. Pretty much everything shifted a little to the left. I love it this way but what did you do to fix the shifting issue?
TIA.
Click to expand...
Click to collapse
You don't. A dev needs to work on the issue. This is the entire reason this thread even exists.
never mind did it a see the diff..
Icons all outa wack at 190
chvybeatsford said:
never mind did it a see the diff..
Icons all outa wack at 190
Click to expand...
Click to collapse
See, I suppose if you don't wanna use the stock dialer, calculator and TouchWiz you can still use this 190 dpi. Just probably have to use different apps. I personally won't use it but that's cause all of the PNGs in the theme I work on are designed for 240 dpi.
beatblaster said:
See, I suppose if you don't wanna use the stock dialer, calculator and TouchWiz you can still use this 190 dpi. Just probably have to use different apps. I personally won't use it but that's cause all of the PNGs in the theme I work on are designed for 240 dpi.
Click to expand...
Click to collapse
Yea moving back to 240 till stuff is fixed. Looks great at 190 but im not to worried.
Go Launcher Ex and Go Contacts (it includes a Dialer) will get you 75% there @ 190 but the key pad during call is still the stock one . I still think it looks gorgeous at 190 density. Any one knows how the calculation is done. I will try to take a crack at it. At least can start with the calculator with out bricking the phone.
rraquib said:
Go Launcher Ex and Go Contacts (it includes a Dialer) will get you 75% there @ 190 but the key pad during call is still the stock one . I still think it looks gorgeous at 190 density. Any one knows how the calculation is done. I will try to take a crack at it. At least can start with the calculator with out bricking the phone.
Click to expand...
Click to collapse
Makes me wonder if you can control the span via simple XML edits..... hmmm....
You can, some one has done this for another phone. I know where they are in the Main.xml files just don't know what the values should be in relation to the pixel density. Is there any way to make it auto scale?
EDIT: I think the file attached is where the magic needs to happen but how?
Did you try messing with:
android:layout_width="320.0dip" android:layout_height="302.65625dip"
It is in tag:
<LinearLayout androidrientation="vertical" android:id="@id/Linewrapper" android:background="@drawable/call_dial_panel_bg_01" androidaddingRight="6.0dip" android:layout_width="320.0dip" android:layout_height="302.65625dip">
I am tempted to mess with it and see what it does. I am pretty sure that will do something but it will be more like trial and error since we don't know what that measurement equals to...
I would start with the calculator first. Can easily be remedied if things go wrong. Here I am attaching a deodexed Calculator APK. Take a whack at it if you like.
S2K_MoZo said:
Did you try messing with:
android:layout_width="320.0dip" android:layout_height="302.65625dip"
It is in tag:
<LinearLayout androidrientation="vertical" android:id="@id/Linewrapper" android:background="@drawable/call_dial_panel_bg_01" androidaddingRight="6.0dip" android:layout_width="320.0dip" android:layout_height="302.65625dip">
I am tempted to mess with it and see what it does. I am pretty sure that will do something but it will be more like trial and error since we don't know what that measurement equals to...
Click to expand...
Click to collapse
Hi everyone,
I had updated my Nexus S to android 4.1 jelly bean yesterday. I am satisfied with everything but the loss of my turn-off screen animation that previously we had for Nexus S (the oldschool TV turn-off animation).
I would like to know if this is a bug during my installation (the installation went smoothly) or android 4.1 purposely removed such animation? Such screen-off effect is one of the reasons that I bought my Nexus S and I am not willing to see it gone. I had searched the forum but so far did not see anyone facing such problem. Kindly advise me what to do.
Thanks everyone in advance!
emperal said:
Such screen-off effect is one of the reasons that I bought my Nexus S ...
Click to expand...
Click to collapse
Really? Good thing it wasn't deciding factor for me, because I don't seem to have it.
there is thread already on this issue.
http://forum.xda-developers.com/showthread.php?t=1785277
Wow. Only a few topics down and you would have seen that massive thread in the previous post.
emperal said:
Hi everyone,
I had updated my Nexus S to android 4.1 jelly bean yesterday. I am satisfied with everything but the loss of my turn-off screen animation that previously we had for Nexus S (the oldschool TV turn-off animation).
I would like to know if this is a bug during my installation (the installation went smoothly) or android 4.1 purposely removed such animation? Such screen-off effect is one of the reasons that I bought my Nexus S and I am not willing to see it gone. I had searched the forum but so far did not see anyone facing such problem. Kindly advise me what to do.
Thanks everyone in advance!
Click to expand...
Click to collapse
Just hold on for a while and cyanogenmod will bring it back.
alien_x said:
Just hold on for a while and cyanogenmod will bring it back.
Click to expand...
Click to collapse
I just updated to jellybean myself and i did notice that that tv animation was gone too. So after some digging U have to go to settings scoll down to developer options and then down to window animation scale and change it to 1x to bring back that tv on/off screen animation back. Also I kept the Transition animation scale at 5x for apple iphone type of visuals.
The only thing that i do not know what is does is the option called Animator duration scale. I played with it from 5x up to 10x and i have not noticed any difference
If anyone knows a explanation would be nice.
I think it may be the "fade in" animations. I'm still trying to figure it out, but I'm pretty sure that's what those are.
emperal said:
Hi everyone,
I had updated my Nexus S to android 4.1 jelly bean yesterday. I am satisfied with everything but the loss of my turn-off screen animation that previously we had for Nexus S (the oldschool TV turn-off animation).
I would like to know if this is a bug during my installation (the installation went smoothly) or android 4.1 purposely removed such animation? Such screen-off effect is one of the reasons that I bought my Nexus S and I am not willing to see it gone. I had searched the forum but so far did not see anyone facing such problem. Kindly advise me what to do.
Thanks everyone in advance!
Click to expand...
Click to collapse
That's seriously one of the reasons you bought the Nexus S??? It's a cool effect, but to be one of the deciding factors of your purchase.....??
Hi everyone,
Thanks for all replies!
For the tv animation it is just one of the many factors that help me in making my purchase, it is just like the choice between super-lcd and super-amoled can be a deciding factor for someone, but not for someone else who cannot see the difference or who does not care. During my comparison regardless of price my friends told me that galaxy s2 has better spec, better screen, better camera etc. but I chose nexus s over s2 for also reasons that the s2 model in my country could not be updated to latest android without rooting.
For the developer option method it works for me too, but I really dnt like all the extra efforts and time needed to solve these problems, it makes me feel like google doesn't take care of its old customers (my perception only).
If Google didn't take care of it's old customers you wouldn't have the JB update to complain about in the first place...
A TV animation just seems like a trivial thing to complain about in all honesty. Its a known bug on the SLCD model and no software is perfect. And is it really that hard to tap a few buttons to fix some settings? I mean, seriously.
chronophase1 said:
A TV animation just seems like a trivial thing to complain about in all honesty. Its a known bug on the SLCD model and no software is perfect. And is it really that hard to tap a few buttons to fix some settings? I mean, seriously.
Click to expand...
Click to collapse
Exactly. The OP put in more effort to make this thread than it took to re-enable the screen off animation.
shinmadhatter said:
I just updated to jellybean myself and i did notice that that tv animation was gone too. So after some digging U have to go to settings scoll down to developer options and then down to window animation scale and change it to 1x to bring back that tv on/off screen animation back. Also I kept the Transition animation scale at 5x for apple iphone type of visuals..
Click to expand...
Click to collapse
This doesn't work on my device.
chronophase1 said:
A TV animation just seems like a trivial thing to complain about in all honesty. Its a known bug on the SLCD model and no software is perfect. And is it really that hard to tap a few buttons to fix some settings? I mean, seriously.
Click to expand...
Click to collapse
is it really that hard to understand that tapping a few buttons won't fix anything? adjusting the animation scales and whatnot will fix bull****
shinmadhatter said:
The only thing that i do not know what is does is the option called Animator duration scale. I played with it from 5x up to 10x and i have not noticed any difference
If anyone knows a explanation would be nice.
Click to expand...
Click to collapse
Well... that 1x solution didn't work which was already by default on me but increasing 5x and 10x did work.
Sedge.One said:
Doesn't work for me.
All animations are set to 1x bx default, and changes do not affect the behavior of the screen-off-animation.
Click to expand...
Click to collapse
asphantix said:
is it really that hard to understand that tapping a few buttons won't fix anything? adjusting the animation scales and whatnot will fix bull****
Click to expand...
Click to collapse
I just wish I knew why adjusting the rate at which those animations occur seems to somehow fix the issue for some. My complaint was more along the lines of people not wanting to take the effort to attempt to even get into the menu to find those settings. Of course hitting buttons ain't gonna solve anything . Well in most case it wouldn't work. Haha. Speaking of, when I originally disabled my animations, my app drawers animations stopped. Never did that in ICS.
My animation still works...
So to clear up the confusion: This bug only concerns the SLCD version. For those who don't know it, AirKernel seems to fix the problem, it did it for me and I'm running Euroskanks CM10.
Aktifit said:
So to clear up the confusion: This bug only concerns the SLCD version. For those who don't know it, AirKernel seems to fix the problem, it did it for me and I'm running Euroskanks CM10.
Click to expand...
Click to collapse
I am using latest alpha - 0.8 - cm10 rom from kalim for a week and crt animation was gone.
Today I flashed latest hypothalamus-07.26.zip kernel and animation is back on my slcd i9023 :good:
063_XOBX said:
If Google didn't take care of it's old customers you wouldn't have the JB update to complain about in the first place...
Click to expand...
Click to collapse
emperal said:
Hi everyone,
I had updated my Nexus S to android 4.1 jelly bean yesterday. I am satisfied with everything but the loss of my turn-off screen animation that previously we had for Nexus S (the oldschool TV turn-off animation).
I would like to know if this is a bug during my installation (the installation went smoothly) or android 4.1 purposely removed such animation? Such screen-off effect is one of the reasons that I bought my Nexus S and I am not willing to see it gone. I had searched the forum but so far did not see anyone facing such problem. Kindly advise me what to do.
Thanks everyone in advance!
Click to expand...
Click to collapse
the effect will only works on nexus s amoled screen, those models with SclearLCD like i9023...you can't see the effect because the timing of turn off the back light happen earlier than the effect. The TV off effect is actually there, but without backlight, we can't see it...you will see it sometimes, because of delay of the backlight due to hardware slow response... have a nice day, guys... pass this to google team and xda team, this will help them easily fix it ...!
Hi there,
I was looking through the forum without lucky and I have a question. I have a SG3 and I would like to change the LCD density from build.prop without brick my phone. So my question is if anyone know what are any possible value for this?
The default value for my last SG2 was 240, and now the SG3 comes with 320. I used to use the SG2 with 160, but I'm not sure if this will work with my SG3.
Thanks in advance, and hope that this info help to anyone else in the community.
Regards,
PwOn said:
Hi there,
I was looking through the forum without lucky and I have a question. I have a SG3 and I would like to change the LCD density from build.prop without brick my phone. So my question is if anyone know what are any possible value for this?
The default value for my last SG2 was 240, and now the SG3 comes with 320. I used to use the SG2 with 160, but I'm not sure if this will work with my SG3.
Thanks in advance, and hope that this info help to anyone else in the community.
Regards,
Click to expand...
Click to collapse
I've tried few resolutions but they keep crashin the phone...so i just gave up...as every time i have to reflash the rom i'm using cos i cant open any apps...if somone knows a working settings would be great to share with us
smilu said:
I've tried few resolutions but they keep crashin the phone...so i just gave up...as every time i have to reflash the rom i'm using cos i cant open any apps...if somone knows a working settings would be great to share with us
Click to expand...
Click to collapse
bump
SOLUTION:
Before change LCD Density value in build.prop make sure that you have installed Apex Launcher or Nova Launcher in your SG3. In that way your phone will not crash...
PwOn said:
Hi there,
I was looking through the forum without lucky and I have a question. I have a SG3 and I would like to change the LCD density from build.prop without brick my phone. So my question is if anyone know what are any possible value for this?
The default value for my last SG2 was 240, and now the SG3 comes with 320. I used to use the SG2 with 160, but I'm not sure if this will work with my SG3.
Thanks in advance, and hope that this info help to anyone else in the community.
Regards,
Click to expand...
Click to collapse
From my understanding on the Galaxy S3 if you go any lower then 240dpi you will crash your phone. Anything lower then 240 I believe would be used for tablets, and the like.
I set mine to 240. lcd density did not work. build prop change via rom toolbox did and it looks AMAZING for 10 seconds then crashes. (freezes) eventually reboots (trying to reset in adb from CWM now) suggestions?
what could be causing it to crash I REALLY want that higher effective resolution. BADLY.
running leaked JB rom
I set my GS3 LTE to 240, works really well. However there were a couple of qwerks to note:
The launcher is rubbish, changed to EXLauncher pro
I had to mod the email app to fill the screen. sadly i can't attach the modded apk to this post as it is too big.
The camera app is a little strange, but perfectly usable.
The clock app crashes on launch - very irritating, however i set alarms using the voice controls! i should install an alternative clock app.
nerys71 said:
I set mine to 240. lcd density did not work. build prop change via rom toolbox did and it looks AMAZING for 10 seconds then crashes. (freezes) eventually reboots (trying to reset in adb from CWM now) suggestions?
what could be causing it to crash I REALLY want that higher effective resolution. BADLY.
running leaked JB rom
Click to expand...
Click to collapse
you got it so far. use alternative launcher. use alternative clock
calculator and talk are also borked
there IS a user working on converting the apk's to work on the S3 in fact he has most of them done but they don't work on US S3's only the international S3. he says he will try to make them work for US S3's (fingers crossed)
The S3 at stock res sucks. it was MADE for 240 in my opinion.
FYI I rooted the device with I9305_CWM_Recovery.tar.md5 and CWM-SuperSU-v0.96.zip then changed ro.sf.lcd_density in puild.prop from 320 to 240.
for some reason there are 2 entries of ro.sf.lcd_density. I assume the first one gets parsed and the second one ignored, as I changed the second one first to no effect. eventually i changed both.
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
nerys71 said:
you got it so far. use alternative launcher. use alternative clock
calculator and talk are also borked
there IS a user working on converting the apk's to work on the S3 in fact he has most of them done but they don't work on US S3's only the international S3. he says he will try to make them work for US S3's (fingers crossed)
The S3 at stock res sucks. it was MADE for 240 in my opinion.
Click to expand...
Click to collapse
Completely agree. it seems utterly crazy to make such a nice big high res screen then just scale up all the apps as if it was designed for only people with poor eyesight. I almost put my device on ebay ready to go back to iphone before i started getting into it.
Do you have a link to the the modded files? I was just looking through the camera app dimensions definitions and I don't have the time to change those! The email app just involved 3 dimension changes.
GS3 with slimbean.
I Installed slimbean 4.3 beta.2 and it has my screen density as 245. If you take a look at the screen shot I uploaded it shows what to do for changing screen density. Hope this helps.
I'm coming from running a smaller nav bar size of my nexus 4.
I can't stand the icons being this large there is just no need for it.
Do anyone know what scripts I need to edit to get it down to 24dpi ?
Thanks
Sent from my Nexus 5 using XDA Premium HD app
sitnlow4life said:
I'm coming from running a smaller nav bar size of my nexus 4.
I can't stand the icons being this large there is just no need for it.
Do anyone know what scripts I need to edit to get it down to 24dpi ?
Thanks
Sent from my Nexus 5 using XDA Premium HD app
Click to expand...
Click to collapse
You could root and then use a build prop editor to change the density. Or you could wait until roms start appearing (PA, etc). You know, give it time, it should blossom
tremblingwater said:
You could root and then use a build prop editor to change the density. Or you could wait until roms start appearing (PA, etc). You know, give it time, it should blossom
Click to expand...
Click to collapse
This is pretty much it. I'm running 320 DPI right now and it's much more usable, but not perfect yet.
Dungeon47 said:
This is pretty much it. I'm running 320 DPI right now and it's much more usable, but not perfect yet.
Click to expand...
Click to collapse
Found my perfect setting of 400. Didn't really like the huge icons by default, and 320 was way too low for me. 400 suits me fine, and replicates roughly my nexus4.
Don't know why Google changed this personally. Never changed DPI before, is there anything I should be aware of now I have done so?
CrazyPeter said:
Found my perfect setting of 400. Didn't really like the huge icons by default, and 320 was way too low for me. 400 suits me fine, and replicates roughly my nexus4.
Don't know why Google changed this personally. Never changed DPI before, is there anything I should be aware of now I have done so?
Click to expand...
Click to collapse
Google changed it because the screen is higher resolution. The only things to be aware of are the possibility of Play Store having compatibility issues. If you get that, just return to stock DPI, update apps, and go back to what you like. The other thing is that it affects everything, so some apps might change their interface as a result.
Dungeon47 said:
Google changed it because the screen is higher resolution. The only things to be aware of are the possibility of Play Store having compatibility issues. If you get that, just return to stock DPI, update apps, and go back to what you like. The other thing is that it affects everything, so some apps might change their interface as a result.
Click to expand...
Click to collapse
If the screen resolution is higher, why could I fit less on my desktop than my Nexus4? I use Dashclock and it chops off data that was always visible on my N4. Seemed like a backwards step.
Hello,
could anyone please make some navbar mods.
Like 36 dp or 32dp, in my opinion the navbar is just too huge.
Thanks.
Depends on what ROM you have as they're not universal. Need framework, systemui apk as well as a deodexed rom.
oh sry.
For stock rom
Edit:
I already tried it myself, but i cant get i to work. So it would be awesome if someone could make a 36dp version for stock.
Seyren said:
oh sry.
For stock rom
Edit:
I already tried it myself, but i cant get i to work. So it would be awesome if someone could make a 36dp version for stock.
Click to expand...
Click to collapse
Stock rom won't work because it is odexed and not deodexed
Sent from my Nexus 5 using Tapatalk
Seyren said:
Hello,
could anyone please make some navbar mods.
Like 36 dp or 32dp, in my opinion the navbar is just too huge.
Thanks.
Click to expand...
Click to collapse
Until someone makes mods or custom Roms which are able to change the size of the navbar, you can adjust the DPI in build.prop, which will make the navbar smaller.
Sent from my Nexus 5
If it's any help, I've dropped my DPI to 380 in build.prop. Perfect for me
Sent from my Nexus 5 using Tapatalk
Gormsen said:
Until someone makes mods or custom Roms which are able to change the size of the navbar, you can adjust the DPI in build.prop, which will make the navbar smaller.
Sent from my Nexus 5
Click to expand...
Click to collapse
Changing sizes of navbar is easy. I've done it in the past. There aren't much custom ROMs at the moment, only choice that I would choose is SlimKat but still on stock for myself. So if you guys want it done then attach systemui.apk, framework-res.apk and I can do it.
El Nino1977 said:
If it's any help, I've dropped my DPI to 380 in build.prop. Perfect for me
Click to expand...
Click to collapse
Stock DPI is WAY too high on this device. You don't get to take advantage of the great resolution on the screen unless you reduce it. I highly recommend doing this as well.
Anyone been able to add a menu button? Can't seem to figure that on out..
zephiK said:
Changing sizes of navbar is easy. I've done it in the past. There aren't much custom ROMs at the moment, only choice that I would choose is SlimKat but still on stock for myself. So if you guys want it done then attach systemui.apk, framework-res.apk and I can do it.
Click to expand...
Click to collapse
Would love this as well... Stock APK's linked below.
Framework APK
System UI APK
Can someone point me in the direction to where I can learn how to change the DPI in "build.prop"?
Please note I really have no idea where to start, but would love to know how to do this in the future as most nav bars always seem to be too large. Appreciate the help.
Thanks
Edit-
I came across these tutorials. http://modstorm.co/tutorials/ Would you say its tutorials for decompiling android apps, and changing navbar height are accurate?
Thanks
530farm said:
Can someone point me in the direction to where I can learn how to change the DPI in "build.prop"?
Please note I really have no idea where to start, but would love to know how to do this in the future as most nav bars always seem to be too large. Appreciate the help.
Thanks
Edit-
I came across these tutorials. http://modstorm.co/tutorials/ Would you say its tutorials for decompiling android apps, and changing navbar height are accurate?
Thanks
Click to expand...
Click to collapse
Visit the play store. Download Rom Toolbox Lite. Open the app. Slide to the performance tab. Select build.prop Editor. Find the "ro.sf.lcd_density". Change the value. $profit$.
530farm said:
Can someone point me in the direction to where I can learn how to change the DPI in "build.prop"?
Please note I really have no idea where to start, but would love to know how to do this in the future as most nav bars always seem to be too large. Appreciate the help.
Thanks
Edit-
I came across these tutorials. http://modstorm.co/tutorials/ Would you say its tutorials for decompiling android apps, and changing navbar height are accurate?
Thanks
Click to expand...
Click to collapse
Thanks, but doesn't that change the entire screen LCD density? I was just looking to alter the navbar height
Sent from my Nexus 5 using xda app-developers app
530farm said:
Thanks, but doesn't that change the entire screen LCD density? I was just looking to alter the navbar height
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yeah, it does. I wish I knew how to change just the nav bar . I'm just praying that PA comes out with their stuff really soon.
zephiK said:
Changing sizes of navbar is easy. I've done it in the past. There aren't much custom ROMs at the moment, only choice that I would choose is SlimKat but still on stock for myself. So if you guys want it done then attach systemui.apk, framework-res.apk and I can do it.
Click to expand...
Click to collapse
Looking forward to this. Thank you so much!
Sent from my Nexus 5 using Tapatalk
Is there a way to completely remove the Nav Bar. I do worded an app from the play store but it made my phone freak out really bad.
Nexus ONE
There is 1 custom rom right now that has adjustable nav bar height. Released today I think. Not sure if it will disappear if you set it to 0%, but you can shrink it down. 60% works well for me.
Phazmos said:
There is 1 custom rom right now that has adjustable nav bar height. Released today I think. Not sure if it will disappear if you set it to 0%, but you can shrink it down. 60% works well for me.
Click to expand...
Click to collapse
It's Cataclysm in the Original Dev section.
40dp navbar for nexus 5
im not the author, ive found it on nexus 4/5 thread. supports both my device on kikat stock. im also using 380 dpi and seems this is perfect. thanks to the author and if u bump on the original comment where s/he posted please thanks. would still love to see 36/34/32 dp navbar. thank you.
Dungeon47 said:
It's Cataclysm in the Original Dev section.
Click to expand...
Click to collapse
That's the 1, and been running good so far.