I updated my Droid Eris to the OS MacRom MR8 SR1. The auto-rotate feature was working fine, but then stopped working. I am using supercharger, set CPU, LauncherPro, Green Glass Keyboard, Muiu Camera, and Cache2Cache. I'm not sure if it is a problem with the Rom or an Application. I've tried rebooting and turning the auto rotation on/off. When off it goes to portrait, when on landscape. Mad props to Macrodroid for the update. 3G is superfast! Allows you to customize your launcher! Any help would be appreciated. I would like to not have to wipe and re-flash the Rom if possible as I have taken a lot of time setting it up with the apps I like.
Scoobyzsnax said:
I updated my Droid Eris to the OS MacRom MR8 SR1. The auto-rotate feature was working fine, but then stopped working. I am using supercharger, set CPU, LauncherPro, Green Glass Keyboard, Muiu Camera, and Cache2Cache. I'm not sure if it is a problem with the Rom or an Application. I've tried rebooting and turning the auto rotation on/off. When off it goes to portrait, when on landscape. Mad props to Macrodroid for the update. 3G is superfast! Allows you to customize your launcher! Any help would be appreciated. I would like to not have to wipe and re-flash the Rom if possible as I have taken a lot of time setting it up with the apps I like.
Click to expand...
Click to collapse
Not sure about the auto rotate but my first suggestion would be to get rid of set CPU. Cm has the CPU and governor adjustments built in under performance in cm settings and that long with set CPU will cause conflicts.
Sent from my ADR6300 using XDA App
Scoobyzsnax said:
I updated my Droid Eris to the OS MacRom MR8 SR1. The auto-rotate feature was working fine, but then stopped working. I am using supercharger, set CPU, LauncherPro, Green Glass Keyboard, Muiu Camera, and Cache2Cache. I'm not sure if it is a problem with the Rom or an Application. I've tried rebooting and turning the auto rotation on/off. When off it goes to portrait, when on landscape. Mad props to Macrodroid for the update. 3G is superfast! Allows you to customize your launcher! Any help would be appreciated. I would like to not have to wipe and re-flash the Rom if possible as I have taken a lot of time setting it up with the apps I like.
Click to expand...
Click to collapse
Get rid of Set CPU (use the built in CM) and kill the supercharger settings (might need to just wipe the dalvik and reflash the Rom, Launcher and KB - Your settings and such will still be in-tact). MR8 has the memory settings tied in already, so supercharger is probably hanging it up. If you want to use supercharger, you can remove the hard-coded settings from the build.prop. Shoot me a PM if you need it done, I'll make up a flash-fix for you...
If it still doesn't work, send me a Pm and let me know... I tried it on my phone and SuperCharger does cause some issues when I applied it...
wow how much ram do you have?
ro.FOREGROUND_APP_MEM=40960 = 160 mb
ro.VISIBLE_APP_MEM=40960 = 160 mb
ro.SECONDARY_SERVER_MEM=40960 = 160 mb
ro.BACKUP_APP_MEM=20480 = 80 mb
ro.HOME_APP_MEM=61440 = 240 mb
ro.HIDDEN_APP_MEM=16384 = 64 mb
ro.CONTENT_PROVIDER_MEM=61440 = 240 mb
ro.EMPTY_APP_MEM=81920 = 320 mb
Why would you want foreground apps killed with 160mb free ram?
However, I think you just have extra 0s in error
edit: To clean build.prop, you can type this command in terminal:
su
sed -i '/.*_MEM/d' /system/build.prop
Macrodroid said:
Get rid of Set CPU (use the built in CM) and kill the supercharger settings (might need to just wipe the dalvik and reflash the Rom, Launcher and KB - Your settings and such will still be in-tact). MR8 has the memory settings tied in already, so supercharger is probably hanging it up. If you want to use supercharger, you can remove the hard-coded settings from the build.prop. Shoot me a PM if you need it done, I'll make up a flash-fix for you...
If it still doesn't work, send me a Pm and let me know... I tried it on my phone and SuperCharger does cause some issues when I applied it...
Click to expand...
Click to collapse
I followed your suggestions on CPU and Supercharger and everything is running super smooth. Thanks a million!
Curious about next step?
zeppelinrox said:
wow how much ram do you have?
ro.FOREGROUND_APP_MEM=40960 = 160 mb
ro.VISIBLE_APP_MEM=40960 = 160 mb
ro.SECONDARY_SERVER_MEM=40960 = 160 mb
ro.BACKUP_APP_MEM=20480 = 80 mb
ro.HOME_APP_MEM=61440 = 240 mb
ro.HIDDEN_APP_MEM=16384 = 64 mb
ro.CONTENT_PROVIDER_MEM=61440 = 240 mb
ro.EMPTY_APP_MEM=81920 = 320 mb
Why would you want foreground apps killed with 160mb free ram?
However, I think you just have extra 0s in error
edit: To clean build.prop, you can type this command in terminal:
su
sed -i '/.*_MEM/d' /system/build.prop
Click to expand...
Click to collapse
I typed this into the emulator and a list of options came up. Was I supposed to do anything else??
Doh... forgot about mounting system as r/w
su
mount -o remount,rw /system
sed -i '/.*_MEM/d' /system/build.prop
mount -o remount,ro /system
Sent from my Milestone using Tapatalk
zeppelinrox said:
Doh... forgot about mounting system as r/w
su
mount -o remount,rw /system
sed -i '/.*_MEM/d' /system/build.prop
mount -o remount,ro /system
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
I typed the above into my phone and nothing visibly happened. Was I supposed to see anything??
Thank you again for your help. About a month ago I asked my friend if he thought he could hit my droid eris with a shotgun blast. I was going to youtube it....I hated it....because of people like you, it has actually turned out to have been a good investment. I have been suffering with 2.1 for about 1 and 1/2 years before now.
Thanks
No error = good lol
But look in build.prop to see if you have any MEM entries.
After some serious downloading and reading....I now have android commander. I can now do some modding of my own I guess? Any how build.prop has no MEM entries. Was this the goal and should I install supercharger now?
yep... letter rip
For some reason the setting won't stick. I tried loading and running the supercharger99 as advised in the help file. I made sure all of the setting were correct. I even turned off the CPU settings at boot for CM7. Lock home in memory unchecked and Compcache was not used either. I really don't need it, but your thread on it is very compelling.
Related
Hi,
Here's a SystemUI.apk which seems to fix the high cpu problem when charging on P500 CM7. Note: I only edited the graphical icon not the battery percentage.
How to install: remove SystemUI.apk and SystemUI.odex in /system/app/, push the new SystemUI.apk to /system/app/
Possible cause of the problem:
On receiving battery change intent, cmbatteryminiicon creates a handler which causes redraw on scheduled time, the problem is, it should only create the handler once, since the handler schedules itself for execution next time. Therefore, we got increased amount of handlers triggering redraw over time which causes the increased cpu usage over charging time.
Also attached is the edited CmBatteryMiniIcon.java
Note: a simple way to check your cpu load when charging is to install an app that shows your CPU load in the statusbar, e.g. SeePU. Charge your phone for 30 minutes and then check your CPU load. If your ROM has the bug, SeePU will continuously shows your CPU load as a 100% (full red color).
Note: requires mik_os' CM7 beta 6.5.1, wipe dalvik cache in recovery.
Note: added a new flashable zip: systemui-faster-animation for those who feel the new animation is too jumpy (aka slow) to test
28/05/2011 Anyone with empty battery could please test this new zip . I have change the animation timer based on current battery level but since my battery is still full I cannot see the animation from the beginning.
It should be made flashable.
Testing it now.
Nice work. Now go get you self 10 posts and post it in mik_os thread.
Sent from my LG-P500 using XDA Premium App with missing Thanks Button.
Please create flashable zip, there is another file CmBatteryMiniIcon.Java, do we need to push that files also.
Thanks.
It's quite simple without flashable zip:
1. reboot into recovery
2. connect phone to computer
3. adb shell
# cd /system/app
# rm SystemUI.*
# exit
4. adb push SystemUI.apk /system/app/
5. reboot phone
You only need to put the apk, the java file is only required if you want to compile android.
Yes, we need a flashable zip, plz create one soon, thanks!
Ok I already installed it but with root explorer but I don't recomend root explorer method.(Only for those who knows what they are doing)
Sent from my LG-P500 using XDA Premium App
eagledipesh said:
Please create flashable zip, there is another file CmBatteryMiniIcon.Java, do we need to push that files also.
Thanks.
Click to expand...
Click to collapse
No u don't its source code. For developers.
Sent from my LG-P500 using XDA Premium App
4silvertooth said:
No u don't its source code. For developers.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Ok thank you both
How do we know that currently we are having high CPU usage while charging?
Sent from my LG-P500 using Tapatalk
lekhwani said:
How do we know that currently we are having high CPU usage while charging?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Use Watchdog Lite.
Go to CPU usage in the app and you can see status bar using more than 30% CPU while charging. Sometimes it takes more than 50% as well.
Will try it now. Btw I am charging now and opened setcpu. It is showing frequencies between 320 and 600 and I am not doing anything. Does this behavior also confirm this? I am on 245/729 ondemand.
Sent from my LG-P500 using Tapatalk
Seems to have solved the high cpu. The charging animation isn't smooth anymore though, and flashes between animation frames.
A small price to pay to have the status bar use less than 1% of the cpu instead of all of it.
Thanks for this fix!
The high cpu usage doesn't start immediately but after some time of charging you can also use mini info app to check CPU usage. Setcpu just shows the clock speed and not CPU usage.
Sent from my LG-P500 using XDA Premium App
lekhwani said:
Will try it now. Btw I am charging now and opened setcpu. It is showing frequencies between 320 and 600 and I am not doing anything. Does this behavior also confirm this? I am on 245/729 ondemand.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Probably yes.i.would use android assistant though it gives a exact graph and it's easy to see what the usage is sometimes when I plug mine in it it will ride on 90% milk of aware of the bug have you told him about the fix will he be putting it in his next beta version???? if so I'll probably wait for the official fix
LG-P500 using XDA Premium App running CM7, ungaze data2sd, over clocked at 787 quadrant score 2100
nogav said:
Seems to have solved the high cpu. The charging animation isn't smooth anymore though, and flashes between animation frames.
Click to expand...
Click to collapse
In the original code, the charging animation frame is updated every 1 second, so I don't think it's supposed to be smooth.
Flashed the zip
Before flash:
After flash:
In short CPU usage reduced to 1% from 35-60%.
This is kind of a genius work.
But after rebooting my 3g is working but not showing the h sign.
Scrolling lag while charge also seems to be gone.
Will check further.
Sent from my LG-P500 using Tapatalk
lekhwani said:
How do we know that currently we are having high CPU usage while charging?
Click to expand...
Click to collapse
If you are running adb you could:
adb shell
vmstat
{ctrl-c to exit}
The id column is the one that shows idle percentage.
# vmstat
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
0 0 210600 51504 112456 9272 100 228 0 1 0 2 97 0 0
0 0 210600 51504 112456 9272 138 217 0 0 0 1 99 0 0
0 0 210600 51504 112456 9272 110 214 0 3 0 2 96 0 0
0 0 210600 51504 112456 9272 136 208 0 0 0 2 98 0 0
^C
In this example my OptT shows 1-4% CPU use (ie, 96-99% idle). So the charging cpu bug was not in effect during this demonstration.
I've de-emphasised the first line because traditionally the first line of vmstat output shows since-boot average or something, and the subsequent lines are snapshots. Dunno if it's that way in this shell (busybox?) or not but thought I'd mention it.
so maybe i was not supposed to do this but i just flashed the zip (didnt do the other steps) and now my notification bar is gone???? but it did fix the charging bug ... how can i fix??????? i saw the posted steps but then i saw the sighed zip and figured you can just use that
dislplin01 said:
so maybe i was not supposed to do this but i just flashed the zip (didnt do the other steps) and now my notification bar is gone???? but it did fix the charging bug ... how can i fix
Click to expand...
Click to collapse
I didn't test the flashable zip, so I don't know if it works or not. If your statusbar is gone then android cannot run your com.android.systemui process. You can either flash your ROM again or use adb to replace the systemui.apk
Here's my updater-script:
Code:
mount("yaffs2", "MTD", "system", "/system");
delete("/system/app/SystemUI.odex");
package_extract_dir("system", "/system");
unmount("/system");
Hmm, is this apk tied to a special version of mik's CM7 build? I use Beta 6.5. Installed with adb shell (removed SystemUI.apk and SystemUI.odex and then copied new SystemUI.apk to /system/app). I get constantly get FCs.
Will try to wipe dalvik cache and reboot again...
THE GOOD:
- V6 supercharger script is working... well the Minfree, ADJ & OOM Grouping values are anyways.
Minfree Values Before:
8192, 10240, 12288, 14336, 16384, 20480
Minfree Values After:
2048, 4096, 51200, 56320, 61440, 70400
Script says since ICS is running that ADJ values wouldn't be applied, but I'm assuming that means they wouldn't be auto applied on boot, b/c after applying the script, the values did change.
ADJ Values Before:
0, 1, 2, 4, 9, 15
ADJ Values After:
0, 4, 10, 12, 14, 15
THE NOT SO GOOD:
- Die Hard Launcher does not work yet with ICS.
- Since we are still on stock ROM, with no init.prop, script won't enable on boot by itself, you have to set Script Manager to run the 99supercharger.sh script (@ /data) on/after boot, for the values to take effect.
http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
(used option #9 1000+HP)
What does this do or what's the benefits of it? I went to that link but it doesn't explain exactly what it is or what it does? Does applying this conflict with other mods such as overclock or the ATP tweaks apk that allows you to change I/O scheduler?
demandarin said:
What does this do or what's the benefits of it? I went to that link but it doesn't explain exactly what it is or what it does? Does applying this conflict with other mods such as overclock or the ATP tweaks apk that allows you to change I/O scheduler?
Click to expand...
Click to collapse
This provides a detailed explanation of what the V6 supercharger does. It really helps a ton on RAM limited devices (I have a couple of nook colors it has made a big difference on).
At a high level it's for memory management. The only conflicts with supercharger are apps for memory management that don't work anywhere near as well anyways.
http://forum.xda-developers.com/showthread.php?t=991276
What option to run
I installed the script and have it working on my rooted prime. However i have never used this script before on any of my android devices and i was wondering what option to run for best performance on my android prime. I have searched everywhere and could not find a guide to tell me what each option means. Also, Will i have to run this each time i reboot?
Dmarsh508 said:
I installed the script and have it working on my rooted prime. However i have never used this script before on any of my android devices and i was wondering what option to run for best performance on my android prime. I have searched everywhere and could not find a guide to tell me what each option means. Also, Will i have to run this each time i reboot?
Click to expand...
Click to collapse
For me, this program worked great with my Evo which had half the memory of this and my EVO 3D. I don't really see a need for this on the TFP as of now. Maybe later if I add more a lot more apps. When I used it I went through the settings to find the right one for me. I would use it for a day and switch to another setting to see how I liked it. Also, if you put a widget on the desktop with script manager it should work on bootup.
doeboy711 said:
For me, this program worked great with my Evo which had half the memory of this and my EVO 3D. I don't really see a need for this on the TFP as of now. Maybe later if I add more a lot more apps. When I used it I went through the settings to find the right one for me. I would use it for a day and switch to another setting to see how I liked it. Also, if you put a widget on the desktop with script manager it should work on bootup.
Click to expand...
Click to collapse
i agree with this, the tfp is so beastly i havent seen the use for the minfree adjustments. but it would be nice for bulletproof launcher and OOM groupings
Closed
nickholtus said:
Hi,
I just saw this post in arc section: http://forum.xda-developers.com/showthread.php?t=1508990
This explain how to unlock the fps limit in roms.
Here a how to:
In terminal:
Adb pull /system/build.prop
Then open build.prop with notepad++ and add this line in the button of the file:
debug.gr.swapinterval=0
Then save the file. (TIP: Make a Copy of the original build.prop file!)
And in ADB type:
Adb push build.prop /system/
And that is it!!
Please test it and report back!
Click to expand...
Click to collapse
or:
Code:
adb remount
adb shell
echo "debug.gr.swapinterval=0" >> /system/build.prop
reboot
This is going in next DFR release, 3.1.1
i tested it on my play.
and i get a fps of 65 (with doomkernel v10)
and with doomkernel v11 78FPS!!!
nickholtus said:
i tested it on my play.
and i get a fps of 65 (with doomkernel v10)
and with doomkernel v11 78FPS!!!
Click to expand...
Click to collapse
Does your screen not glitch a bit?
nickholtus said:
i tested it on my play.
and i get a fps of 65 (with doomkernel v10)
and with doomkernel v11 78FPS!!!
Click to expand...
Click to collapse
On which game/app do you get those fps??
also is there any app like fraps for pc to print fps on screen??
Thanks nickholtus!
i am using quadrant standard for this..
no i don´t have any glitches.
if you get some i will try to fix that
Look at this:
FXP said:
hy
fps is limited to 60 fps due to hawdware (display)
any fps higher than this is not in syn with diaplay and can create artifacts
Click to expand...
Click to collapse
nickholtus said:
i am using quadrant standard for this..
no i don´t have any glitches.
if you get some i will try to fix that
Click to expand...
Click to collapse
Using dualboot kernel here and I have bad frameskipping issues.
Regarding this, the device cannot truly run at more than 60fps (we have a 60Hz screen) so what will happen if you got 120 fps then you will only see 60 of the 120 frames, 60 will be skipped, so you still get the same viewable framerate
Keiran
Would it work to edit build.prop directly, with ES File manager Text editor ?
Excellent work Nick, thanks for this
homeworlder said:
Would it work to edit build.prop directly, with ES File manager Text editor ?
Click to expand...
Click to collapse
Yes that would work (don't forget to reboot after)
Atarii said:
Excellent work Nick, thanks for this
Yes that would work (don't forget to reboot after)
Click to expand...
Click to collapse
Do you mind explaining steps on what to do through the phone with terminal. I just want to make sure i am doing this right.
Thanks!
ps3l3ader said:
Do you mind explaining steps on what to do through the phone with terminal. I just want to make sure i am doing this right.
Thanks!
Click to expand...
Click to collapse
Open up a command prompt which can run adb then:
Code:
adb remount
adb shell copy /system/build.prop /system/build.prop.bak
adb shell echo "debug.gr.swapinterval=0" >> /system/build.prop
adb reboot
The phone should reboot and change be made
KeiranFTW said:
Using dualboot kernel here and I have bad frameskipping issues.
Regarding this, the device cannot truly run at more than 60fps (we have a 60Hz screen) so what will happen if you got 120 fps then you will only see 60 of the 120 frames, 60 will be skipped, so you still get the same viewable framerate
Keiran
Click to expand...
Click to collapse
So let's say if we're using the device, and the homescreen looks like it's running at about 30FPS (I kinda got an eye for 30 vs 60), would using this tweak give it a jump in speed or just remove the limit cap only? I know what you mean by only getting 60FPS because of using a 60Hz screen. Just a thought.
Swap interval usually means v-sync for computers but since this is a phone, I'm not sure why the refresh rate would be halved for 30 fps...
I'll have to test this out later.
CrimsonKnight13 said:
Swap interval usually means v-sync for computers but since this is a phone, I'm not sure why the refresh rate would be halved for 30 fps...
I'll have to test this out later.
Click to expand...
Click to collapse
If you were replying to what I said, I didn't mean the count being split in half in that way. Some launchers are heavier than others, so maybe if using a launcher with many widgets, causing framedrop, vs using Launcher7 or Zeam which are very lightweight.
CrimsonKnight13 said:
Swap interval usually means v-sync for computers but since this is a phone, I'm not sure why the refresh rate would be halved for 30 fps...
I'll have to test this out later.
Click to expand...
Click to collapse
You can enable vsync too, but I think most custom kernels don't contain the stuff to do it
It has really bugged out my screen, disabled it for now. If you are epileptic don't touch this
Sent from my R800i using DFR3.0.5 NAND + CM7 SELFKANG SD
Selim873 said:
If you were replying to what I said, I didn't mean the count being split in half in that way. Some launchers are heavier than others, so maybe if using a launcher with many widgets, causing framedrop, vs using Launcher7 or Zeam which are very lightweight.
Click to expand...
Click to collapse
Makes sense. I was just brainstorming.
KeiranFTW said:
You can enable vsync too, but I think most custom kernels don't contain the stuff to do it
It has really bugged out my screen, disabled it for now. If you are epileptic don't touch this
Click to expand...
Click to collapse
I have other GPU & UI tweaks built into build.prop. I'm curious to see how well all of them work together.
all these "tweaks"/"hacks" are useless for daily use...
i dont think we need Unlock FPS for Xperia 2011... we have 60 FPS limit which is fine as the UI is smooth...
these hacks are useful on devices like Xperia X10 where there is 30 FPS cap...
this has all been tested way back (almost a year back) and will just cause TONS of artifacts even with small things like menu scrolling...
Ref: http://forum.xda-developers.com/sho...&highlight=debug+gr+swapinterval#post13644591
the only use is to show high benchmark numbers
Oh boy. This is very cofusing with bubble shoot :3
so its like frameskipping since the screen is a 60hz screen and cant except anymore than 60fps sounds like a waste of time
SAUROM with build.prop tweaks, nothing else flashed through CWM
Hi I noticed that when over about 525mb or RAM usage on our device it starts to increase launcher lag and general lag across:
GO Launcher
ADW Launcher
TW Launcher
I tried different CPU governers:
Smartass2
Ondemand
Power Save (dur dur dur)
And right after I turn it on within 5 mins this is my RAM:
http://www.box.com/s/65b898b945607334c5b5
http://www.box.com/s/6cc0ab0a29bd003e9dc6
Can I reduce the amount of memory the apps marked with RED use?
Can I remove the ones circled in GREEN safely by deleting the apk?
How much memory do we want to keep free at all times?
Thanks in advance!
fixed 2nd link sry
zeppelinrox who makes scripts told me to use less dalvik heap size and i tried it,,are phones are 128mb,,,i turned mine down to 64mb and it seems to run alot more smoother now,,,I've noticed both roms have 128mb which is too much and not needed for this device..That's why i keep my stock with only a overclocked kernel and just add my own build prop tweaks....
wish777 said:
zeppelinrox who makes scripts told me to use less dalvik heap size and i tried it,,are phones are 128mb,,,i turned mine down to 64mb and it seems to run alot more smoother now,,,I've noticed both roms have 128mb which is too much and not needed for this device..That's why i keep my stock with only a overclocked kernel and just add my own build prop tweaks....
Click to expand...
Click to collapse
Thanks for the response. I will look for an app that can help me modify this and post back if it uses less memory.
memory optimizer root works for adjusting more aggressive settings it free too....
wish777 said:
memory optimizer root works for adjusting more aggressive settings it free too....
Click to expand...
Click to collapse
i just checked it out but actually going to roll with RAM Manager Free or RAM Manager Pro seems awesome, thanks for your help as you were the only one that replied lol.
CM12.1 support DPI adjustment natively (if you see some apps still show bigger font, then try modify the build.prop to same value, this may help.)
========================
B320/B322 update screwed up below DPI adjustment. Thanks @medwatt testing, see #45 for details. For values like 240 or 260, the phone is completely blank, and if you do 'adb shell logcat *:E', you can see the resource not found error all over the place.
========================
Edit on July 3, 2015:
On Lollipop B309, the ro.sf.lcd_density is in build.prop already and set to 320, we can change it to smaller value: (make a backup first)
Code:
ro.sf.lcd_density=240
you can use any number between 240 to 320. Save then reboot. (Thanks @ArkAngel06 point out this entry still works)
Then everything is working fine. No expose needed and didn't see any big problem so far.
One problem we noticed is stock 'Browser' app FC, pls use your favorate 3rd party browser instead. (The one i currently use is boat browser)
========================
Following is original post for JellyBean 4.3
===Normal disclaims applies, be careful and know how to use adb to restore /system/build.prop before you try this=============
You phone may brick if this file got corrupted.
ROOT is required to change the LCD density.
Today trying to play around the DPI of display, and noticed the stock value is 320:
Code:
getprop | grep dens
[ro.sf.lcd_density]: [320]
But our 720p display native DPI is 240. That's why all the stuff display so big??
Anyway, I backed up /system/build.prop, and play a little bit.
I recommend simply use Root Browser with "RB Text Editor" to do the task. Other DPI changer app may work and convenient, but it is more risky and may do some change unknown to the phone. Due to lack of backup/restore recovery right now, I prefer manually editing the file myself.
Adding following to the end of /system/build.prop.
Code:
ro.sf.lcd_density=264
For some different varies like Consumer Cellular version, or MT2L05 version, you can try following if above doesn't work:
qemu.sf.lcd_density=264
Not sure it is a bug or what, when I use ES file explorer to edit the file, If I select edit mode right after open the file, it won't scroll to the end of file. I have to scroll to the end first in view mode, then select edit mode. Anyway, Root Browser editor works without any problem.
Following is some test result:
Code:
______________ System UI________ Settings__________ Gallery
180__________force close
200______________ok____________ force close______ force close
220______________ok____________ force close______ force close
240(native)______ok____________ force close______ force close
260______________ok____________ force close______ force close
264______________ok________________ ok____________force close
280______________ok________________ ok____________force close
320(stock)______ ok________________ ok________________ ok
Also, for all DPI less than 320, the stock lock screen shortcut is not displayed properly.
I think I will stick with 280 (update, now I am using 264) for a few days and see if I found more problems. And it should be easy to find an alternative gallery app.
The smaller font and everything actually make the display more clear and sharp
PS. I know there is font size in display settings, but the DPI change will make system zoom everything based on this new display density.
Thanks aragon257 and others feedback, some info from below is collected from the replies. Thanks.
MORE INFO/UPDATE:
. There is Exposed framework modules (like app settings) to do per app DPI settings. Please see end of this post for more info.
. The app force closing caused by lower DPI is purely software (view layout arrangement) issue, so lowering DPI will not do any harm to hardware.
. List of Apps that Force Close. I list them from higher DPI to lower DPI, The apps that crashes in higher DPI will also crash in lower DPI.
DPI 264 or 280: Currently I am using 264.
Lock Screen: No crash here. The app short cut moved to center of the circle, and requires less distance swipe to unlock.
Gallery (Also affecting camera since it start Gallery when you view pictures)
Alternative: "Galleray KK" and "Camera KK" from play store works pretty good, though it is Ads supported.
DPI 240:
Settings
Phone app when receiving calls.
Use Xposed Framework
OK, set DPI to 240 in build.prop, I need use Xposed module "App Settings" to set following App DPI to higher value to make the phone fully work:
Code:
Gallery(com.android.gallery3d): 297 (dp: 320x480)
Phone(com.android.phone): 264
Settings(com.android.settings): 264
SystemUI(com.android.systemui): 264
This number is set to lowest possible value, of course you can set to 320, then related apps will be bigger.
Please see attachment for some screenshot: (Left is stock 320 DPI, right is 264 DPI)
Thanks for doing all the research here
Use xposed and install app settings. Use it to give those apps that crash the default DPI. Just tried working great. And thanks about the tip of adb build.prop backing up.
Running at 240 DPI here.
Edit: Play store wouldn't download anything until I cleared the cache.
Edit again: Actually viewing images and trying to use the camera causes the gallery to crash... Ill fix it
FINAL Edit: Installed the kitkat camera and gallery. I had to unisntall the old gallery first. This works for me
Great, that xposed module is pretty cool, but for now I must resist as we don't have recovery yet
BTW, I have updated first post to correct the System UI FC number, it is 180, not 220. ie, DPI can be as low as 200 and the phone is still usable. So, native 240 is a pretty safe value.
Also, the "Huawei home" FC start showing up from 220 and below, though I am using Nova launcher.
Cheers.
I was having problems with incoming calls crashing the phone app. So back to 320, but using App Settings to change my downloaded apps to 240
Admired by this thread:
http://forum.xda-developers.com/galaxy-nexus/general/info-official-galaxy-nexus-lcd-density-t1392089
Call me bored, today I have tried more DPIs, and found 264 is the lowest number that Settings is working. Since the crashing is just cause by GUI view arrangement issue, nothing to do with hardware etc. So I will stick with 264 for now.
For the past few days with settings 280, I only noticed gallery is the problem. I didn't try too much widget/apps. Everything else I tried works pretty good.
Please refresh my memory, is lowering the DPI making the image smaller? If so, im interested.
yes, everything (font,icon,layout)will be smaller. but image actually maybe different story. try and see yourself!
so what apps are better in tablet mode for me to try?
Bobvark said:
so what apps are better in tablet mode for me to try?
Click to expand...
Click to collapse
I didn't use any particular tablet mode etc stuff, the lower DPI gives me more space asset, thats all.
xordos said:
I didn't use any particular tablet mode etc stuff, the lower DPI gives me more space asset, thats all.
Click to expand...
Click to collapse
ok, so Chrome, gmail, what would be good DPI for those? I'm a little worried about f'n up my phone and don't just want to do trial and error.
Is 240 the standard you all are using?
Bobvark said:
ok, so Chrome, gmail, what would be good DPI for those? I'm a little worried about f'n up my phone and don't just want to do trial and error.
Is 240 the standard you all are using?
Click to expand...
Click to collapse
264 or 280 should be safer. 240 the settings app wont work.
Added some screenshot to the 1st post.
I wanna mess with this later
aragon257 said:
I was having problems with incoming calls crashing the phone app. So back to 320, but using App Settings to change my downloaded apps to 240
Click to expand...
Click to collapse
ok, now with a twrp backup taken, I installed xposed and now i got exact same problem. 240 is really sweet dpi, even the lock screen layout is good.
I tried complete delete phone.apk, and contacts.apk, but looks like not easy to find a good replacement. other dialer app from play store still requires these two apks. And i checked my other phone 4.3 rom, they force close. will continue to the search.
Have you tried it with the xposed programs? I know it worked for gallery but not sure for settings.
oncouch1 said:
Have you tried it with the xposed programs? I know it worked for gallery but not sure for settings.
Click to expand...
Click to collapse
Thanks. Didn't try gallery with app settings module yet. For 240 dpi, call out/in problem is what I am focused on right now.
Was trying app settings with 240, I set phone dialer etc. at stock setting but forgot had face lock so when I restarted, crash due to camera (what a [email protected]!) Thank you guys for TWRP so I could restore! . On vacation and no PC to try and adb to modify build.prop.
Sent from my MT2L03 using XDA Free mobile app
xordos said:
Thanks. Didn't try gallery with app settings module yet. For 240 dpi, call out/in problem is what I am focused on right now.
Click to expand...
Click to collapse
yes, with exposed module, at 240 dpi, gallery/camera works fine, settings also worked, only phone app still FC. so now i am at 264, and use exposed to fix gallery.
Silly question, app settings didn't work on dialer?
oncouch1 said:
Silly question, app settings didn't work on dialer?
Click to expand...
Click to collapse
when calls come in, phone apps FC when dpi is 240 ( and app settings use 320 for com.android.phone)
EDIT:
OK, Maybe this defeat the purpose, set SystemUI to 264 resolve the incoming call problem. The incoming call crashed the phone app because the StatusBar trying to get a phone icon resource but failed.
To summary, In build.prop DPI set to 240, I need use Xposed "App Settings" to set following App DPI to higher value to make the phone fully work:
Code:
Gallery(com.android.gallery3d): 297
Phone(com.android.phone): 264
Settings(com.android.settings): 264
SystemUI(com.android.systemui): 264
This number is set to lowest possible value, of course you can set to 320, then related apps will be bigger.