I had to get a new phone today as my old Note2 wifi died.
The phone is already updated to 4.3 from Sprint. I rooted and if I change the DPI to 240 the Samsung Keyboard breaks. I used Xposed on 2.1 and was able to adjust the settings for each app manually. When I used TI backup to use Xposed again it killed the phone and put it into a boot loop. I'm assuming this is due to it being out of date.
I recovered and see there is a new Xposed. Does this work on 4.3 stock roms that are rooted? I really just want Nova Launcher and a few apps to be 240dpi, or the entire phone if I have too, but I want to keep using the stock keyboard.
Thanks
Related
So... I have been on a custom ROM for a while now. The ROM I have been using is great... unfortunately... I have been having constant problems on the market. Currently, I can go to the market on the web and it still lists my device from when it had the latest stock version. My issue is that now it is showing a TON of apps that are incompatible which is complete BS. I was able to get some of the APKs and had some from a titanium backup I had done previously... and they all work perfectly fine.
I did a wipe of market data and removed my account on my phone. I then rebooted, added my account, and started up the market. This fixed about half of the apps... but I still have a ton of apps showing incompatible.
To try and track down this issue... can someone post a build.prop from the latest stock build? I want to try some modifications to my build.prop to try and fix the issue. Currently, I am on the King Kang ROM (AOKP+Paranoid)
EDIT: Was able to restore my device ID from a backup from when I was running stock. I am now able to install things... though it worries me that the problem could re-occur as with its normal configuration it would prevent installation of some applications.
Goblinlord said:
So... I have been on a custom ROM for a while now. The ROM I have been using is great... unfortunately... I have been having constant problems on the market. Currently, I can go to the market on the web and it still lists my device from when it had the latest stock version. My issue is that now it is showing a TON of apps that are incompatible which is complete BS. I was able to get some of the APKs and had some from a titanium backup I had done previously... and they all work perfectly fine.
I did a wipe of market data and removed my account on my phone. I then rebooted, added my account, and started up the market. This fixed about half of the apps... but I still have a ton of apps showing incompatible.
To try and track down this issue... can someone post a build.prop from the latest stock build? I want to try some modifications to my build.prop to try and fix the issue. Currently, I am on the King Kang ROM (AOKP+Paranoid)
EDIT: Was able to restore my device ID from a backup from when I was running stock. I am now able to install things... though it worries me that the problem could re-occur as with its normal configuration it would prevent installation of some applications.
Click to expand...
Click to collapse
Did you ever change the DPI on your phone? That will make installing things from the market impossible unless you have a modded market.
Sent from my SPH-D710 using xda app-developers app
however it was set on this ROM is where it was initially and had problems. I changed with Paranoid but other than that no. After changing with Paranoid I can still DL most apps. Though... the DPI is pretty jacked immediately after flashing... its all set at like 320 default which is too large for almost anything. I have set it down to 200. Even though I still have it at 200 after restoring a device ID I can now install stuff again for now though.
Just picked up a new T-Mobile Note 2 and getting down to some rooting again, been awhile since Ive ROMd an android. Was hoping to stick to some stockish roms because i like the sammy bloatware (SNote, AllShare, Air View, SVoice, to name a few) and i would like to keep those features while running a custom rom because i also want to use Google Wallet. I was following a guide but i got stuck because I can't edit the build.prop file. I can use root explorer to open it, edit and save it, but when i open it up again, even without reboot, it reverts back to the original build.prop. Does this on rooted stock 4.1.2 and current Jedi Master 13 rom, any suggestions? thanks in advance.
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.
I used DPI changer (I thought it was set for a single reboot, but it was a persistant edit), and now touchwiz home crashes upon boot up, making it impossible to use my S4 mini. It's a verizon I435 (4.4.2 or 4.4.3) rooted with towelroot. I was wondering if there was any way to edit build.prop via my pc (as I can't flash with a locked bootloader), or is my only option to restore back to stock?
If anyone else should have this problem you can use adb on the PC and push the edited /system/build.prop (edit dpi to 240) back to teh phone.
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.