If you tried to change your screen density and ran into gfx glitches etc, this is for you. A simple how-to change your screen DPI on a LePro 3 running EUI without messing up lockscreen clock, dialer, etc.
Firstly, the two methods I knew of with which to change screen density are as follows
- (ROOT REQ) Just changeing the sf.lcd_density value in build.prop (mostly) doesnt work at all, and doesnt affect the resolution whatsoever.
- The other method commonly used, and which doesnt require root if you have access to a computer running ADB is via shell, and using WM (window manager). This one will work, and change your DPI, but will mess up the interface. This is also the method employed by many apps on play store which require root to change your DPI, hence giving the same messy result.
Well, tonight I finally managed to make it work without any glitches, misplaced text etc, all is as it should be, and I'm running 360 DPI right now (screenshots).
Root is required (alternatively you could use TWRP to replace the file, on non rooted phones, I guess). Using a root explorer, navigate to \data\property\ and find the file named persist.sys.sf.lcd_density. Open it as a text document, all it contains is a number which is your phones native DPI
Change it to whatever you like, save and reboot.
Be warned, a TWRP backup is handy, coz a wrong setting can cause the system ui to crash on boot, leaving you dead in the water. :laugh:
Cheers, works here. My lockscreen pattern is still ****ed up, its either to the left or right, not centered, but apart from that its all good.
Is it better solution than Nova Launcher?
marik1 said:
Is it better solution than Nova Launcher?
Click to expand...
Click to collapse
What are you talking about? Thia changes your device DPI, as in everything, not just home screen
@Incogn I believe that is a feature, to ease one handed unlocking, it moves the pattern to the side of the screen on which youve swiped your finger on.
I can live with the messed up dialer for now. 300dpi is perfect for me. =D
Joms_US said:
I can live with the messed up dialer for now. 300dpi is perfect for me. =D
Click to expand...
Click to collapse
Using 380 and dialer is perfect here
Anything below 380 messes up the dialer, but nothing else. I solved that one by installing the google dialer
trizex said:
Anything below 380 messes up the dialer, but nothing else. I solved that one by installing the google dialer
Click to expand...
Click to collapse
Interesting, which version? TIA
@Joms_US did it just this morning, @Abdiel1224 posted on Turbo's thread that it was possible by downloading opengapps aroma version, then install them through TWRP, selecting just the dialer and dialer framework. Sounds simple enough, but it wasnt smooth for me at all. After flashing, once booted, app called setup wizard would FC non-stop and wouldnt let me access my launcher/or anything else. After trying numerous times different gapps flashing options, restoring my TWRP backup, then flashing all gapps, etc etc, I finally concluded it was googles setup wizard that was f*cking with me....
The way i got around it was...creative. Managed to get into my recent apps, through solid explorer was able to launch titanium backup, and then force stop/freeze the offending app (google setup wizard). Et voila, after that it worked like a charm.
To save you all the headache/legwork that I had, if you should run into the same problem I did (System wizard FC on boot), just reboot to TWRP, navigate over to System/priv-app/setupwizard/ and delete setupwizard.apk
Works for me. However, the file did not exist. I just created it and put the number in. It worked great!
What is the original dpi in le pro3. I have a rom 20s by cydras and he reduced dpi...
patryk0511 said:
What is the original dpi in le pro3. I have a rom 20s by cydras and he reduced dpi...
Click to expand...
Click to collapse
I'm pretty sure it is 420
Related
Hi if I change the density on me GS2 some apps no longer show up under downloaded to my phone. one example is Adobe Flash Player. I can find it in the market and it will say its installed but on top it says not compatible with my device. Does anyone know if there is a way to fix this.
No fix, just confirming the same thing, even when only changing from 240 to 220.
It's related to the new Market, the only fix right now is using a "supported" density such as 160 or 240.
Trying 160 now,seems to be ok. Thanks for the tip. TW launcher leaves a large dead spot under the screen indicator. Switched to Launcher Pro, looks good.
Change Reboot method to "killall" then apply... should work now.
Near disaster with this app. Checked compatability mode under settings, it rebooted but only showed splash screen, then went black. Tried rebooting, same thing. Could get into recovery and download modes, but nothing else. Odined stock kernel again, no change. Cleared data and cache, still nothing. Finally has the idea to Odin Zedomax V4.1, and got CWM. Restored a saved backup, and finally it booted. Odined the stock kernel again, use Titanium, and back to normal. Lesson learned-don't try compatability mode.
Hi, new to the forum, I tired to figure out this problem on youtube to no avail. So I have a rooted g3 with twrp. After the botting process, it takes me to the setup screen. But after getting to the point where I pick the look of the onscreen home buttons etc, the wizard crashes, I press 'OK" and it starts over. So then I found a link here about going into twrp and deleting the setupwizard.apk file which is supposed to 'fix" the problem(http://forum.xda-developers.com/showthread.php?t=2668851). Did that then I rebooted but still same issue remains. What else can be done about this?
Can't you just skip it and do it manually
Dez730 said:
Hi, new to the forum, I tired to figure out this problem on youtube to no avail. So I have a rooted g3 with twrp. After the botting process, it takes me to the setup screen. But after getting to the point where I pick the look of the onscreen home buttons etc, the wizard crashes, I press 'OK" and it starts over. So then I found a link here about going into twrp and deleting the setupwizard.apk file which is supposed to 'fix" the problem(http://forum.xda-developers.com/showthread.php?t=2668851). Did that then I rebooted but still same issue remains. What else can be done about this?
Click to expand...
Click to collapse
I had the same issue when flashing "Lonely Rom" and "Zone Rom" (come to find out my original out of the box rom crashed also if I went back into it and tried to do the set up again). 2 apks need to be deleted (4 if still odexed) LgStartUpWizard in system app folder and LgSetupWizard in priv-app folder. I edited my zip before flashing with all the updated Google equivalents plus some other stuff I normally do. The Google set up process worked like a charm and everything is running better than stock (better battery life and no noticeable lags) even though it's a "stock rom", I also run Xposed with several modules for my needs with no adverse effects here.
zoman7663 said:
I had the same issue when flashing "Lonely Rom" and "Zone Rom" (come to find out my original out of the box rom crashed also if I went back into it and tried to do the set up again). 2 apks need to be deleted (4 if still odexed) LgStartUpWizard in system app folder and LgSetupWizard in priv-app folder. I edited my zip before flashing with all the updated Google equivalents plus some other stuff I normally do. The Google set up process worked like a charm and everything is running better than stock (better battery life and no noticeable lags) even though it's a "stock rom", I also run Xposed with several modules for my needs with no adverse effects here.
Click to expand...
Click to collapse
Thanks man, lol but I unrooted back to stock an hour ago. But now I'll know what to do when I root again & have the same issue pop up
BACARDILIMON said:
Can't you just skip it and do it manually
Click to expand...
Click to collapse
Nah, the step I got to there was a 'next' or 'back'.
Similar Issue
Dez730 said:
Hi, new to the forum, I tired to figure out this problem on youtube to no avail. So I have a rooted g3 with twrp. After the botting process, it takes me to the setup screen. But after getting to the point where I pick the look of the onscreen home buttons etc, the wizard crashes, I press 'OK" and it starts over. So then I found a link here about going into twrp and deleting the setupwizard.apk file which is supposed to 'fix" the problem(http://forum.xda-developers.com/showthread.php?t=2668851). Did that then I rebooted but still same issue remains. What else can be done about this?
Click to expand...
Click to collapse
Hello,
I am new to the site, and fairly inexperienced with rooting. I used KingRoot to root my LG G3 and then did a factory reset so that I could re update to the current android version before rooting. Now I get stuck at the same point in the setup process. However, I do not have TWRP or CWM installed. What are my options?
Thanks
Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
ROADKING17 said:
Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
Click to expand...
Click to collapse
Seqrch plays tore there is tons of apps
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app
ROADKING17 said:
Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
Click to expand...
Click to collapse
If you are rooted use a file manager with an editor that has root capability (like File Manager HD) and go to /system. Make a backup copy of build.prop and then edit it to change the value of ro.sf.lcd_density from 480 to something lower, like 450, 400, or 360. I tried the latter and it worked. However the appearance of some native apps like phone or camera may become funky. IF you want everything to look normal you will have to install Xposed and do some stuff like this: http://forum.xda-developers.com/showthread.php?t=2507369
Be careful not to go too low with this value. People usually don't go below 320 because the phone may not reboot afterwards. Below 360 things are not even visible, at least for me.
najoor said:
If you are rooted use a file manager with an editor that has root capability (like File Manager HD) and go to /system. Make a backup copy of build.prop and then edit it to change the value of ro.sf.lcd_density from 480 to something lower, like 450, 400, or 360. I tried the latter and it worked. However the appearance of some native apps like phone or camera may become funky. IF you want everything to look normal you will have to install Xposed and do some stuff like this: http://forum.xda-developers.com/showthread.php?t=2507369
Be careful not to go too low with this value. People usually don't go below 320 because the phone may not reboot afterwards. Below 360 things are not even visible, at least for me.
Click to expand...
Click to collapse
Ok Thanks
ROADKING17 said:
Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
Click to expand...
Click to collapse
Before you attempt to use the guide that najoor suggested, be sure to backup your ENTIRE ROM and not just the build.prop file. Installing Xposed on many Note 3's and any TW devices for that matter, ends in disaster. Many are left in an infinite bootloop, causing you to need to wipe everything and reinstall your ROM.
ludeawakening said:
Before you attempt to use the guide that najoor suggested, be sure to backup your ENTIRE ROM and not just the build.prop file. Installing Xposed on many Note 3's and any TW devices for that matter, ends in disaster. Many are left in an infinite bootloop, causing you to need to wipe everything and reinstall your ROM.
Click to expand...
Click to collapse
I concur. I personally don't like Xposed anymore. It was fun the first few times I used it and then I realized it tends to be chaotic in the way it changes the system. In general any tool/software that changes things in an irreversible way without the user's explicit knowledge is in my opinion poorly written. I remember that when I had an ATT note 3 on Android 4.3 I rooted it and installed Xposed and some of its modules and was very content with myself. But then when the time came to upgrade to 4.4.2 the phone refused to do so because it saw my system as "altered in an unauthorized way". I unrooted it to no avail. I uninstalled Xposed and all its modules, once before and once after unrooting to no avail. Finally I sat down and started looking at the system files and Xposed had changed so many things without my knowledge that tracing all of them and reversing them took me forever. I had the luxury of using Safestrap back then to do trial and error but since there is no such thing for lollipop, if you don't have a custom recovery and you mess up, you will need to flash the ROM from scratch and lose your data in the process.
najoor said:
I concur. I personally don't like Xposed anymore. It was fun the first few times I used it and then I realized it tends to be chaotic in the way it changes the system. In general any tool/software that changes things in an irreversible way without the user's explicit knowledge is in my opinion poorly written. I remember that when I had an ATT note 3 on Android 4.3 I rooted it and installed Xposed and some of its modules and was very content with myself. But then when the time came to upgrade to 4.4.2 the phone refused to do so because it saw my system as "altered in an unauthorized way". I unrooted it to no avail. I uninstalled Xposed and all its modules, once before and once after unrooting to no avail. Finally I sat down and started looking at the system files and Xposed had changes so many things without my knowledge that tracing all of them and reversing them took me forever. I had the luxury of using Safestrap back then to do trial and error but since there is no such thing for lollipop, if you don't have a custom recovery and you mess up, you will need to flash the ROM from scratch and lose your data in the process.
Click to expand...
Click to collapse
I've never used Xposed and I never will, but I also have the resources and the knowledge to just change the stuff in the framework and SystemUI myself.
If I'm helping anyone upgrade their system, the first thing I ask is if they've installed Xposed or running a ROM that has it pre-installed. If they say yes I recommend them just starting over from scratch with OEM firmware, which is easy to do on any brand phone. You have Odin for Samsung, RSD Lite for Motorola, and fastboot for HTC to achieve this.
Okay, so...I've been searching for a good month or so on what and how to do to eventually fix this, no luck.
First of all, let me say I'm a complete noob in this stuff, and yes, i understand that I shouldn't have tampered with what I have no experience with, anyway;
I saw a thread on ported apps from the G4, and figured, "Heck, why not". Rooting and everything went smooth, until it said that I have to change the format (?) or something of the system/apps folder to something else than it already is.
That's where everything went in the wrong direction. The folder became invisible (?) and unreadable by the phone, even tho I could see it with the ES File Explorer, but couldn't with Root Browser. I tried changing the format of the system/apps folder to what it originally was and that didn't help.
So, now I have no system apps which I can use, I always get the "_____ has stopped working" notification. Bluetooth doesn't work, NFC, the remote app, can't change the lockscreen effects OR the lockscreen wallpaper, and many other apps and settings crash randomly.
The question is, can I find or get by any chance a copy of someone else's folder to copy it back to mine to fix this if it works this way. Or is the only way to fix this to flash back the stock ROM to the phone? Or perhaps is there a way to make the folder "usable" again by doing something I don't know? Any help would be appreciated.
Thanks!
Currently running Android 5.0 if that matters.
Edit: Just failed to mention that the phone is usable, not in any bootloops or whatsoever, the LG launcher is not working of course, but I somehow got the phone running with Nexus Launcher. The keyboard is the same, using Swiftkey. Yes, it's usable like this but not convenient, I need the system apps lol.
Finally figured out how to install Lineage... I think... it's installed for sure but not working. When at first startup it asked to choose a launcher, I picked PIXEL because had no idea which was which, and now I have no desktop, just the wallpaper and every 10sec the message pops up saying Pixel Launcher Keeps Stopping.
Went into the app, force stop, cleared cache and data, reboot and no change. No icons or anything so can't get into Play and download another launcher either.
Any ideas? I have 0 rooting/image/lineage type experience. My old tablet was a Nexus10 and Wugfresh did everything for me so, kinda new to this.
Thanks
THRobinson said:
Finally figured out how to install Lineage... I think... it's installed for sure but not working. When at first startup it asked to choose a launcher, I picked PIXEL because had no idea which was which, and now I have no desktop, just the wallpaper and every 10sec the message pops up saying Pixel Launcher Keeps Stopping.
Went into the app, force stop, cleared cache and data, reboot and no change. No icons or anything so can't get into Play and download another launcher either.
Any ideas? I have 0 rooting/image/lineage type experience. My old tablet was a Nexus10 and Wugfresh did everything for me so, kinda new to this.
Thanks
Click to expand...
Click to collapse
Looks like you have a strange lineageOS version. Normally there is only trebuchet launcher. You can always restart installation at the step in twrp wipe system and data.
kurtn said:
Looks like you have a strange lineageOS version. Normally there is only trebuchet launcher. You can always restart installation at the step in twrp wipe system and data.
Click to expand...
Click to collapse
I followed howtogeek.com/348545/how-to-install-lineageos-on-android (I'm too new to post links).
Maybe it's the GApps? was vague on that stuff and were like 8 options and no idea which to choose so went for the Stock version
I need to redo it again anyways... followed directions but SuperSU not working right... tablet does show rooted but when I went to install Pokemon Go, immediately says won't work on rooted devices. Stupid Niantic. Doesn't matter, I never used anything that needed Root anyways. I'm a pretty basic user. Just want the games and Chrome to work really... but ever since 7.1 downloaded to the tablet, quite a few people with the same tablet can no longer play Marvel Contest of Champions because of the insanely long load screens and lag. From what I tried so far, this fixed it.
I'll try the install of LineageOS again but leaving out SuperSU and GApps.
THRobinson said:
I followed howtogeek.com/348545/how-to-install-lineageos-on-android (I'm too new to post links).
Maybe it's the GApps? was vague on that stuff and were like 8 options and no idea which to choose so went for the Stock version
I need to redo it again anyways... followed directions but SuperSU not working right... tablet does show rooted but when I went to install Pokemon Go, immediately says won't work on rooted devices. Stupid Niantic. Doesn't matter, I never used anything that needed Root anyways. I'm a pretty basic user. Just want the games and Chrome to work really... but ever since 7.1 downloaded to the tablet, quite a few people with the same tablet can no longer play Marvel Contest of Champions because of the insanely long load screens and lag. From what I tried so far, this fixed it.
I'll try the install of LineageOS again but leaving out SuperSU and GApps.
Click to expand...
Click to collapse
There is a XDA'er playing Pokémon go without GApps. Search for @Setialpha and his nanodroid project.
kurtn said:
There is a XDA'er playing Pokémon go without GApps. Search for @Setialpha and his nanodroid project.
Click to expand...
Click to collapse
All working now... tried without GApps and didn't like it, couldn't figure out where Google app store button was etc... so redid it again, same way as before with GApps but, left out the SuperSU which is what rooted the tablet, and works fine now. Just made sure when started up, not to choose Pixel as a launcher.
Need to figure out a few things... hoping a way to switch around the clock... time in the top/left corner is weird... never had a phone/tablet where it wasn't top/right. But small issues like that... just happy that certain apps are running properly again. Have playing games on a phone, I have big hands.
One issue I can't sort out yet... when I hold down on the background I get options for home settings, widgets and wallpaper...when I click to change wallpaper it just says app not installed
THRobinson said:
All working now... tried without GApps and didn't like it, couldn't figure out where Google app store button was etc... so redid it again, same way as before with GApps but, left out the SuperSU which is what rooted the tablet, and works fine now. Just made sure when started up, not to choose Pixel as a launcher.
Need to figure out a few things... hoping a way to switch around the clock... time in the top/left corner is weird... never had a phone/tablet where it wasn't top/right. But small issues like that... just happy that certain apps are running properly again. Have playing games on a phone, I have big hands.
Click to expand...
Click to collapse
How did you get it to work all over again? I have a similar problem with no idea of how to boot my phone back in recovery mode (TWRP) and flash another GApps/ROM. I was using ADB command and honestly, I'm green on this.
Bekinson said:
How did you get it to work all over again? I have a similar problem with no idea of how to boot my phone back in recovery mode (TWRP) and flash another GApps/ROM. I was using ADB command and honestly, I'm green on this.
Click to expand...
Click to collapse
Can't recall... spent hours on this thing to make it work and now that it does I haven't touched the installer since.
Fixed
I rebooted into TWRP, copied on my computer the file "/data/system/packages.xml" edited under <package name="com.google.android.apps.nexuslauncher" ... and <perms>, I added the following lines:
<item name="android.permission.STATUS_BAR" granted="true" flags="0" />
<item name="android.permission.MANAGE_ACTIVITY_STACKS" granted="true" flags="0" />
(watch the screenshot)
saved the new xml and put back in /data/system/ with TWRP file manager... and the crash was fixed, no need to install other stuff!
wrong forum. Delete