Database Users

LCD Density changer - Not saving after reboot

Hi all,
Just wondered if anyone had any joy with the LCD Density changer remembering your updated density after a reboot.
If I re-power the device, it always returns to the stock 240 despite me clicking "Save" at 180.
It's getting slightly frustrating as the reason I paid for the app was to avoid having to re-do it everytime.
Anyone had any success getting it to remember? I rooted via Z4root, so I'm not sure if it's related to this method of rooting?
Thanks in advance.
If not, can someone tell me a step by step guide on how to hard-edit the density? - Thanks!

You have to go to settings and select "Save density as system density", then go back and save again on main screen.
You see a message saying it was saved as system settings and well keep after reboot or something similar.
all the best,
Joao.

awsome
I just did the exact same thing, also using z4root Only I also pressed the physical menu button while inside the lcd density changer app --> settings --> set saved density as system density ..or something like that (I don't have my tab with me atm). I hope this was helpful

Cheers guys - sorted at last. Much appreciated.
Hope the Galaxy Tab gets some love with some custom ROMs soon. Seems the Advent Vega is getting all the attention at the moment when I feel that the Samsung, with a few tweaks and bloatware gone - could be even more impressive than it is now!
Cheers all!

also, be sure to choose the permanent root option in z4root, or else your root will disappear on reboot

Any good screenshots where you guys take advantage of a higher density on the tab? (Sorry if OT)

Mate - just edit the build.props file in the system folder using root explorer or whatever
I have mine set for 200 and theres no need to muck about with apps of any kind... literally, just change 2 letters and youre good to go:
1. Download and install Root Explorer from Android Market.
There are other file managers for root users available, but this is one I use and what the rest of this tutorial is based on.
2. Open Root Explorer on your Tab, scroll to the bottom, and tap the system folder.
3. Tap the Mount R/W button at the top of the screen to gain read-write access to the files.
4. Long press on the build.prop item in the list.
5. Select Open in Text Editor from the pop-up menu that will appear.
6. Locate the line that reads ro.sf.lcd_density = 240. Delete “240″ and input another value in its place.
7. Tap the Menu button on the Tab.
8. Tap Save & Exit from the toolbar that will appear on the bottom of the screen. A backup of the original build.prop will be created automatically.
9. Tap the Mount R/O button at the top of the screen to return to the previous read-only state.
10. Exit Root Explorer and reboot the Tab to see the changes.
11. Repeat steps 2-10 as needed. Set the density to 240 to go back to the stock DPI.

[MOD]How to get rid of the data usage reminder when Wifi is disabled

This can be done by editing build.prop in /system.
Easiest way to do this is with root explorer:
-Open root explorer and go to /system
-Mount /system as R/W
-Find build.prop and open in text editor (long press on the build.prop file to get the menu.)
-Look for line 'ro.config.hw_remindwifitopdp=true'
-Change it to 'ro.config.hw_remindwifitopdp=false'
-Save and reboot, then you are done.
Recovery .zip would be easy, but build.prop has the info on rom version etc. So it would get messed up...
If your network data is very expensive, then i would not recommend to change this...

Thanks so much! I'm sure everybody has been as glad as I am to put an end to this horrible "feature". Every time I leave my house I cease getting emails and Facebook notifications and I don't realise. I'm so used to Windows that I just press cancel on anything annoying that pops up.

This worked great, Thanks.

AmeriCanAndroid screen size issue

so i just flashed the AmeriCanAndroid rom and everything is running smoothly. the only issue is that the screen is very small. like the notification bar is so small i can hardly see it. the lock screen is a little bigger then a US stamp. i searched the original thread but there are over 1500 pages and the search function yeilded no results . so how do i fix the screen size?

The very first page of ACA thread says
"-Starting with 080111 and later, users can edit /sdcard/android/startup.txt prior to booting to adjust LCD_DENSITY, GPS_ZONE, and DATA_SIZE (data.img)
(ie: the default lcd_density of ACA is 167. Edit the lcd_density= value to 240 to get standard sized icons and fonts)"
The part you're looking for is to change the value to 240.
I do agree, its a plague to look through that thread and search ain't no help if you don't search right

RE: Wrong Section
Hi...please put this in the questions and answers section...iron fist will be on you ...here are some solutions I found by simply using the search:
You can increase the density (sort of like changing monitor resolution) on your screen by simply changing the build.prop file. This gives you more viewing area on your screen. The build.prop file contains many user variables that are editable and one of them is the LCD Density. The lower the number, the higher the resolution. The default value is 240, but by simply changing it to 200, you can increase the resolution and see more emails in your email app, more app listings in the market, more room for widget alignment, crisper graphics, and much more!
PERMANENT ROOT SOLUTION:
now that we can do perm root, you can permanently change this by modifying your build.prop file located /system/build.prop. look for ro.sf.lcd_density and modify the number and save and reboot.
Recommended value is 200, though many users like 190. If you are unsure what you like, please try TEST MODE shown below!
Please be sure to download Spare Parts from the Market, and disable Compatibility Mode in the app. This will fix many, many apps from not displaying full-screen, however there are some apps that will not re-size.
This works really well if you pair it with something like Launcher Pro or ADW.Launcher, where you have control over rows/columns and resizing widgets.
Easiest Method -- Go to Market and download one of the LCD Density apps. Search "LCD Density."
Phone-Only Method:
You can use Root Explorer, or any text editor like notepad++ or text edit.
1. Open a File Manager and locate /system/build.prop
2. Make sure "/system" is mounted as R/W (in Root Explorer, click the Mount R/W button at the top.)
2A. MAKE A BACKUP!
3. Open and Edit the file.
4. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
5. Save the file.
6. Exit and Reboot!
If you use a separate text editor, just copy the file to your SDCard, edit it there, and move it back and overwrite the original. I recommend backing up the original just-in-case.
ADB Method:
at the cmd prompt:
1. adb pull /system/build.prop
2. Go to SDK / Tools folder and open build.prop in a text editor (recommend WORDPAD for Windows).
3. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
4. Save & Exit
5. go back to cmd prompt and type: adb shell mount -o remount,rw /dev/block/mmcblk0p25 /system
6. type: adb push build.prop /system/
7. exit and reboot phone!
hope this helps you out

Or if that doesn't work, go to spare parts and uncheck "compatibility mode" then reboot phone

Pansi SMS screen size issue
I am using american android 2.3.7.
I have installed Pansi SMS application for messaging but some how it is not coming on the fullscreen of HD2. It is just capturing upper middle part of the screen Neither am i able to open the settings of Pansi SMS. Even the windows key is not working to open its setting.
How can i resolve this.
Is there any other SMS app as good as PANSI ?

[Q] CyanogenMod file manager not able to switch to root access.

CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?

RogueSly said:
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
Click to expand...
Click to collapse
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.

Nut_House said:
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Click to expand...
Click to collapse
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.

RogueSly said:
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
Click to expand...
Click to collapse
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.

If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.

Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
I've already tried installing the latest nightly version and ran a permission fix on it, but end up with the same result. I'll try clearing cache, dalvik, and then fixing again.
gharlane00 said:
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Click to expand...
Click to collapse
The file manager doesn't have any permissions in SuperSU and never asks for any since it's not in root access mode. :\

Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
Yeah, still the same result. Clearing dalvik and cache didn't work.

Just grab es file explorer.
Sent from my SPH-L720 using xda app-developers app

RogueSly said:
Yeah, still the same result. Clearing dalvik and cache didn't work.
Click to expand...
Click to collapse
same problem.
tried to install supersu, reinstall busy box on bin and xbin, fix permissions, no luck, option still greyed out.
file manager always worked for me as root, both on cm-based ROMs and aosp.
this time it is not working with the combo saberMod and matrix on N4.
(i think this is a device-independent issue)
---------- Post added at 08:20 PM ---------- Previous post was at 08:07 PM ----------
After a lot of tentatives I solved it.
I am not 100% sure of which change made it though
I think it was by using ES root manager and resetting system as R/W.
Sent from my Nexus 4 using xda app-developers app

Alternate fix
I also had the same issue and resolved it by tapping the menu button on the top left corner. when you do this, another menu button appears in the top right corner. Hit that, then settings, and choose root mode. Took me a while to figure out!!!

solved...
Installing busy box should resolve the issue...

Sorry for bumping, I have busybox and su installed, init.d support as well, but Cyanogen's File manager still cannot access root (option is grayed out). I'm on a stock Prestigio rom. It worked previously, but I reflashed firmware and now it doesn't work on this new firmware. Any thoughts?

Hi terirem and everybody,
I had this issue recently and I've managed to fix it. This is what You should do:
Short run:
Type in rooted phone terminal:
su
am start com.cyanogenmod.filemanager.ics
done
Long run:
1. Of course You need rooted phone, I've installed also BusyBox but I am not sure if it's necessary.
2. Install Terminal application
3. Install (if it's not installed yet) and run cyanogenmod file manager then minimize it by pressing home button (make sure You don't do anything else on Your phone to don't kill file manager process, it needs to be alive for 4th point)
4. I will make all commands bold for easier reading. run your terminal app and type: top -n 1 (this command will list all your running applications just once).
5. Find cyanogenmod in last "name" column, mine has name: com.cyanogenmod.filemanager.ics (if you can't find it you can try the one I had for 7th step, should probably work)
6. Type: su You will be asked to give superuser permissions to terminal, agree. Now instead of $ an # should appear, this means all commands from now on have root privilage.
7. Now we will finally rerun filemanager again with superuser permissions, type: am start com.cyanogenmod.filemanager.ics (if you had different name of filemanager just write the one you got after am start)
8. Go to cyanogenmod filemanager general settings and change access mode to root (it should be finally available, if not make sure again You typed am start with root permissions in terminal, if still doesn't work then forget about point 9).
9. Give me a beer, or actually simple thanks is enough, I need to stop drinking.

My SuperSU is kept auto-granting and system storage is kept read-written, also I cleared the every caches.
The CM file manager is still not shown a root mode to me.
I have J-rummy’s ROM toolbox as an alternative root explorer, but sometimes is less readable than CM file manager.
There is a guy forgetting to let the system storage read-written to remind him.

I did this with CM file manager - make sure you have root access not just safe mode in general settings. When you open filemanger it is granted super U access and then you can edit and save without issues

CM Dev Settings
In Dev options is Root access set to Apps and ADB?

For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode

bsevcenk said:
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
Click to expand...
Click to collapse
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).

passtim said:
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
Click to expand...
Click to collapse
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su

id74em8 said:
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
Click to expand...
Click to collapse
Apologies, but I'm no expert at these things. What is a 'systemless' SuperSU?
Is making a link as you suggest safe?

Phone goes back to huawei eRecovery

Hi there,
First of all, lemme tell what i did.
Phone model : Huawei p9 lite VNS-L31 ( Dual Sim )
I downgraded my p9lite to andriod 6.0
After that, i unlocked the bootloader, unlocked my Phone etc and installed TWRP.
Phone was still working at this point. Installed the magisk root and Phone still worked.
main reason i wanted to root is to spoof at pokemon go ( yeah it sounds silly, but it is ).
In order to make it work i had to do some stuff, heres a copy paste from the website i followed the tutorial from :
* Step 5- Download a GPS Spoofing app of your choice. I prefer GPS Joystick but I have had great success with Fake GPS Floater. HERE is a known working GPS Joystick apk from my phone to use instead of converting the app over.
Download Service Disabler
Download a root file manager. I use root explorer but I believe its a paid only app, give Root Browser a try from HERE.
Download GPS Test app from HERE
Now its time to convert your spoofing app to a system app. If you downloaded my apk open your root explorer and copy/paste the apk to /system/priv-app and select the file and change permissions to 644 (all read selected and owner write selected), skip the rest of these steps below. If you downloaded from the Play store Open up your root explorer and navigate to /data/app and find the gps spoofing app that you installed and select the entire folder and cut it to /system/priv-app. Now go into the folder that you just moved and delete everything but the apk, All odex files and folders must go. Now long press highlight the apk and change permissions of the file to 644 (all read selected and owner write selected). Back out to the folder that the apk is in and do the same but set permissions to 755 (all read, owner write, and all execute).
Next up is Service Disabler, open the app and go to the system tab, search for location, open fusedlocation and disable it (samsung owners need to do the same for Samsungfusedlocation), search again for google and select google play services, navigate down to fusedlocation and disable it.
Next open GPS Test and go to hamburger menu, AGPS and select clear only.
Reboot to recovery and select wipe, advanced, select dalvic cache and cache. swipe to wipe and then reboot. Boot up time will take a few minutes to optimize all apps.
I followed the steps verry carefully.
My Phone starts to huawei logo, it stays on the logo and it goes to the Huawei eRecovery.
any suggestions?

Restart your phone by holding power button (Hold it until it vibrates).
try this 20 times for example , till it boots into system

FunnkyHD said:
Restart your phone by holding power button (Hold it until it vibrates).
try this 20 times for example , till it boots into systen
Click to expand...
Click to collapse
Tried it, but it does not boot.

solvathus said:
Hi there,
First of all, lemme tell what i did.
Phone model : Huawei p9 lite VNS-L31 ( Dual Sim )
I downgraded my p9lite to andriod 6.0
After that, i unlocked the bootloader, unlocked my Phone etc and installed TWRP.
Phone was still working at this point. Installed the magisk root and Phone still worked.
main reason i wanted to root is to spoof at pokemon go ( yeah it sounds silly, but it is ).
In order to make it work i had to do some stuff, heres a copy paste from the website i followed the tutorial from :
* Step 5- Download a GPS Spoofing app of your choice. I prefer GPS Joystick but I have had great success with Fake GPS Floater. HERE is a known working GPS Joystick apk from my phone to use instead of converting the app over.
Download Service Disabler
Download a root file manager. I use root explorer but I believe its a paid only app, give Root Browser a try from HERE.
Download GPS Test app from HERE
Now its time to convert your spoofing app to a system app. If you downloaded my apk open your root explorer and copy/paste the apk to /system/priv-app and select the file and change permissions to 644 (all read selected and owner write selected), skip the rest of these steps below. If you downloaded from the Play store Open up your root explorer and navigate to /data/app and find the gps spoofing app that you installed and select the entire folder and cut it to /system/priv-app. Now go into the folder that you just moved and delete everything but the apk, All odex files and folders must go. Now long press highlight the apk and change permissions of the file to 644 (all read selected and owner write selected). Back out to the folder that the apk is in and do the same but set permissions to 755 (all read, owner write, and all execute).
Next up is Service Disabler, open the app and go to the system tab, search for location, open fusedlocation and disable it (samsung owners need to do the same for Samsungfusedlocation), search again for google and select google play services, navigate down to fusedlocation and disable it.
Next open GPS Test and go to hamburger menu, AGPS and select clear only.
Reboot to recovery and select wipe, advanced, select dalvic cache and cache. swipe to wipe and then reboot. Boot up time will take a few minutes to optimize all apps.
I followed the steps verry carefully.
My Phone starts to huawei logo, it stays on the logo and it goes to the Huawei eRecovery.
any suggestions?
Click to expand...
Click to collapse
As far as i noticed, on a huawei p9 lite you can't disable a system module, such the fused location module. I know, I did this mistake by myself time ago for the same purpose as yours and i did'nt find a solution. Another strange thing is that after the wipe data and th magisk reflash (reinstall) the safetynet test won't pass. That's strange..