I'm running most recent cm11/cMetal ROM and am trying to change the LCD density from stock to 240. I've got ROM toolbox pro and tried to use the built in build.prop editor but it doesn't seem to work.
Is this a 4.4 issue? I've tried in r/w and r/o and it does not work (I only did that because someone mentioned it during my research.)
Has anyone had any success or have any tips?
legal.xchech said:
I'm running most recent cm11/cMetal ROM and am trying to change the LCD density from stock to 240. I've got ROM toolbox pro and tried to use the built in build.prop editor but it doesn't seem to work.
Is this a 4.4 issue? I've tried in r/w and r/o and it does not work (I only did that because someone mentioned it during my research.)
Has anyone had any success or have any tips?
Click to expand...
Click to collapse
I'm also wanting to change and haven't found a way yet .
legal.xchech said:
I'm running most recent cm11/cMetal ROM and am trying to change the LCD density from stock to 240. I've got ROM toolbox pro and tried to use the built in build.prop editor but it doesn't seem to work.
Is this a 4.4 issue? I've tried in r/w and r/o and it does not work (I only did that because someone mentioned it during my research.)
Has anyone had any success or have any tips?
Click to expand...
Click to collapse
Navigate to /system/build.prop using Solid/Root explorer and open it in text editor and change the property ro.sf.lcd_density to 240 or whatever you like. Then reboot.
RajatPatel said:
Navigate to /system/build.prop using Solid/Root explorer and open it in text editor and change the property ro.sf.lcd_density to 240 or whatever you like. Then reboot.
Click to expand...
Click to collapse
Yup, that worked! I'm a little disappointed I didn't think of editing it manually myself. Oh well. Thanks for the help!
I just tried this on the newest CM11 nightly and got a bootloop. Anyway to fix this?
Unchange said:
I just tried this on the newest CM11 nightly and got a bootloop. Anyway to fix this?
Click to expand...
Click to collapse
Dirty flash your ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Dirty flash your ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I don't mean how to fix the boot loop; I mean how can I get the LCD density change to stick without a boot loop?
Unchange said:
I don't mean how to fix the boot loop; I mean how can I get the LCD density change to stick without a boot loop?
Click to expand...
Click to collapse
There is no reason your lcd density should have caused a bootloop unless you configured the numbers outside of the galaxy nexus proper density radius or you messed with the wrong thing in build.prop. Try downloading Build Prop Editor from the play store and only modify the LCD Density.
DPI 280 is so clear and comfortable.
With latest nightly cm-11-20140120 I am unable to change the lcd density. Seems lcd_density attribute in build.prop is ignored... Anyone experiencing this issue?
mgaw said:
With latest nightly cm-11-20140120 I am unable to change the lcd density. Seems lcd_density attribute in build.prop is ignored... Anyone experiencing this issue?
Click to expand...
Click to collapse
It's the only thing I manually change after dirty flashing each nightly and has always worked for me. I'm on toroplus for what it's worth...and I ran the 20th, 21st and now 22nd nightlies.
yotvb531 said:
It's the only thing I manually change after dirty flashing each nightly and has always worked for me. I'm on toroplus for what it's worth...and I ran the 20th, 21st and now 22nd nightlies.
Click to expand...
Click to collapse
Actually, with 22nd it works again for maguro.
Related
does anybody found a way to change system fonts on ICS?
redeyes717 said:
does anybody found a way to change system fonts on ICS?
Click to expand...
Click to collapse
Replace DroiSans.ttf (and DroidSanBold.ttf) in /system/fonts/ with your preferred font.
You'll need to be rooted of course.
so, almost same way than GB. Do we need busybox installed?
redeyes717 said:
so, almost same way than GB. Do we need busybox installed?
Click to expand...
Click to collapse
No, you don't need busybox...
this is not working at all.
what's working you can find here, it's a start...
http://forum.xda-developers.com/showpost.php?p=19894335&postcount=5
Rom toolbox it work for me...
Sent from my Galaxy Nexus using XDA App
Hey Guys,
i have the problem that the paradroid doesn't work complite.
it can change the lauchner but not an app allone (for example youtube).
does someone know how to fix it?
So i have a desire hd with the pacman rom v19.3(inkl. Gapps) with the KangBangKernel.
I have flashed the paradroid.zip from the thread.
peace spradd
nobody knows how to fix it?
I must confess that I can't figure out what your problem is. What do you mean by change an app?
bananagranola said:
I must confess that I can't figure out what your problem is. What do you mean by change an app?
Click to expand...
Click to collapse
I believe that he means the Default Actions dialogue box.
bananagranola said:
I must confess that I can't figure out what your problem is. What do you mean by change an app?
Click to expand...
Click to collapse
it means the layout and size wich you can configurate in the Paranoidsettings
spraddl said:
it means the layout and size wich you can configurate in the Paranoidsettings
Click to expand...
Click to collapse
I guess I have the same problem - after choosing any app from the list to change the resolution the PA settings app FC. I can change the overall system settings in PA though. Tried clearing data of the PA settings app, but no luck.
Martinez
hi, i have a gnexus with slimbean v1.8 and mpokang-v10 "superam version".
the application is installed correctly, but when I go to download a theme it says that my device is not supported.
Please help me.
ipernexus said:
hi, i have a gnexus with slimbean v1.8 and mpokang-v10 "superam version".
the application is installed correctly, but when I go to download a theme it says that my device is not supported.
Please help me.
Click to expand...
Click to collapse
Had the same problem on my gnex with PA 3.99 RC2, for me it was a problem with the DPI settings. If I remember correctly Slimbean came with a altered DPI setting out of the box. Maybe you can fiddle with that, I know it worked for me
xxxmarienxxx said:
Had the same problem on my gnex with PA 3.99 RC2, for me it was a problem with the DPI settings. If I remember correctly Slimbean came with a altered DPI setting out of the box. Maybe you can fiddle with that, I know it worked for me
Click to expand...
Click to collapse
my LCD density is set to 245.. is this the problem? :S
ipernexus said:
my LCD density is set to 245.. is this the problem? :S
Click to expand...
Click to collapse
Yes, set it to the stock dpi for gnex, 320 I believe. Then you should be good.
Sent from my Galaxy Nexus using xda app-developers app
You also need to keep the navbar size on default...
Gesendet von meinem Galaxy Nexus mit Tapatalk
to get around it and keep the dpi that you want, you could install xposed framework and use the Play Store Fixes module from the downloads section in framework installer, and set it to fake 320 dpi and no restrictions path. i use it on carbon rom with a dpi of 260 and never have a play store issue, including themer beta.
OR you can try a different rom. Dont get me wrong I like slimbean but, Im just saying
I like how the op says themer beta doesn't work at all but he's using a custom rom like slimbeam, really...., you should say it doesn't work on slimbeam instead of blaming the app, works flawless on stock 4.3 even for a beta.
hey guys,
this might be a more broader android question, but either way: is there a way to change the hardware device name of a device?
i.e. my issue is the following - i use the "good for work" application for my work emails. My company basically has every manufacturer added to their approved list (HTC, Samsung, even Nexus devices work no problem). Now that I have my sweet OP3, I get the below error message (pic attached)
"the device hardware version is 'oneplus a3000 android 6.0.1' and is not permitted. Install the application on a permitted device."
now - before you tell me to go to my network admins and have the device added - I can't do that for reasons I won't go into here. Basically i want to understand if there's a way to change certain files on the phone that will make this application think it's a nexus device and clear it.
I tried editing the build.prop file (using twrp and adb - since I don't have root) to remove all mention of oneplus, etc. and replacing with "nexus" or something else (used the build.prop file from my 5x for reference). But the app still does not work and the OP3 still shows the model as One Plus 3 in the "about phone" section. This is really fascinating to me. What is driving this device's identity?
Appreciate any thoughts/suggestions you might have.
Try xposed mods... I think it is possible
Wrong forum.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
wrong section.
post this in Q&A
@piotrus22, If you correctly modified your build prop then it's almost impossible to come as Oneplus name in about section of setting.
as far as I know the name in about section is read from build prop.
can you provide link to your modified build.prop file so i can see what's a problem.
Have you applied correct permissions (rw-r--r-- or 0644) to build prop after side loading
Go to your Bluetooth settings, select the menu, and Rename this device.
JumboMan said:
@piotrus22, If you correctly modified your build prop then it's almost impossible to come as Oneplus name in about section of setting.
as far as I know the name in about section is read from build prop.
can you provide link to your modified build.prop file so i can see what's a problem.
Have you applied correct permissions (rw-r--r-- or 0644) to build prop after side loading
Click to expand...
Click to collapse
thanks @JumboMan. attached are both build.props (edited and non-edited). I ran the command "adb shell chmod 644 /system/build.prop" after I pushed the file onto the phone. I believe it worked because I added the line about LCD density (ro.sf.lcd_density=420) and the density did indeed change. Also - I am able to view the updated build.prop in a file browser when I open the phone with the changes I've made.
...still confused...
piotrus22 said:
thanks @JumboMan. attached are both build.props (edited and non-edited). I ran the command "adb shell chmod 644 /system/build.prop" after I pushed the file onto the phone. I believe it worked because I added the line about LCD density (ro.sf.lcd_density=420) and the density did indeed change. Also - I am able to view the updated build.prop in a file browser when I open the phone with the changes I've made.
...still confused...
Click to expand...
Click to collapse
I have carefully inspected build.prop file and i found that build.prop doesn't have "ro.product.model" line . That's why you are not able to change device name.
So if you have to change device name you have to manually add above line with whatever device name you want and push file to phone and apply proper permissions
e.g ro.product.model=device name you want
In your case above line will look like ro.product.model=Nexus 5x
Though not required,change lines containing OnePlus to your custom device name
JumboMan said:
I have carefully inspected build.prop file and i found that build.prop doesn't have "ro.product.model" line . That's why you are not able to change device name.
So if you have to change device name you have to manually add above line with whatever device name you want and push file to phone and apply proper permissions
e.g ro.product.model=device name you want
In your case above line will look like ro.product.model=Nexus 5x
Though not required,change lines containing OnePlus to your custom device name
Click to expand...
Click to collapse
ok - making progress here. the model name now shows up as Nexus 5x, but when the computer recognizes the phone it still shows up as ONEPLUS A3000... and what about the build? I've tweaked everything I can think of but still can't change the build number from "ONEPLUS A3000_16_0705"
any ideas?
piotrus22 said:
ok - making progress here. the model name now shows up as Nexus 5x, but when the computer recognizes the phone it still shows up as ONEPLUS A3000... and what about the build? I've tweaked everything I can think of but still can't change the build number from "ONEPLUS A3000_16_0705"
any ideas?
Click to expand...
Click to collapse
now I think I'm going out of ideas.
I think you have to ask some experienced dev
JumboMan said:
now I think I'm going out of ideas.
I think you have to ask some experienced dev
Click to expand...
Click to collapse
how do I do that? just hope one of them sees this post? LOL
piotrus22 said:
how do I do that? just hope one of them sees this post? LOL
Click to expand...
Click to collapse
Yesterday I researched a lot about your question but I only found half answer.
Now Today I'm back with more build prop lines that will 100% solve your question.
This time I tested myself first before posting to confirm the changes
So here is a Trick
=====
1.To change Model Number
ro.product.model=Nexus 5x
2.To Change Build Number
ro.build.display.id=Nexus 5x
ro.build.display.full_id=Nexus 5x
ro.build.id.hardware=Nexus 5x
=====
Note - value "Nexus 5x" is used just as an example.
You change this value to anything you want.
JumboMan said:
Yesterday I researched a lot about your question but I only found half answer.
Now Today I'm back with more build prop lines that will 100% solve your question.
This time I tested myself first before posting to confirm the changes
So here is a Trick
=====
1.To change Model Number
ro.product.model=Nexus 5x
2.To Change Build Number
ro.build.display.id=Nexus 5x
ro.build.display.full_id=Nexus 5x
ro.build.id.hardware=Nexus 5x
=====
Note - value "Nexus 5x" is used just as an example.
You change this value to anything you want.
Click to expand...
Click to collapse
you sir are amazing. just tried it and it worked. will test it out to see if it causes other issues. may I buy you a beer?
piotrus22 said:
may I buy you a beer?
Click to expand...
Click to collapse
For me Thanks=Beer, so thanks are sufficient
JumboMan said:
For me Thanks=Beer, so thanks are sufficient
Click to expand...
Click to collapse
Ok @JumboMan, so now my phone won't save video. Basically when I try to take a video with the camera app, it hangs up on the "saving" section. Then the only way to get the camera running again is to reboot. I can't believe this is related to what I did in the build.prop files right?
The driver names will ever be the real device name. So...
:thumbup:
Sent from my XT320 using xda premium
piotrus22 said:
Ok @JumboMan, so now my phone won't save video. Basically when I try to take a video with the camera app, it hangs up on the "saving" section. Then the only way to get the camera running again is to reboot. I can't believe this is related to what I did in the build.prop files right?
Click to expand...
Click to collapse
It may be due to build prop changes but I'm not sure. can you use 3rd party camera app check for your problem. or it only occurs with stock camera.
JumboMan said:
It may be due to build prop changes but I'm not sure. can you use 3rd party camera app check for your problem. or it only occurs with stock camera.
Click to expand...
Click to collapse
Third party camera app has the same problem. Will revert to original build prop and see if that fixes the issue. Will report back.
JumboMan said:
For me Thanks=Beer, so thanks are sufficient
Click to expand...
Click to collapse
Dethfull said:
The driver names will ever be the real device name. So...
:thumbup:
Sent from my XT320 using xda premium
Click to expand...
Click to collapse
@Dethfull do you know which items in the build prop coordinate to the drivers for the camera?
ok so I think I fixed it. I played around with the build.prop file and it appears changing the ro.product.manufacturer =OnePlus back from Nexus5 did the trick. Camera seems to be much faster than before and videos can save now, and the Good app still works.
Will update if things change but hopefully not!
Changed my OP3 DPI to 400 and certain apps acting weird, MX Player huge thumbnails, cant properly crop pictures for DP in Whatsapp and Instagram and so on. Changing to original 480 DPI solves all problem its huge for me, anything to do? I changed DPI using "[email protected]_radaideh"
paul369741 said:
Changed my OP3 DPI to 400 and certain apps acting weird, MX Player huge thumbnails, cant properly crop pictures for DP in Whatsapp and Instagram and so on. Changing to original 480 DPI solves all problem its huge for me, anything to do? I changed DPI using "[email protected]_radaideh"
Click to expand...
Click to collapse
Thre is always some or other issue when you change dpi on a non rooted phone. Once you root your phone changing dpi works more flawlessly.
paul369741 said:
Changed my OP3 DPI to 400 and certain apps acting weird, MX Player huge thumbnails, cant properly crop pictures for DP in Whatsapp and Instagram and so on. Changing to original 480 DPI solves all problem its huge for me, anything to do? I changed DPI using "[email protected]_radaideh"
Click to expand...
Click to collapse
how did you change dpi? adb command (adb shell wm density) is not sufficient. you have to change also build.prop file and all your apps will work (this is possible also without rooting --ie: temporary boot in TWRP + mount system as RW + pull/push system/build.prop -- , but it is much easier to do everything if you are rooted). be aware that future OTA updates will fail if you modify build.prop.
bonham1988 said:
Thre is always some or other issue when you change dpi on a non rooted phone. Once you root your phone changing dpi works more flawlessly.
Click to expand...
Click to collapse
Im rooted and Xposed
paul369741 said:
Im rooted and Xposed
Click to expand...
Click to collapse
Ok try le dpi changer or a script on xda for debloating and changing dpi. Both of them works fine on my OnePlus 3
Sent from my OnePlus3 using XDA Labs
Blu3Blood said:
how did you change dpi? adb command (adb shell wm density) is not sufficient. you have to change also build.prop file and all your apps will work (this is possible also without rooting --ie: temporary boot in TWRP + mount system as RW + pull/push system/build.prop -- , but it is much easier to do everything if you are rooted). be aware that future OTA updates will fail if you modify build.prop.
Click to expand...
Click to collapse
I Just used the Toolkit nothing else modified, if change dpi back to original while OTA then no issues huh?
bonham1988 said:
Ok try le dpi changer or a script on xda for debloating and changing dpi. Both of them works fine on my OnePlus 3
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Tried le dpi changer , now phone doesnt boot :crying::crying::crying:
paul369741 said:
Tried le dpi changer , now phone doesnt boot :crying::crying::crying:
Click to expand...
Click to collapse
Try changing the build prop file from twrp. Reset the dpi from there and see if that works? Or restoring a previous backup if you had one.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Try changing the build prop file from twrp. Reset the dpi from there and see if that works? Or restoring a previous backup if you had one.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
I pulled my build.prop and all it has now is lcd density=420 etc , nothing else, i flashed OOS again, hope its fixed
paul369741 said:
I pulled my build.prop and all it has now is lcd density=420 etc , nothing else, i flashed OOS again, hope its fixed
Click to expand...
Click to collapse
Resetting the original dpi value I.e., 480 might have worked anyhow since you've reflashed oos try the Aroma debloater script on xda. I changed dpi and got rid of stock apps from that script only and it worked fine.
Sent from my OnePlus3 using XDA Labs