Related
Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
shyv said:
Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
Click to expand...
Click to collapse
Running 200 here on cm 7 with no problems
shyv said:
Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
Click to expand...
Click to collapse
In the build.prop, next to the line qemu.sf.lcd_density=200, there's a command on something called debug.fb.rgb565=0, try deleting it.. i remember last time, when i haven't delete it, causes me some graphical issues.
SAPPH1RE said:
In the build.prop, next to the line qemu.sf.lcd_density=200, there's a command on something called debug.fb.rgb565=0, try deleting it.. i remember last time, when i haven't delete it, causes me some graphical issues.
Click to expand...
Click to collapse
well, I just tried it with having this line deleted. My phone got stuck in bootloop then :/
(Note: I had to push the build.prop with ADB on my phone, first I tried to do it on my phone with RootExplorer, I dont know why it didnt work then. I could change the file, but after reboot it was set back to normal again.)
Edit: OK maybe I just made something wrong, I did it again with the RootExplorer method, and the line "debug.fb.rgb565=0" is now gone, but i left the space there. Still no improvements, density is on 200 now Might it be CM7 that I'm using?
shyv said:
well, I just tried it with having this line deleted. My phone got stuck in bootloop then :/
(Note: I had to push the build.prop with ADB on my phone, first I tried to do it on my phone with RootExplorer, I dont know why it didnt work then. I could change the file, but after reboot it was set back to normal again.)
Edit: OK maybe I just made something wrong, I did it again with the RootExplorer method, and the line "debug.fb.rgb565=0" is now gone, but i left the space there. Still no improvements, density is on 200 now Might it be CM7 that I'm using?
Click to expand...
Click to collapse
Which CM7 did you use? Mine on signature, works great all the time.. Well, when i remember the first time i tinkering with lcd density, i tried 160 instead.. The font was so small, my homescreen looks empty enough.. Looks good, but i had some horizontal line on menu.. Increase the lcd density to 200 resolve the problem while still maintaining to look good.. No fuzzy or blurred..
Maybe yours it's no compatible to 200 like mine on 160.. Maybe the hardware itself, i don't know.. Try 210, or 220..
edit: Could u post the pic of the aforementioned prob?
I am using CM7 build #25. The launcher and apps are okie except gameloft games where they don't show in fullscreen mode :| is there any walkaround for them?
lpachuong said:
I am using CM7 build #25. The launcher and apps are okie except gameloft games where they don't show in fullscreen mode :| is there any walkaround for them?
Click to expand...
Click to collapse
Open spare parts apps (if you don't have, try searching the market), untick compatiblity mode, and reboots.. That should fix any app that didn't run fullscreen..
SAPPH1RE said:
Which CM7 did you use? Mine on signature, works great all the time.. Well, when i remember the first time i tinkering with lcd density, i tried 160 instead.. The font was so small, my homescreen looks empty enough.. Looks good, but i had some horizontal line on menu.. Increase the lcd density to 200 resolve the problem while still maintaining to look good.. No fuzzy or blurred..
Maybe yours it's no compatible to 200 like mine on 160.. Maybe the hardware itself, i don't know.. Try 210, or 220..
edit: Could u post the pic of the aforementioned prob?
Click to expand...
Click to collapse
It seems like my device is just compatible to 240 dpi, my phone is not even trying to resize that stuff, the lower I set the dpi the more it gets "unclear".
(The funny thing is, that on the stock rom, everything looks very nice and small. must be something related to the whole roms)
shyv said:
It seems like my device is just compatible to 240 dpi, my phone is not even trying to resize that stuff, the lower I set the dpi the more it gets "unclear".
(The funny thing is, that on the stock rom, everything looks very nice and small. must be something related to the whole roms)
Click to expand...
Click to collapse
Hmm, weird.. Try flashing other CM7..
SAPPH1RE said:
Open spare parts apps (if you don't have, try searching the market), untick compatiblity mode, and reboots.. That should fix any app that didn't run fullscreen..
Click to expand...
Click to collapse
Thx man
I have changed my density to 190 with LCD Density app and everything looks great.
But I have an issue, everytime I reboot my phone it goes back to 240. Then I have to use LCD Density once again and reboot to get back at 190.
Is there a solution to get around this problem?
I´m using latest CM7 nightly build #30.
snowmer said:
I have changed my density to 190 with LCD Density app and everything looks great.
But I have an issue, everytime I reboot my phone it goes back to 240. Then I have to use LCD Density once again and reboot to get back at 190.
Is there a solution to get around this problem?
I´m using latest CM7 nightly build #30.
Click to expand...
Click to collapse
I tried it once and same result for me.
Just use rootexplorer to edit the file and change the density.
Or use adb to "pull" then modify the file and "push" it back:
adb pull /system/build.prop
modify with txt editor
adb push build.prop /system/
Next time use 7zip to modify the files before flashing the ROM.
I alway modify /system/build.prop for the lcd size and /system/etc/gps.conf for time servers before flashing.
truc007 said:
I tried it once and same result for me.
Just use rootexplorer to edit the file and change the density.
Or use adb to "pull" then modify the file and "push" it back:
adb pull /system/build.prop
modify with txt editor
adb push build.prop /system/
Next time use 7zip to modify the files before flashing the ROM.
I alway modify /system/build.prop for the lcd size and /system/etc/gps.conf for time servers before flashing.
Click to expand...
Click to collapse
thanks.
but im not sure how to use adb.
i only get failed cannot write file.
I will go on with the second solution and modify the zip file before flashing the next CM7.
Thanks for your help again.
snowmer said:
I will go on with the second solution and modify the zip file before flashing the next CM7.
Thanks for your help again.
Click to expand...
Click to collapse
Really, this is very easy to do on the phone, without any extra applications. Just use a file explorer with root access (like root explorer), navigate to /system/, open your build.prop file, modify the density line (ro.sf.lcd_density=xxx) to whatever you want and reboot. 190 is working nicely for me (nightly 30/CleanDHD).
snowmer said:
thanks.
but im not sure how to use adb.
i only get failed cannot write file.
Click to expand...
Click to collapse
Sorry, forgot this.
Just type "adb remount" to mount the system in Read/Write instead of ReadOnly
If you're under linux you may need sudo (but don't think so as under w7 you don't need admin...)
I dont see any improvement by changing it to 200 its only bad look now, I will change it back to 240.
And what improvements it should give me, by changing to lower density?
Sent from my Desire HD using XDA Premium App
s2 density at 200 not booting
please assist my s2 is not booting after changing to 200 with lcd density changer on a rooted s2. heeeeeeelp
Well, As every1 knows HDPI Roms Wont work on Wildfires, But Theres some root apps that let u change ur resolution would that help them to work?
J I M said:
Well, As every1 knows HDPI Roms Wont work on Wildfires, But Theres some root apps that let u change ur resolution would that help them to work?
Click to expand...
Click to collapse
The problem is hdpi is well above our miserable 120 (I don't know the exact number between 2-300 I think, but as it higher there's a lot more leverage for changing it on hdpi) if you change it to a much higher number on a low res screen nothing will fit on the screen.
The apps allow you to change the density software side, but on the hardware side you'll still have a low res screen.
Sent from my HTC Wildfire using xda premium
Yep, the apps there just change the DPI of the device.
If you would want to get HDPI, you would need a DPI setting of around 200 DPI (look at the pic I attached) and I think that you would't really be able to see much on the screen at that DPI level.
Hey guys.
I'm quite desperate here.
I have a rooted LG G3s and recently I tried to change the DPI without really knowing what I did. I used texdroider and changed to around 640 dpi.. which is way to high for the actual phone. Now I can't enter my phone because the screen is to big.. and it only shows the upper top of the screen?
what can I do? I'm not really good at programming and commands.. So a walktrough would be very much appreciated..
Kind regards
Nekodemus
Pull the build.prop via adb, edit it manually to any value above 540 and then push the file back with the correct permissions and you'll be good.
If you don't know how to do the above a quick Google search will help you out- I'm commuting at the moment so I'm afraid I can't be anymore help!
Nekodemus said:
Hey guys.
I'm quite desperate here.
I have a rooted LG G3s and recently I tried to change the DPI without really knowing what I did. I used texdroider and changed to around 640 dpi.. which is way to high for the actual phone. Now I can't enter my phone because the screen is to big.. and it only shows the upper top of the screen?
what can I do? I'm not really good at programming and commands.. So a walktrough would be very much appreciated..
Kind regards
Nekodemus
Click to expand...
Click to collapse
640 is defaut value..
I've been through the build.prop extremely thoroughly but can't find even a mention of the LCD density. Anybody have any luck with changing their DPI?
Had the same problem and also no luck with different apps. But "Le DPI changer" works for me.
noisyriver said:
Had the same problem and also no luck with different apps. But "Le DPI changer" works for me.
Click to expand...
Click to collapse
Just tried it, and no luck it won't work...
You have to be rooted, but I assume you are as you tried to change the build.prop. And you need to reboot after the change.
You can change dpi in adb without root. I'm kind of busy right now but it's easy to find on Google
Sent from my Moto Z Play using XDA Labs
noisyriver said:
You have to be rooted, but I assume you are as you tried to change the build.prop. And you need to reboot after the change.
Click to expand...
Click to collapse
Correct, phone is rooted. The problem is ro.sf.lcd_density isn't present anywhere in the build prop to edit. I've been setting my DPI this way on all my past phones and tablets, this time it's just not there for me to edit
HTML:
Hello Good Day everyone.
I am pleased to announced that you can tweak some Android settings without root permissions Yay. Someone can try other phones but this works on my xiaomi mi A3 and A1. BOTH of my phones are not rooted neither are they unlocked. I borrowed my friends J7 prime and got some working there too. Your mileage may vary. It should work the same on most phones. I tried some stuff and this is my findings. Some tweaks require that you Write secure settings through adb. I am not taking responsibility if you try and you damage your phone. Do this at your own risk. Thank you.
NB
If you delete the app or uninstall you lose all your settings.
If you do want to undo changes just delete setting line.
For best user experience use all working tweaks. Or you can choose what you want or do not want it is up to you. Your mileage still may vary.
OTA UPDATES don't affect settings on my phone neither do they conflict with manufacturers settings. There are some new settings line enabled on android properties that made some of my added tweaks on system tables redundant so I just deleted those redundant ones from system table. Will do some further investigating YOU can always COMPARE android properties with the tweaks you are adding to see if you are adding redundant comands. Android is forever improving, rooting is becoming obsolete, for the not pickers, a lot of these tweaks may not be necessary in the future because android might have them as standard but until then this is necessary to get the best out of your phone or to get the things you want and not what Google gives you. Thank you
LETS BEGIN
https://youtu.be/I1EBwRBQAgw
1. Download database editor
https://play.google.com/store/apps/details?id=by4a.setedit22
2. Open settings database editor select system table.
3. Add new settings "ro.config.hw_quickpoweron" >save changes> value at "true"> save changes
Add new Setting "boot.fps" > save changes > value at "25" > save changes
Add new settings > "debug.sf.nobootanimation">save changes> value at "1" >save changes.
4. Reboot phone.
Enjoy faster boot.
You can try other working tweaks below:
1. Display density
display_density_forced "209" trust me on this for mi a3 IDK why but it does. For other phones add whatever you are comfortable with or is recommended.
2.Ring without delay
ring.delay "0"
3.Faster boot under 10 seconds.
boot.fps "25" range from 15 to 30 depending on how fast your processor is.
debug.sf.nobootanimation "1"
4.wifi scan interval
wifi.supplicant_scan_interval "120" increases time between WiFi scans, saves battery and CPU power.
5.power savings
pm.sleep_mode "1"
power_supply.wakeup "enable"
6.Gaming/3d performance.
debug.enabletr "true"
debug.qctwa.preservebuf "1"
dev.pm.dyn_samplingrate "1"
video.accelerate.hw "1"
debug.overlayui.enable "1"
debug.egl.hw "1"
Debug.egl.prifiler "1"
debug.sf.hw "1"
debug.composition.type "c2d"
debug.composition.type "gpu"
debug.performance.tuning "1"
7. Better navigation scrolling speed
windowsmgr.max_events_per_sec "100"
8. Disable fingerprint reader animation.
fod_animation_type "4"
9.disable logcat
Logcat.live "disable"
10. Enhance Sound quality
af.resampler.quality "255"
mpq.audio.decode "true"
11. Internet browsing and download.
net.tcp.buffersize.default "4096,87380,256960,4096, 16384,256960"
net.tcp.buffersize.wifi "4096,87380,256960,4096,163 84,256960"
net.tcp.buffersize.umts "4096,87380,256960,4096,163 84,256960"
net.tcp.buffersize.gprs "4096,87380,256960,4096,163 84,256960"
net.tcp.buffersize.edge "4096,87380,256960,4096,163 84,256960"
net.tcp.buffersize.hspa "6144,87380,524288,6144,163 84,262144"
net.tcp.buffersize.lte "524288,1048576,2097152,5242 88,1048576,2097152
net.tcp.buffersize.hsdpa "6144,87380,1048576,6144,8 7380,1048576"
net.tcp.buffersize.evdo_b "6144,87380,1048576,6144, 87380,1048576"
net.rmnet0.dns1 "8.8.8.8"
net.rmnet0.dns2 "8.8.4.4"
net.dns1 "8.8.8.8"
net.dns2 "8.8.4.4"
net.ppp0.dns1 "8.8.8.8"
net.ppp0.dns2 "8.8.4.4"
net.wlan0.dns1 "8.8.8.8"
net.wlan0.dns2 "8.8.4.4"
net.eth0.dns1 "8.8.8.8"
net.eth0.dns2 "8.8.4.4"
net.gprs.dns1 "8.8.8.8"
net.gprs.dns2 "8.8.4.4"
Note
You can use whAtever dns is faster for u for example cloud share dns1 1.1.1.1 dns2 1.0.0.1
12.Enable GPU Acceleration (avoid enabling this in developer mode it resets when phone restarts)
debug.qc.hardware "true"
debug.qctwa.statusbar "1"
debug.qctwa.preservebuf "1"
debug.composition.type "gpu"
hw3d.force "1"
hwui.render_dirty_regions "false"
hwui.disable_vsync "true"
13. Haptic feedback
haptic_feedback_enabled "0" 0 is off and 1 is on. 0 disables boot vibration as well.
14. Touch sensitivity
touch.presure.scale "0.001"
debug.egl.profiler "1"
15.Dalvik Virtual Machine tweaks. Better performance of device overall
dalvik.vm.checkjni "false"
dalvik.vm.dexopt-data-only "1"
dalvik.vm.heapstartsize "5m"
dalvik.vm.heapgrowthlimit "48m"
dalvik.vm.heapsize "64m"
dalvik.vm.verify-bytecode "false"
dalvik.vm.execution-mode "int:jit"
dalvik.vm.lockprof.threshold "250"
dalvik.vm.dexopt-flags "m=v,o=y"
dalvik.vm.stack-trace-file "/data/anr/traces.txt"
dalvik.vm.jmiopts "forcecopy"
16.Smoother video streaming and tweak media
media.stagefright.enable-player "true"
media.stagefright.enable-meta "true"
media.stagefright.enable-scan "true"
media.stagefright.enable-http "true"
media.stagefright.enable-aac "true"
media.stagefright.enable-qcp "true"
media.stagefright.enable-record "true"
17..Wireless Tweaks
net.ipv4.ip_no_pmtu_disc=0
net.ipv4.route.flush=1
net.ipv4.tcp_ecn=0
net.ipv4.tcp_fack=1
net.ipv4.tcp_mem=187000 187000 187000
net.ipv4.tcp_moderate_rcvbuf=1
net.ipv4.tcp_no_metrics_save=1
net.ipv4.tcp_rfc1337=1
net.ipv4.tcp_rmem=4096 39000 187000
net.ipv4.tcp_sack=1
net.ipv4.tcp_timestamps=1
net.ipv4.tcp_window_scaling=1
net.ipv4.tcp_wmem=4096 39000 18700
18. This removes fps cap (TRY AT YOUR OWN RISK) I run this doh it's fine.
debug.gr.swapinterval "0"
More Tweaks will be added soon stay tuned.
To disable fingerprint animation for faster unlocking do these settings in the same app.
Add new setting and type;
fod_animation_type
And in edit settings type;
4
garylawwd said:
To disable fingerprint animation for faster unlocking do these settings in the same app.
Add new setting and type;
fod_animation_type
And in edit settings type;
4
Click to expand...
Click to collapse
Do u think I should add 3verything I use? I think I should I'll update post. Thank u
If I follow this guide will I still be able to receive OTA updates??
Barbiox Dogg said:
If I follow this guide will I still be able to receive OTA updates??
Click to expand...
Click to collapse
In theory yes. Your phone is not unlocked neither is it rooted. No permissions to Google Android settings has been compromised so to Android your phone is still stock and locked. How the program works is like a launcher works on Android. Installing a launcher changes settings and allows features without affecting it's Android settings original launcher. Settings database editor does the same except it runs user commands on top of android system settings. That's why if u delete a setting or if u uninstall app it just goes back to original settings and deleted those you added. You can compare settings from system table and android properties tables. You cannot change android properties settings doh. I cannot confirm if you will get OTAs because I just played around with these settings yesterday and updates for XIAOMI MI A3 is the 5th of every month. What you can do is wait until after the 5th of october and I will update to let you know a defenitive yes. If anything just erase the settings u used. Remember or use settings from this guide so u can find and delete them. Or if u used a site use dat to find and delete. I'll add this reply to update post.thank you.
Dasmion said:
In theory. Your phone is not unlocked neither is it rooted. No permissions to Google Android settings has been compromised so to Android your phone is still stock and locked. How the program works is like a launcher works on Android. Installing a launcher changes settings and allows features without affecting it's Android settings original launcher. Settings database editor does the same except it runs user commands on top of android system settings. That's why if u delete a setting or if u uninstall app it just goes back to original settings and deleted those you added. You can compare settings from system table and android properties tables. You cannot change android properties settings doh. I cannot confirm if you will get OTAs because I just played around with these settings yesterday and updates for XIAOMI MI A3 is the 5th of every month. What you can do is wait until after the 5th of october and I will update to let you know a defenitive yes. If anything just erase the settings u used. Remember or use settings from this guide so u can find and delete them. Or if u used a site use dat to find and delete. I'll add this reply to update post.thank you.
Click to expand...
Click to collapse
Thanks so much for quick response. You are the man.
Barbiox Dogg said:
Thanks so much for quick response. You are the man.
Click to expand...
Click to collapse
You are welcome.
Hello, I was curious whether the audio improvement also affects the headphones or is it just the phone speaker?
Thank you.
something wrong with database link .... and setedit is not working with this adb command line
and which tabs we put the commands? system? global? secure? android propriet(cannot edit here)?
TiagOverminD said:
something wrong with database link .... and setedit is not working with this adb command line
and which tabs we put the commands? system? global? secure? android propriet(cannot edit here)?
Click to expand...
Click to collapse
1. Ok seeing that the link failed, you can get the app on the play store. It's name is "Settings database editor". It is represented by a blue gear and red background photo.
2. Explain what you mean by setedit isn't working with command line. Like is it that it closes after u put in the adb command. Does it not open, what is the error message?
3 system table.
1.Haptic feedback / intensity
haptic_feedback_enabled "1"
haptic_feedback_intensity "1"
this is not working for me. anyone tested?
bibekmufc said:
Hello, I was curious whether the audio improvement also affects the headphones or is it just the phone speaker?
Thank you.
Click to expand...
Click to collapse
In my opinion it applies to both. The difference is noticable in the speaker but not by a huge margin. With headphones I have the kz zs10 and the tin hifi p3. It's an improvement as well, not very drastic but it is there. In my opinion any improvement is good improvement with this phone. The other settings show drastic improvement for example fast boot, better WiFi and navigation fps.
grafa89 said:
1.Haptic feedback / intensity
haptic_feedback_enabled "1"
haptic_feedback_intensity "1"
this is not working for me. anyone tested?
Click to expand...
Click to collapse
Which one does not work for you?
The Intensity
grafa89 said:
The Intensity
Click to expand...
Click to collapse
Yea done testing on my A1 and A3. It works properly on my A1 but not my A3. I would have to remove this from my recommend list seeing that you and I are having this issue. Sorry for the inconveniences. Feel free to try the others. In the mean time I'm going to look for work around for vibration intensity without root. I'm sure there is one method out there.
Dasmion said:
1. Ok seeing that the link failed, you can get the app on the play store. It's name is "Settings database editor". It is represented by a blue gear and red background photo.
2. Explain what you mean by setedit isn't working with command line. Like is it that it closes after u put in the adb command. Does it not open, what is the error message?
3 system table.
Click to expand...
Click to collapse
working man ! thanks but maybe some lines ''ro.'' work only in build prop,i'm wondering disable passive gps and use only agps
can you make any video tutorial for all of us?? please
TiagOverminD said:
working man ! thanks but maybe some lines ''ro.'' work only in build prop,i'm wondering disable passive gps and use only agps
Click to expand...
Click to collapse
Glad it worked. Thanks.
soliman.sohan said:
can you make any video tutorial for all of us?? please
Click to expand...
Click to collapse
Thanks for the suggestions, I'll make the effort and put the link in the post.
bibekmufc said:
Hello, I was curious whether the audio improvement also affects the headphones or is it just the phone speaker?
Thank you.
Click to expand...
Click to collapse
Made a little video thanks