Right, because like many people I couldn't live with the ridiculous DPI that LG decided to go with on this beast I used wm shell density to change it. Now, that thanks to some of the xda gods, this has become unnecessary. How do I revert that so I can just use build.prop instead? I've tried using the same command to go back to the original DPI but, unsurprisingly, this didn't work. Is there some sort of negation command? Any help would be greatly appreciated, thanks!
Posted this in the other thread but here: adb shell wm density reset && adb reboot
Sent from my LG-H810 using Tapatalk
That's awesome, cheers. changing build.prop still doesn't help with the DPI though. Still can't get lower than 530
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.
Well I'm a graphics designer. I took the phone.apk from my rom. Did some photoshop and voila. Custom dialer and all. But it won't install. I really need some help resolving this issue.
Sent from my HTC Vision using XDA App
you probably need to build it into the ROM, or boot into recovery and adb push the file into the proper place for it to work
I tried repacking it into the rom and reflashing the rom. Once done the rom didn't work properly. I didn't have google sync for my contacts or market. How can I push the file properly to replace the original?
Sent from my HTC Vision using XDA App
first backup original
adb pull /system/app/phone.apk phone.apk.bak
then push i would delete it
adb shell rm -f /system/app/phone.apk
then push the edited one
adb push /dir/to/apk/phone.apk /system/app/phone.apk
Thank you. I will try this later tonight. Ill post the outcome.
Sent from my HTC Vision using XDA App
Wanna show us a pic of how it looks. I really wanna see
Its nothing special. I changed some colors around. Added some starwars. Stuff on the buttons. I want to see the look first then a complete makeover. Ill post it soon if it works.
Sent from my HTC Vision using XDA App
couldnt get it to work.... some more instructions would help. as to how set up the adb to transfer. im not sure if im doing it right.
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
Whats going on.
How can I get past this?
Help please...
can you post the apk? attach it to the first post and we can try it out, might be that your sdk is not set up correctly or any hundred other variables
144saint said:
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
Whats going on.
How can I get past this?
Help please...
Click to expand...
Click to collapse
Since you're editing an APK, I'm pretty sure the APK needs to be signed. Check out APK Manager here: http://forum.xda-developers.com/showthread.php?t=695701. There is also a new app that allows you to sign APKs on your phone: http://forum.xda-developers.com/showthread.php?t=857450. Never tried it though.
Also, I've read elsewhere that you'll need to edit the images is the contacts.apk as well (the dialer in phone.apk is only displayed while actually on a call).
I will edit some images on the contacts.apk might take a few days. depending on how much time I get. this is first go at this so dont expect too much. Just something different to see.
The app keeps force closing after I updated to 7.1. More specifically, Wifi Calling works normally, but if I use LCD Density (220) it force closes. How can I fix this?
Sent from my HTC Vision
I take it you've run Fix Permissions already from Clockworkmod?
Yes, I have.
I think you also had the problem with Swype... edit your build.prop as described in your other thread.
Sent from my HTC Vision using XDA App
spare parts > enable compatibility mode
see if that helps.
It doesn't help. Any other methods? If not, can someone provide a thorough walkthrough of what I need to change in my system files for it to work? Wifi calling is a biggie for me!
Sent from my HTC Vision
mapheG2 said:
It doesn't help. Any other methods? If not, can someone provide a thorough walkthrough of what I need to change in my system files for it to work? Wifi calling is a biggie for me!
Sent from my HTC Vision
Click to expand...
Click to collapse
The build.prop edit did not work? Or the other suggestion above your last post?
If you want to try to edit the build.prop, open your file manager and navigate to /system folder. Scroll down to build.prop.
Long press > Open As > Text
Change this:
ro.product.model=HTC Vision
ro.product.brand=htc_wwe
To this:
ro.product.model=T-Mobile G2
ro.product.brand=tmobile
If I misunderstood and you've already tried this, then please disregard.
No, you understood me correctly. I checked the other thread and downloaded ES File Explorer and did what I was told. My build.prop files now contains all the changes that you told me to make, yet my WIFI Calling is still force closing. Any ideas from here??
mapheG2 said:
No, you understood me correctly. I checked the other thread and downloaded ES File Explorer and did what I was told. My build.prop files now contains all the changes that you told me to make, yet my WIFI Calling is still force closing. Any ideas from here??
Click to expand...
Click to collapse
Logcat please! Wifi calling should work perfectly out of the box on CM7.
I will provide you that once I get back home to my system that has ADB and everything else. For the time being, I don't know if you can find out the problem with this error message.
"The application Wi-Fi Calling (process com.android.kineto) has stopped unexpectedly. Please try again."
There is so much stuff. How am I supposed to copy and paste from the CMD terminal?
mapheG2 said:
There is so much stuff. How am I supposed to copy and paste from the CMD terminal?
Click to expand...
Click to collapse
adb logcat > logcat.txt
ctrl+c when you're done capturing data. this will dump the logcat into 'logcat.txt'. paste it into www.pastebin.com and reply back with the link.
just for kicks, i'd recommend redownloading the CM7.1 package and reflashing it. don't wipe anything, just flash it right over top of your current setup. (it's also always advised to check the md5 key to ensure your download isn't corrupt)
Ok, so I reflashed it without wiping anything and that didn't fix my problem. I'm wiping cache, fixing permissions, and reflashing the ROM now just to double check. If that doesn't work, I'll post my logcat.
Here you go: http://pastebin.com/PzsmyuCB
Hopefully you can tell me whats wrong
Anyone can help??
mapheG2 said:
There is so much stuff. How am I supposed to copy and paste from the CMD terminal?
Click to expand...
Click to collapse
Download alogcat from the market, launch it, launch wi-fi calling, pause alogcat once you get the error and save it.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
Download alogcat from the market, launch it, launch wi-fi calling, pause alogcat once you get the error and save it.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thanks, but I already provided the logcat. Could you please help me from there?
changing LCD density can cause lot of weird issue for some apps, this only happens when you change the LCD density correct?
Have you tried doing a full Superwipe+ and fresh install of CM7.1? Wifi calling has worked flawlessly for me since CM7 (with 200 density, if the changing the density seems to break stuff).
You can always do a full backup with CWM and revert to your current state if it doesn't fix it.
EfemaN said:
Have you tried doing a full Superwipe+ and fresh install of CM7.1? Wifi calling has worked flawlessly for me since CM7 (with 200 density, if the changing the density seems to break stuff).
You can always do a full backup with CWM and revert to your current state if it doesn't fix it.
Click to expand...
Click to collapse
This isn't a bad idea. Just make sure you use the SuperwipeG2+ext4 located here so that you don't lose your 4 ext partitions. This assumes you're already converted to ext 4. If not, I recommend it. It consolidates internal memory space and has been said to improve speed (slightly).
By wiping, I will lose my data on my phone, right? I don't wish to do that, because I don't like putting things back into place (icons on homescreen, widgets, etc.). Anyway I can remove the WIFI calling app and have someone upload the app for me to reinstall?
Yes, this only happens when I change LCD Density. By messing around with the build.prop file, I can now change my LCD Density WITHOUT using the LCD Density app, but still doesn't fix the problem. Wifi Calling works when I'm at the default 240 but I'm too accustomed to 220 nowadays. It worked just fine in previous CM.
And I have no clue in regards to that whole 4 ext things?
I have rooted my Tab Pro 10.1 and tried to use Root Explorer to change the lcd density to 400 in build.prop. I have changed the screen density in several other devices successfully this way. But when I rebooted my Tab Pro, there were so many system errors and fc's I couldn't even get to root Explorer to change back. I had to completely restore with Odin.
Has anyone else been able to change the lcd density successfully? Any tips or suggestions?
I've tried as well on my Tab Pro 8.4" and I'm running a rooted custom rom based on stock. Had to reinstall rom.
I don't know if the errors are related to Samsung's Magazinelauncher and if changing launchers would help, I haven't tried. I've been trying to live with Touchwiz, if I can't there's no point for me to stay on a stock(ish) rom. If I decide to use CM then I'll try changing density again, maybe even try resolution change to extend battery life.
I'm using Apex launcher, so I don't think that's it. Still working to find solutions.
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.