I'm on MM 20B now, I'm trying to change the stock DPI from 640 to 540 but the phone goes in bootloop, from there I use TWRP to replace the "build.prop" file with a untouched copy to solve the loop. Now, why is it doing that in the first place. Btw is not a MM problem, I had this problem even with LP roms.
alinnsts said:
I'm on MM 20B now, I'm trying to change the stock DPI from 640 to 540 but the phone goes in bootloop, from there I use TWRP to replace the "build.prop" file with a untouched copy to solve the loop. Now, why is it doing that in the first place. Btw is not a MM problem, I had this problem even with LP roms.
Click to expand...
Click to collapse
Use an editor that does not truncate the build.prop to a size of maximum 10KB. Most editors do so you will "lose" the end of the file.
Textroider is a nice and simple app to do the task you're trying to achieve :good:
Pfeffernuss said:
Use an editor that does not truncate the build.prop to a size of maximum 10KB. Most editors do so you will "lose" the end of the file.
Textroider is a nice and simple app to do the task you're trying to achieve :good:
Click to expand...
Click to collapse
Thanks mate! ?
Related
So I flashed the CyanogenMod 6.1 and I love it. Then tried to used the LCD changer to make my desktop like I had it before on the stock ROM. I changed the Value to 200 and now every time I change from Portrait to Landscape view and visa versa I get an error saying "Android.process.acore has stopped unexpectedly" Can anyone help with this? Thanks
I have no idea but should of just change the density in the build.prop using root explorer, really makes it easy...
Sent from my T-Mobile G2 using Tapatalk
Sent from my T-Mobile G2 using XDA App
I've been getting the acore force close a lot too. Not sure if its when changing orientation. Just happens sparatically.
I got the force close also when I set the density between 200 and 210. 190 and 220 both seem to work good so far.
I used the temp root method instead of directly modifying the build.prop file. Setting it at 200 is perfectly fine, had no issues.
Sent from my T-Mobile G2 using XDA App
im having the same problem @ 200...
just out of curiosity, and because im slightly lazy and at work right now, but where is build.prop located?(i dont have my phone with me right now and will have to change it later)
I tried 220 and got the same thing..ill try 190 and see. I will also try to edit the build.prop and see where that gets me
Sent from my T-Mobile G2 using XDA App
jeallen0 said:
im having the same problem @ 200...
just out of curiosity, and because im slightly lazy and at work right now, but where is build.prop located?(i dont have my phone with me right now and will have to change it later)
Click to expand...
Click to collapse
ok i found the build.prop... gonna change it on my break with root explorer and see what happens.
So I wiped and re-installed cyanogenrom6.1 and used lcd changer and tada!! No more force closes! must have just been something weird in the first install of cyanogen.
Sent from my T-Mobile G2 using XDA App
I am experiencing the same issues using 200. I want to change it in build.prop but cant get Root Explorer to mount it as RW...Anyone have any ideas?
I know its a hack...
I used adb to mount -o rw,remount /dev/block/mmcblk0p25 /system
then went in Root Explorer and could make the edits...What can i do to make it permanent?
wpickel said:
I am experiencing the same issues using 200. I want to change it in build.prop but cant get Root Explorer to mount it as RW...Anyone have any ideas?
Click to expand...
Click to collapse
Did you click the button on top of root explorer that says mount at r/w? You have to do that first. Edit then save. It will save a back-up build.prop. Make sure youve done a nandroid backup before this tho cuz if you screw up your build.prop it will be the only was to fix it.
wpickel said:
I am experiencing the same issues using 200. I want to change it in build.prop but cant get Root Explorer to mount it as RW...Anyone have any ideas?
Click to expand...
Click to collapse
yeah, make a copy of default.prop and add this line "ro.secure=0". repush the file with terminal emulator or adb.
Hey gus,
today my Camera suddenly stopped working properly. When i try to use dual mode or start taking a video, the app suddenly crashes.
I already tried a factory reset. After that I could not even find the app installed, it disappeared. When I reinstalled it (backuped the apk before reset) I got the same issue: dual mode and videos not working. The phone was rooted and I used the camera mod that sets the 1080p framerate to to 60 fps, but the camera worked properly until today. In addition to that the media profiles xml should be original again since I did a factory reset, so this should not be the problem.
Anyone pls help me.
Maybe someone can upload his/her camera files so I can try installing another apk? Its possible I got a damaged apk or so..
When you change something in protected area i.e. system you change it for good. No matter how many factory resets you do it would stay the same. Applying camera mod involved modifying mediaprofile.xml that is in system/etc folder. Only way to fix it would be to grab the stock mediaprofile.xml and put it back in the system/etc folder.
Sent from my LG-D850 using XDA Premium 4 mobile app
I guess I'm not the only one having issue with the camera mods. I changed framerate to 1080p60, but got worse results and the phone got stuck on the boot screen. Had to use the flashtool to go back to stock. If your phone boots, restore the xml as previously mentioned. Im curious, which version of the G3 do you have?
Thanks for your answers
@enaybee: could you please upload your original file? I just dud a backup of the apk, forgot the media profiles.
@garykl: Got the german 16 GB version from 1&1
LosG said:
could you please upload your original file? I just dud a backup of the apk, forgot the media profiles.
Click to expand...
Click to collapse
Here you go media profile xml
Thanks man, now I just need to reinstall it as a system app, can you explain what i have to do? I put it in the priv-apps folder and etc folder, rebooted, but nothing happened
Just grab the mediaprofile.xml and place it inside /system/etc directory with the help of any file explorer that gives you access to system folder (requires root) like root explorer or es explorer. Make sure stock file replaces the modified file. Reboot and that should take care of the issue if it was only caused by the mod.
Sent from my LG-D850 using XDA Premium 4 mobile app
I already did this with es explorer, set the permissions to rw r r and rebooted, all files are in the right folders.
Still no camera app
Maybe it doesnt work because we got different phone versions?
I checked the model number and it says D-855
Edit:I dont know why, but suddenly the app appeared in my drawer. Problem solved, thanks alot for your help [emoji106]
LosG said:
Problem solved, thanks alot for your help [emoji106]
Click to expand...
Click to collapse
glad to help. :good:
Is it possible to change dpi of one app without root?
No
please don't attempt also
pibach said:
No
Click to expand...
Click to collapse
In a bid to improve display performance of my tab S ,
I have tampered with the resolution settings using an app from playstore namely resolution changer, and now my tab S, boots up but with a bunch of failed to load........messages and i cant see anything on the screen.........
i had earlier( before this catastrophe) installed TWRP 2.8.5.0 and made a backup of my complete system....... but however now i am not able to boot into TWRP also. Links to mega.co.nz are not working , therefore unable to download stock ROM.
kindly help me with alternate solutions or working links to stock firmwares......
Only way to get out of that is reflash stock rom, afaik. Samsung GUI cannot handle different DPI and crashes, that is why app individual DPI (with root) ist required. There are a bunch of threads on that toppic...
pibach said:
Only way to get out of that is reflash stock rom, afaik. Samsung GUI cannot handle different DPI and crashes, that is why app individual DPI (with root) ist required. There are a bunch of threads on that toppic...
Click to expand...
Click to collapse
thanks, just did that and my tab is back to life
That's learning the hard way. I've gone the same route, see here : http://forum.xda-developers.com/galaxy-tab-s/general/dpi-settings-t2833667
Tried to change the DPI but doesn't work through ADB which is odd as every other android phones always worked.
Any ideas?
Edit build.prop change to dpı,
And Flash to twrp
EypCnn said:
Edit build.prop change to dpı,
And Flash to twrp
Click to expand...
Click to collapse
If he unlocked his bootloader..
solazz said:
You can lower DPI without root just need to use ADB... In developer options in the phone, enable USB debugging... Then, connect to PC and run the code below:
adb shell wm density 400 && adb shell reboot
Change 400 above to the DPI that you wanted to use...
Click to expand...
Click to collapse
This worked for me, are you sure your device is properly connected?
The Dutchman said:
This worked for me, are you sure your device is properly connected?
Click to expand...
Click to collapse
Just tried it again and it's worked. Odd. Thanks guys.
Bummer that tabletUI (DPI set to 288 or lower) makes the Notification Center to force close in a loop when restarting the system and it boots up again. It worked on first reboot but now not. Not even after a factore reset. Funny thing it works if enabling it after the system is booted. Something with their Notification Center APK does not like low DPI at startup.
Hi, What is the current screen density of the P2 and what is a good value to change to
Ta
Build.prop needed
Please help me, can you share the build.prop of the Lenovo p2? I Need it for a bug fixing try. Thanks
I changed the dpi with root essentials, works great
Sent from my Lenovo P2a42 using XDA-Developers Legacy app
Tao98 said:
Please help me, can you share the build.prop of the Lenovo p2? I Need it for a bug fixing try. Thanks
Click to expand...
Click to collapse
What's the location of the file.
kelosh said:
Hi, What is the current screen density of the P2 and what is a good value to change to
Ta
Click to expand...
Click to collapse
DPI-Calculator says 401dpi is the real density of this display. And this value looks properly to me :cyclops:.
Does anyone know how to change change dpi without having unlocked bootloader?
there is the option in settings/display/screen size
at least in nougat.
@Korax94 And if you don't have nougat you should read post 4 in this thread.
Messed myself over editing my build.prop and don't want to reboot my phone without having it in the system directory. Can anyone quickly upload their build.prop for me please? Thanks.
RegnierD said:
Messed myself over editing my build.prop and don't want to reboot my phone without having it in the system directory. Can anyone quickly upload their build.prop for me please? Thanks.
Click to expand...
Click to collapse
Sorry - I am already on September 2018 update. I can upload that build.prop - but not sure if that might cause problems on boot. Let me know.