Related
Has anybody attempted to adjust the screen density on the MT4G? I've done it before with the Android ROMS on my HD2 and I was thinking that adjusting the density down may have a great effect of the depth and clarity. All the talk in the Desire ROM Thread and how the screen looks just got me thinking.
Anybody that has the location and some instructions that want to toss it out... I will give it a shot.
OR.... I may be way off base.
sicdroid said:
Has anybody attempted to adjust the screen density on the MT4G? I've done it before with the Android ROMS on my HD2 and I was thinking that adjusting the density down may have a great effect of the depth and clarity. All the talk in the Desire ROM Thread and how the screen looks just got me thinking.
Anybody that has the location and some instructions that want to toss it out... I will give it a shot.
OR.... I may be way off base.
Click to expand...
Click to collapse
I have mine running at 190. Most people are running at 200.
instructions are pretty simple with ADB, hopefully you have some experience with it.
adb pull /system/build.prop
open up a text editor and look for "ro.sf.lcd_density=240" change the 240 to desired number and save
adb push build.prop /system/build.prop
reboot
enjoy the additional screen real estate.
Sicdroid let me know your impressions on the mod and I'll be right behind you to try it next
Sent from my HTC Glacier using XDA App
Please post questions in Q&A section.
Foo_Blyat said:
Sicdroid let me know your impressions on the mod and I'll be right behind you to try it next
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I set it to 215... 190 was just a little to small. There is a lot more real estate on the screen for sure.
BTW, I used Root Manager instead of adb. Check it out and see what you think. Easy to test and change it back.
I found what I "Believe" to be a sweet spot for me at 220. The clarity and the way it makes use of the screen is great. I will post a MOD post with the info and sceen shots before and after in the Dev Section.
Reconizing pklee for the info of course.
I know that the most common way people have been switching between phone and tablet modes in AOSP builds of ICS is by changing the lcd density. Well, I'm here to tell you that there is an easier way to do it, and it doesn't create weird looking out-of-aspect-ratio artifacts in certain apps (like Google Music in portrait orientation in tablet mode).
So, in your build.prop, instead of using the traditional ro.sf.lcd_density= line, you can remove that entirely, and use:
ro.build.characteristics=
and after the "=" just put either tablet or phone.
That's it! Easy peasy!
Jade Eyed Wolf said:
I know that the most common way people have been switching between phone and tablet modes in AOSP builds of ICS is by changing the lcd density. Well, I'm here to tell you that there is an easier way to do it, and it doesn't create weird looking out-of-aspect-ratio artifacts in certain apps (like Google Music in portrait orientation in tablet mode).
So, in your build.prop, instead of using the traditional ro.sf.lcd_density= line, you can remove that entirely, and use:
ro.build.characteristics=
and after the "=" just put either tablet or phone.
That's it! Easy peasy!
Click to expand...
Click to collapse
Thanks for the tip mate
That was added in CNA v5 and i think it created problems and was changed back in v5.1.
Fyi, tablet mode changes the dpi to 160, at the moment i use 200 because 160 is a tad bit small for me.
Good tip tho, interested to see if it creates any issues with Imilika v8..
Sent from my GT-N7000 using XDA
Great tip, although this really belongs in the "General" section.
Expect more from someone with almost a thousand posts...
sundazetoo said:
That was added in CNA v5 and i think it created problems and was changed back in v5.1.
Fyi, tablet mode changes the dpi to 160, at the moment i use 200 because 160 is a tad bit small for me.
Good tip tho, interested to see if it creates any issues with Imilika v8..
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
exactly
If you didn't create it... this belongs in general...
Sent from my GT-N7000 using xda premium
Jade Eyed Wolf said:
I know that the most common way people have been switching between phone and tablet modes in AOSP builds of ICS is by changing the lcd density. Well, I'm here to tell you that there is an easier way to do it, and it doesn't create weird looking out-of-aspect-ratio artifacts in certain apps (like Google Music in portrait orientation in tablet mode).
So, in your build.prop, instead of using the traditional ro.sf.lcd_density= line, you can remove that entirely, and use:
ro.build.characteristics=
and after the "=" just put either tablet or phone.
That's it! Easy peasy!
Click to expand...
Click to collapse
So basically you keep the DPI @ 320 & change the above parameter to tablet?
Will this give me the tablet like two panes in settings, gmail & google play?
Screen shot please, and stop crying about this brlongs here ore there. Cry babys
daddymatt said:
If you didn't create it... this belongs in general...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Spot On
Thread Moved To General​
prgopala said:
So basically you keep the DPI @ 320 & change the above parameter to tablet?
Will this give me the tablet like two panes in settings, gmail & google play?
Click to expand...
Click to collapse
So basically ICS has 2 modes, tablet mode and phone mode. To my understanding this is dependent on the dpi, anything lower than 213 dpi will display ICS in tablet mode i.e. 2 panes on most apps. Apparently 160 dpi is the official tablet mode..and i think 320 dpi is the standard phone mode. I currently run mine in 200 dpi and most apps show 2 panes.. I am sure there is a better explanation somewhere
Sent from my GT-N7000 using XDA
sundazetoo said:
That was added in CNA v5 and i think it created problems and was changed back in v5.1.
Fyi, tablet mode changes the dpi to 160, at the moment i use 200 because 160 is a tad bit small for me.
Good tip tho, interested to see if it creates any issues with Imilika v8..
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
So far, I haven't had any issues with Imilka's build. Then again, the stock keyboard still looks funky in portrait tablet mode, but that's nothing new. Everything else works perfectly.
More than anything, this fixes things like tablet portrait Google Music recent's.
sundazetoo said:
So basically ICS has 2 modes, tablet mode and phone mode. To my understanding this is dependent on the dpi, anything lower than 213 dpi will display ICS in tablet mode i.e. 2 panes on most apps. Apparently 160 dpi is the official tablet mode..and i think 320 dpi is the standard phone mode. I currently run mine in 200 dpi and most apps show 2 panes.. I am sure there is a better explanation somewhere
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Absolutely... i don't think just changing the build characteristics parameter to 'tablet' will give you true tablet mode...I guess it will help in apps like music etc where the controls are screwed up in tablet mode...did you try it btw, i mean keeping the DPI below 213 & setting the characteristics to tablet and then check the music app for e.g.
Can sum1 tell me plz ...
what shud i edit in build.prop in order to run gameloft games ...
bcz for default setting it sayz
" your device not compatble blah blah and request for refund "
Using ICS STUNNER ROM
Can ne1 help me out wid dis thing or wts the workaround for this ???
Anyone mess around with LCD Density on stock/FORCE Rom, I usually am always on AOSP and most of the roms have a built in LCD changer which I always use- usually actually just the normal Slimbean density. But I've been missing showing off some of the TW features to friends but I can't stand how massive everything is on stock. Like to go down to 360 at least. Any recommendations on the safest/best third party app on changing the LCD density, or is that not chill to do on Stock TW, not sure of the limitations of it and what not!
Sent from my SPH-L720 using xda app-developers app
Looking for the same! DO NOT USE
"LCD Density Modder" was a little buzzed a week after owning the s4 and didnt read the comments. It ended up bricking my phone. Thank God for my 14 day exchange policy!
Sent from my SPH-L720 using xda app-developers app
sprint_dobbs said:
Looking for the same! DO NOT USE
"LCD Density Modder" was a little buzzed a week after owning the s4 and didnt read the comments. It ended up bricking my phone. Thank God for my 14 day exchange policy!
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the heads up! I'm not sure on the technical details of it, on my S3 I never had a TW rom that changed LCD density so I'm thinking it may have something to do with that?
Just looking for a definite confirmation or not if it is possible! And oh wow that's definitely lucky! Don't mess up the new one ;P
Sent from my SPH-L720 using xda app-developers app
inlineboy said:
Anyone mess around with LCD Density on stock/FORCE Rom, I usually am always on AOSP and most of the roms have a built in LCD changer which I always use- usually actually just the normal Slimbean density. But I've been missing showing off some of the TW features to friends but I can't stand how massive everything is on stock. Like to go down to 360 at least. Any recommendations on the safest/best third party app on changing the LCD density, or is that not chill to do on Stock TW, not sure of the limitations of it and what not!
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I haven't done it yet on the S4, but you can usually modify your build.prop file located in /system/ There is a setting for density there. Or you can try out XPOSED framework, but last I checked, they hadnt gotten it to work with the S4 yet. Just tread lightly as modifying the build.prop density will likely make stock apps(phone,contacts,etc) not scale properly.
ACoolGuy said:
I haven't done it yet on the S4, but you can usually modify your build.prop file located in /system/ There is a setting for density there. Or you can try out XPOSED framework, but last I checked, they hadnt gotten it to work with the S4 yet. Just tread lightly as modifying the build.prop density will likely make stock apps(phone,contacts,etc) not scale properly.
Click to expand...
Click to collapse
Yeah I know I could manually edit my build.prop but I'd rather not mess around with anything myself
Yeah I'm pretty sure Xposed is out for the S4 yet.
I'm just looking to see if anyone has had an success themselves changing the density on Stock TW, and as I've always been wary (I have never even used) of density changing apps, was looking for if anyone had any success or experience with doing so.
Sent from my SPH-L710 using xda app-developers app
im looking for the same thing... i would like to give TW a chance but i just cant deal with how big and clumsy everything feels/looks to me
Accidentally used LCD Density Modder
So I tried to use the LCD Density Modder app before I read not to and now I appear to be bricked. Does anyone know of any way to undo it without doing a factory reset?
have you not tried rom toolbox? it has a build prop editor built in....you wont get to scale your apps but if something goes wrong and you start getting force closes you can easily go back in an change it....just make your modifications in incriments of like 25 or 50 untill you start having issues then back it off to a point where you were good just like on AOSP. 360 of course being the lowest you can go on the s4. also if your worried about editing your build prop you can get holo launcher.....it has an option to scale your apps icon size so your not actually changing lcd density.also has a nice AOSP feel if thats what your used to.
I'm bricked
I'd love to try ROM Toolbox at some point, but right now my problem is that my phone doesn't work. When I boot it up, I see the boot screen, then it goes black, and a few minutes later the blue LED turns on and stays lit and phone starts getting pretty warm. I don't have a custom recovery, but I even tried a factory data reset using the built-in recovery mode and that didn't work so now I'm at a loss. I'm wondering if anyone else has had the same problem and/or knows how to fix my phone.
I used JRummy's build.prop and it worked like a charm. Down at the bottom you will see density. Default is 480 but I like 420 or 400 personally but you can change it however you like. Cheer's!
This app will allow you to change the intensity of the vibration your device gives you, some kernels/mods do this specific feature, but with this app you can change it even on custom kernels or stock roms. You just need root.
https://play.google.com/store/apps/details?id=com.dunnow.software.vibrationTuner
A while ago I wrote this app to enhance my personal UX on my N4, I've been told it works well with N5 too, since it might be usefull for some of you guys, I'm sharing it here.
ROOT IS REQUIRED. Please read the app description.
Thanks, that really helped
Sent from my Nexus 5 using xda app-developers app
Working anyone?
All intensities from 1 to 95 feel the same!
Yep working pretty well not to say perfectly.
In case it can help I have Nexus 5 stock rom rooted only.
Maybe depending on how much you changed from stock result could be different...
letmedanz said:
Working anyone?
All intensities from 1 to 95 feel the same!
Click to expand...
Click to collapse
Maybe you're doing the same mistake as i did.
After you adjust the slider to a new value you need to push the "Set intensity" before you can use the Test button with the new value.
Took me 5 min to realise that.. :|
i need to root for this?
thank you mate
Ya it works amazing on mine and I'm on stock odex with root
Sent from my Nexus 5 using xda app-developers app
I used this. Confirmed it works. I like it on 70.
Sent from my Nexus 5 using XDA Premium 4 mobile app
warsylep said:
Maybe you're doing the same mistake as i did.
After you adjust the slider to a new value you need to push the "Set intensity" before you can use the Test button with the new value.
Took me 5 min to realise that.. :|
Click to expand...
Click to collapse
Yep, sorry about that, last update changed UI and UX "set intensity" is no longer needed, just select the value and done.
3puntos said:
i need to root for this?
thank you mate
Click to expand...
Click to collapse
Yep, root is mandatory since it edits system lvl files, since apps can't write on those files, root is mandatory to do so. Sorry if it's an inconvenience. u_u
Great app. I was looking for something like this.
Dunnow said:
This app will allow you to change the intensity of the vibration your device gives you, some kernels/mods do this specific feature, but with this app you can change it even on custom kernels or stock roms. You just need root.
Click to expand...
Click to collapse
Hey,
I need to make something similar for my HTC one (m8) runnig gpe, the vibration is insane.
Could you shed some light on how this app works?
I'm guessing it's a kernel module which changes the vibration intesity?
brujoand said:
Hey,
I need to make something similar for my HTC one (m8) runnig gpe, the vibration is insane.
Could you shed some light on how this app works?
I'm guessing it's a kernel module which changes the vibration intesity?
Click to expand...
Click to collapse
Actually it does not play with the kernel at all. Turns out that Nexus LG devices have a file with the intensity, so, basically, this app, overwrites that value on each boot to set the user prefered default and from there the system takes care to get that value and go on.
The file locations it's listed on the "FAQ" part of the app. Some people told me to add support to other devices, but they don't seem to have such file, or at least, not under the same file directory. You could search for it (if it's even there) and If it is (under another directory ofc) I could try to add compatibility to my app and solved.
It actually bothers me that people is rating the app poorly just because they can't read this is ment only for N4 and 5 (since are the only 2 that i know of using that method) ... u_u
Hi All,
work this with AOSP ROM? Where can I find the apk file? I have now no internet connection on my phone, so I could not download it from Store directly.
Thanks in advance!
I use Trickster Mod for controlling the vibration because it also does many, many other things.
As some of you may notice,the titan performs strangely poorly on pie,this is due to pie's new skiagl renderer which doesn't play well with our device,the zip below will return pie to the old renderer used on Oreo and below (OpenGL HWUI) and reduce the lag significantly,you will quickly notice a difference if you use either the XDA app or Lawnchair launcher,you will see their huge stutters are no more all thx to OpenGL HWUI,also don't expect this to ever be merged officially into a ROM as OpenGL does have some small issues like screenshots not appearing in the notifications properly,other than that it's a great way to boost the performance of our beloved titan,this patch was already merged on the Moto g4 play and LG G2 both with very positive feedback but won't be merged into the titan's device tree as by request of it's developers (so please don't bother any of the devs about this patch as it was already refused into the main device tree)
Did anyone try this?
amir.nawed said:
Did anyone try this?
Click to expand...
Click to collapse
Feel free to try,the worst that can happen is the fix not working
DanGLES3 said:
Feel free to try,the worst that can happen is the fix not working
Click to expand...
Click to collapse
Will try and update in comment.
Btw, the latest build of LOS 16 use OpenGL or Skiagl??
amir.nawed said:
Will try and update in comment.
Btw, the latest build of LOS 16 use OpenGL or Skiagl??
Click to expand...
Click to collapse
Skia,as I said,Renan didn't implement the fix for some reason (he didn't make it very clear why)
Sadly it made no difference on my device running LOS 16 December build. The ui is still laggy. I wonder how the AOSPExtended Pie rom is so smooth!
amir.nawed said:
Sadly it made no difference on my device running LOS 16 December build. The ui is still laggy. I wonder how the AOSPExtended Pie rom is so smooth!
Click to expand...
Click to collapse
The UI will still lag a lot (thanks to HWC2),my fix effect is small on most apps,but apps like lawnchair or the XDA labs apps see huge improvements,also tbh aex and Los 16.0 run almost exactly the same for me
The reason we cant use it while building: This prop causes some bugs like screenshot preview doesnt show up on notification panel, and few more, tho, they are minor, but yet people will complain, so its better to keep this hack optional
thedeadfish59 said:
The reason we cant use it while building: This prop causes some bugs like screenshot preview doesnt show up on notification panel, and few more, tho, they are minor, but yet people will complain, so its better to keep this hack optional
Click to expand...
Click to collapse
Indeed, totally agree,thx for the explanation
Sent from my Moto G 2015 using XDA Labs
@DanGLES3
Does this tweak work in the same way as adding command "hwui.renderer = opengl" to build.prop?
Or is there a difference?
Dugatoembridge said:
@DanGLES3
Does this tweak work in the same way as adding command "hwui.renderer = opengl" to build.prop?
Or is there a difference?
Click to expand...
Click to collapse
Pretty sure this build.prop command doesn't exist on android,I only saw debug.hwui.renderer when looking through pie sources
Sent from my Moto G 2015 using XDA Labs
DanGLES3 said:
Pretty sure this build.prop command doesn't exist on android,I only saw debug.hwui.renderer when looking through pie sources
Sent from my Moto G 2015 using XDA Labs
Click to expand...
Click to collapse
Yes the command is this, I just abbreviated!
Dugatoembridge said:
Yes the command is this, I just abbreviated!
Click to expand...
Click to collapse
Yeah,my fix just modifies the ROM at install time to prevent unecesary reboots afterwards to modify the build.prop file
Sent from my Moto G 2015 using XDA Labs
I recommend to add ro.config.low_ram=true to build.prop and check some tweaks for performance and battery, the last rom i checked (AOSP Extended Pie) with that and other tweaks, i got a little more of free ram and a little better performance (slighty better but it didn't make much difference)