[Q] Default PPI - LG G Flex 2

What is the default PPI for the Flex2? I changed mine early on to its native 401, but, now wanting to go back (because of update) I dont remember what the original was.
thanks.

A bump here on this, can someone who hasn't changed their DPI install texdroider_dpi from the playstore and tell me what their current DPI is? I overwrote my backup when looking for it.
thanks!

480

If you change the DPI using adb (the method to change it for non-rooted phones), will I still be able to get OTA updates? I thought editing the system partition at all will result in OTA failing (source:https://www.androidpit.com/android-5-0-lollipop-ota-update-fail)

Related

Launcher has stopped - error

I just installed LCD Density Modder Pro and changed my DPI from 160 to 120, which worked fine after rebooting. It was too small so I changed it again this time to 140, after rebooting this time I got an error saying "Unfortunately, Launcher has stopped." Everytime I click "OK" it pops up again.
I did a Factory Reset setting it NOT to restore a backup, and the error remains. I am able to get into Settings, however I am unable to launch any applications as I cannot access the desktop or applications list.
Any suggestions?
Edit: Additional info, running Latest ICS OTA March 12th - Asus Transformer TF101
This was in the app description:
BirdAPI Inc said:
Warning! Changing DPI values may cause some apps to crash or display incorrectly. Also, if you set a dpi that is incompatible with the device or OS, then it may fail to boot, and you will have to restore your OS and or build.prop file. I recommend doing a full backup of your system before using this program if you are new to changing your dpi. If your phone fails to boot, you can restore the build.prop file using adb from recovery mode. I am not responsible for any damage done to your device. Use at your own risk!
Click to expand...
Click to collapse
Try restoring just the build.prop file?
I wish that part had been highlighted in someway so I wouldn't have missed it.
I'm clearly a newbie. What is ADB and how can I access Recovery Mode to restore the "build.prop" file on my Asus Transformer TF101?
Thanks for help, I really appreciate it!
EDIT: FIXED
Woah... Fixed. I manually reinstalled the latest update: WW_epad-user-9.2.1.17. Voila DPI issue fixed.
Speedier said:
I wish that part had been highlighted in someway so I wouldn't have missed it.
I'm clearly a newbie. What is ADB and how can I access Recovery Mode to restore the "build.prop" file on my Asus Transformer TF101?
Thanks for help, I really appreciate it!
EDIT: FIXED
Woah... Fixed. I manually reinstalled the latest update: WW_epad-user-9.2.1.17. Voila DPI issue fixed.
Click to expand...
Click to collapse
Here's a good thread about ADB
http://forum.xda-developers.com/showthread.php?t=1071584&highlight=adb
Do you have CWM recovery and did you do a nandroid backup?
EDIT: Noticed it's been fixed.

[Mod] Google Play Multi DPI fixed

I have tried multiple play store fixes from around the web and seemed to receive multiple force closes and various other issues when trying to launch Google play and Google apps. So, I decided to take the time to actually fix the files for the rom that I am currently using. Therefore, if you are someone who modified the DPI of your phone manually, happens to be running the Alpha for CM9 (or are willing to try with other roms) you can download the Vending.apk and GoogleServicesFramework.apk from this thread here and see if it helps you too. I should mention that you have to Clear data on the Google Play Store after replacing the files so it can again work properly.
I know many people are going to just say "why didn't you just download LCDModderPro, since it has the market fix?" Simple answer, because I wanted to do it myself. That is one of the great things about Android, it's open source and you can modify things to meet your needs. So why did I post this if I just wanted to do it myself? Well, once it was done I figured I might as well share... below are the links if anyone finds it to be useful.
Google Play 3.5.16:
My attempt at a CWM flashable zip: http://d-h.st/L5B
The files if you just want to copy them to /system/app yourself: http://d-h.st/AhT
The original files in case something goes wrong: http://d-h.st/5FS
Google Play 3.5.19
CWM Flashable Zip: http://d-h.st/d0t
The files if you just want to copy them to /system/app yourself: http://d-h.st/JGo
Google Play 3.7.13:
CWM flashable zip: http://d-h.st/fvz
The files if you just want to copy them to /system/app yourself: http://d-h.st/GfI
I am requesting that only people more experienced try this one ^^ out. I am trying something different this time around and I only actually edited a couple of lines, literally one in both the GoogleServicesFramework.apk and one in Phonesky.apk. It has been working for me for three days now, if you have an issue or it fails to work let me know.
Don't forget to clear data for the Google Play store after installing
Do what you do bro lol
Sent from my SGH-T989 using Tapatalk 2
Why didn't you just download LCD Modder Pr..... Oh..... Nevermind....
SolsticeZero said:
Why didn't you just download LCD Modder Pr..... Oh..... Nevermind....
Click to expand...
Click to collapse
Ha! I guess that little rant wasn't totally necessary...
Thank you for sharing! I personally used LCD Modder Pro, but it's good to know another way to get it done!! Thanks again!
Good work. there is option if we dont wanna use lcd modder pro....
Thanks, works great. I like the fact that I can get Google Play working without the use of an extra application. I'll hope you keep this updated.
PlagueBoy said:
Ha! I guess that little rant wasn't totally necessary...
Click to expand...
Click to collapse
Yeah, I was just messin with ya, dude. Great work, by the way. This is a lot more convenient.
Google Play Version 3.5.19
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...
PlagueBoy said:
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...
Click to expand...
Click to collapse
Oh nice, I hope the issues will be a thing of the past so we can run custom DPI with no hassle. Thanks for the fix, its appreciated.
PlagueBoy said:
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...
Click to expand...
Click to collapse
I can confirm this. Just installed 3.5.19 running 200dpi. Cleared data and rebooted. New version shows all my apps where before "incompatible" apps would not appear. Finally done with this mod
elitrix said:
I can confirm this. Just installed 3.5.19 running 200dpi. Cleared data and rebooted. New version shows all my apps where before "incompatible" apps would not appear. Finally done with this mod
Click to expand...
Click to collapse
Yup. That is what I am seeing here as well. There should be a need to update the original post/files then. If people still want to use 3.5.16 until it is officially pushed to our phones then this will help, otherwise download 3.5.19 and you shouldn't have to worry about your DPI... as far as I can tell anyway.
I wish I would have found this before buying the LCD Density Modder Pro
Lol
Thanks for the hard work and the alternative approach to the app on the market! And thanks for the heads up about the new market
Sent from my SAMSUNG-SGH-I727 using XDA
PlagueBoy said:
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...
Click to expand...
Click to collapse
After flashing and trying different roms for a bit, I realized that Market 3.5.19 ultimately ended up having the same issues. I went ahead and updated the APK and updated the OP with the new link for the download. It is a CWM zip, don't forget to clear data after the install.
I have only tested this on CM9 and AOKP roms, it should still work on others… but I thought I should put it out there that I have only personally tested it on those two roms.
PlagueBoy said:
After flashing and trying different roms for a bit, I realized that Market 3.5.19 ultimately ended up having the same issues. I went ahead and updated the APK and updated the OP with the new link for the download. It is a CWM zip, don't forget to clear data after the install.
I have only tested this on CM9 and AOKP roms, it should still work on others… but I thought I should put it out there that I have only personally tested it on those two roms.
Click to expand...
Click to collapse
Yeah i can confirm this. 3.5.19 seemed to work for one day or so. But what ended up happening was that the apps just wouldn't show up at all. I normally use dropbox to test it but that always worked on this new market. Dolphin browser, Draw something, app quarantine wouldn't show up in a search. My phone is running sky ics 4.0.3, dpi 180.
EDIT: omg thank you! You are awesome! Thank you for doing this! You are faster with updates then LCD Density Modder pro, they are lagging it with updates. He is still running 3.5.15, amazing! You rock!
---------- Post added at 09:05 PM ---------- Previous post was at 08:37 PM ----------
I just flashed the 3.5.19 CWM flashable zip you made and it worked great! As soon as i rebooted clear the data and amazing. I cant thank you enough! Thank you
If we wanted to do it our selfs, could we extract your zip and take the files? Just wandering for future references.
Just wondering what dpi are you guys using? I tried toying with dpi values on atrix, wanted to get a reference of what the range to look for the sweet spot on the skyrocket
Also i just tried flashing and could not even make it to the boot animation. I'm running the sky ice off the latest leak.
Admittedly i wasn't sure if i was to change the DPI first, reboot, and the flash, or flash clear data then change DPI. I'm back to a nandroid backup, if someone could shed light on this it would be of great help.
Thank you
s.sharm01 said:
Just wondering what dpi are you guys using? I tried toying with dpi values on atrix, wanted to get a reference of what the range to look for the sweet spot on the skyrocket
Also i just tried flashing and could not even make it to the boot animation. I'm running the sky ice off the latest leak.
Admittedly i wasn't sure if i was to change the DPI first, reboot, and the flash, or flash clear data then change DPI. I'm back to a nandroid backup, if someone could shed light on this it would be of great help.
Thank you
Click to expand...
Click to collapse
I think, at least I found, when doing the math that the native DPI of the phone should be 207.32 and CM9/AOKP tends not to like DPI being set on an odd number, so 208 is what I have settled on. Although, as Voiid mentions he is running 180 and elitrix mentions 200, just find something that works for you!
As for your issue, I haven't been able to replicate it on my phone. You didn't clear the cache/d-cache in CWM after install did you? I have heard there are times when ICS has issues after doing so... if you did that it could be your problem. As for the proper way to do things, well, I have flashed this at many different times with different roms. I recommend clearing data in apps manager after the flash though, that way it has to resend the DPI information mimicking a first boot or launch of the Google Play store. Try downloading the files them selves, extracting them and manually copying them into the /system/apps folder in something like root explorer. Don't forget to change permissions to rw-r-r.
Voiid - I have uploaded the files in non-cwm flashable format so you can just have the modded files and the link is in the OP. However, for future reference, yes you can just extract the files from the app folder in the CWM zip and use them moving forward as updates come along.
Thanks for the reply Plague. The problem i am having seems to be with dpi modder app. I tried changing the dpi to 200, 180 and 210 and all of them sent me into a bootloop (not actually sure if it was a bootloop because the phone never got passed the samsung logo, i'm assuming it was still on). Either way i resolved the issue by using rom toolbox and changing the dpi to 200. Then i flashed the modded play store and its working great. Thank fully i am crazy about having nandroid backups so i didn't loose anything.
PlagueBoy said:
I think, at least I found, when doing the math that the native DPI of the phone should be 207.32 and CM9/AOKP tends not to like DPI being set on an odd number, so 208 is what I have settled on. Although, as Voiid mentions he is running 180 and elitrix mentions 200, just find something that works for you!
As for your issue, I haven't been able to replicate it on my phone. You didn't clear the cache/d-cache in CWM after install did you? I have heard there are times when ICS has issues after doing so... if you did that it could be your problem. As for the proper way to do things, well, I have flashed this at many different times with different roms. I recommend clearing data in apps manager after the flash though, that way it has to resend the DPI information mimicking a first boot or launch of the Google Play store. Try downloading the files them selves, extracting them and manually copying them into the /system/apps folder in something like root explorer. Don't forget to change permissions to rw-r-r.
Voiid - I have uploaded the files in non-cwm flashable format so you can just have the modded files and the link is in the OP. However, for future reference, yes you can just extract the files from the app folder in the CWM zip and use them moving forward as updates come along.
Click to expand...
Click to collapse
Thank you PlagueBoy for the answer and the help!
s.sharm01 said:
Thanks for the reply Plague. The problem i am having seems to be with dpi modder app. I tried changing the dpi to 200, 180 and 210 and all of them sent me into a bootloop (not actually sure if it was a bootloop because the phone never got passed the samsung logo, i'm assuming it was still on). Either way i resolved the issue by using rom toolbox and changing the dpi to 200. Then i flashed the modded play store and its working great. Thank fully i am crazy about having nandroid backups so i didn't loose anything.
Click to expand...
Click to collapse
Yeah I had this issue too! Changing the dpi with LCD Modder Pro caused my phone to not boot too. I am not sure why though some apps that change dpi do that on this phone. On my old phone, the HTC aria, LCD modder worked. So idk. I just use root explorer and go to /system/ open build.prop as a text (make sure the folder is writeable) and change the dpi from within that my self. The line says
ro.sf.lcd_density=240
Its like in the center of the file.
You can change that number to whatever just make sure its a feasible number.
And then save it and reboot.
But you said rom tool box works so thanks for the heads up!
Sent from SAMSUNG-SGH-I727 using awesomesauce
Will this fix works on a galaxy s i9000
Sent from my GT-I9000 using Tapatalk 2

(Help)can't open when change DPI by LCD density modder

My p6200 can't open when I change screen dpi from 160 to 170 by LCD dencity Modder How I can fix
Thank you
I had a similar thing happen to me. If you have an adb set up that works then you can pull the build.prop file onto your pc, edit it back to 160 and copy it back to your tablet and reboot. I have never been able to get adb to recognize my GT-P6210 so I had to reflash a factory rom to get things back to normal.
login to play store on computer. Install go launcher to device over network. Navigate to apps to whatever changes dpi then go 160 and below
Same thing happened to me before. My GT7+ was stuck in the black screen. Whenever I tried to switch it off, it rebooted and got stuck again.
Thank god I installed Clockworkmod (CWM) before I messed around with the LCD density. I asked my nephew to do a nandroid backup from his GT7+, so that I can restore it on my own device.
That was the only method to repair my GT7+ as far as I know. I hope you had installed CWM.

DPI Changer utility not working

Rooted my S3 successfuly but the DPI changer utility is not working, saying "Unable to read configuration file."
Is there any other way i can change the DPI to 240?
I found the LCD Density Modder on the play store, run it and changed the dpi to 240. Now it won't even boot up!
Please help. I have no other backup! Any way to change this back to whatever the default is without doing a hard reset?
I'm not sure how to fix that, but there is a thread which says never to use that utility for LCD density. You can use ROM toolbox to change the density. You should always have a nandroid backup after rooting with a custom recovery

Setting display density before startup?

Let me elaborate a bit.
I've been using the official nightly builds of CM12 for a while now and I reflash the latest build every Sunday or so. I also modify build.prop each time to set ro.sf.lcd_density=360 so I can get a nice, usable screen.
However, whenever I flash a new nightly (dirty flash, so apps stay) it reverts, and I lose my home screen layout because the density value is different. It's a bit frustrating, so I was wondering if there was a way to edit the density value from within recovery to set it back to 360 before the first startup.
Any ideas would be appreciated!
Sent from my A0001 using XDA Free mobile app
They've changed the way the ROM is flashed since Lollipop. You used to be able to edit the build.prop in the ROM zip before flashing but you can't do that anymore. So unfortunately the answer to your problem is no.
Transmitted via Bacon
I know it's not what you asked, but some other CM12 ROMs (BlissPop for sure, as that's what I'm using now) have an option for display density built into the Settings, and it survives dirty flashes just fine. HTH

Categories

Resources