Voice Recorder and DPI - G4 Q&A, Help & Troubleshooting

Voice recorder breaks when the global DPI is changed.
My solution with other LG apps is to use Xposed App Settings and force the DPI to 540 or 640. That seems to work just fine with everything, like the notoriously fickle camera app, but it just will not work with the Voice Recorder. I set it to 640 in App Settings and it will not function at all, yet I change global DPI back to stock 640 and it functions just fine.
Any idea on how to get around it? Or convince app settings to force it harder? Is there a different app dependant that also needs to be set to 640?
Cheers

It breacks also Quick Remote. It open but donĀ“t work...

up, any idea how to fix this ? i didnt want to create a new topic so i searched and found this

hi use genisys rom lollipop 2.1 or marshmallow 2.8 or this patch fixed sound recorder dpi 5xx problem

Related

[Q] Google Music and 240 DPI

Hi all,
I notice when I change my DPI to 240, Google Music switches to its tablet interface. It's obviously awful on a phone. Is there any way to manually switch which interface Google Music is using?
Either that or somehow spoof a specific app into thinking the DPI setting is 320?
Thanks,
Giancarlo
MrBig0 said:
Hi all,
I notice when I change my DPI to 240, Google Music switches to its tablet interface. It's obviously awful on a phone. Is there any way to manually switch which interface Google Music is using?
Either that or somehow spoof a specific app into thinking the DPI setting is 320?
Thanks,
Giancarlo
Click to expand...
Click to collapse
I have noticed the same thing on my gs2 though I am switching from 240 to 182. Your post is the only I've found about the issue and it's driving me crazy. If anyone has ideas where to even look in the apk to adjust this it would be extremely appreciated.
I've noticed a few problems from it. Music Playerpro has some display issues, and the Youtube app crashes as soon as I open it. Both work fine with the native DPI.
If you switch to 241 dpi g-music works
You're a genius! Thanks!
Change to 240, open market, then freeze market updater so you don't lose the applications available, change to 241.

marshmallow lg radio and internet not working.

I am on rooted stock marshmallow with xposed installed.I have changed resolution to 1080p and 530dpi.I face a problem everytime i try to open lg fm radio and lg internet i see ''unfortunately ,app has stopped'' and i see the logo of android robot instead of the app icon.How can i restore the fm radio and lg internet browser?
soulfreem said:
I am on rooted stock marshmallow with xposed installed.I have changed resolution to 1080p and 530dpi.I face a problem everytime i try to open lg fm radio and lg internet i see ''unfortunately ,app has stopped'' and i see the logo of android robot instead of the app icon.How can i restore the fm radio and lg internet browser?
Click to expand...
Click to collapse
that is simply caused by your dpi settings, android uses diff dpi folders for diff devices in terms of icons. there is hdpi xhdpi etc, each folder is used in a certain range of dpi, i can't remember but for simplicity i'll use fake examples.
say hdpi folder is 50-100 dpi.
and xhdpi folder is 101-150 dpi. (these folders are found in the apk for the app.)
i used to be a old school themer who themed directly with apk files so i know this topic =D
if lg programmed your phone as 125 dpi default, then they probably only built files and icons for the xhdpi folder. (layouts tell your phone how to draw the ui).
if you switch your dpi to anything lower than 101, then the app will instantly crash because its looking for files in the hdpi folder now instead of xhdpi and lg didn't make the app compatible for those settings because they are assuming you aren't going to change your dpi and they only built the app for that specific phone/dpi range to save money, time, etc. and for control.
essentially your apps are instantly crashing because you have changed the dpi out of the range that will look for the correct files in the apk. if you slowly move your dpi towards the default ( rebooting every time and trying the apps ) eventually you will find the lowest or highest possible setting that won't bump you into the wrong layout and icon folders (folders inside the app (apk)).
can i ask you what version of lg g3 you are running because i'm jealous your radio is working (when you have the correct dpi range set )
(some things you might notice, are that the only apps that stop working are the LG apps that came with the phone, playstore apps are programmed to run in a wider range of dpi settings so they can be installed across a wider range of phones)
This is one of the reason people run AOSP / Cyanogenmod or other popular roms because most of those can run on almost any dpi (within reason) cyanogenmod has dpi built into the settings menu now, but has a bunch of presets, you still have to use build.prop if you want to try things outside of those values but their range is really good i don't think you would want to.. The catch 22 is sometimes you lose your radio and ir blaster anyways on other roms. i think both are working on cm 12.1 but i'm not 100% about fm radio, i have seen lots of ppl get the ir blaster working but you need to flash a patch that changes a few settings (selinux permissive and something else i think) there is a flashable fix for it somewhere kicking around xda if you search for it i'm sure you can find it.
on cm13 the ir blaster is working but the lg quick remote app isn't so you have to use a playstore app until lg releases a version for marshmallow and someone ports it to aosp, also will probably have to turn selinux to 0 still as well

Camera Forced close when I record with dpi changed in build.prop

Good afternoon,
I changed the dpi in build.prop recently, but only now that I realize that the camera stopped recording . When put to record , advancing to one second it gives force close . What can it be?
I am using the rom marshmallow
The dpi. Lg apps dont work with lower dpi

Changing lcd density (DPI) problem

I'm facing an issue when changing lcd density (DPI) using build.prop editor, some widgets which was working on OP1 CM 11,12,13, are not displayed fine now. also Play store has some resolution issues, like recommended developer icon !
I tried different resolutions (380,400,420,460) all with the same results.
Any clues ?
Don't change DPI globally, that's problem-prone. Instead, install Xposed with module "App settings" and change DPI only for those apps where you want it. (Another advantage is that you even additionally have more flexible options, like changing text size or using the app's tablet UI etc.)
zorro_tmh said:
I'm facing an issue when changing lcd density (DPI) using build.prop editor, some widgets which was working on OP1 CM 11,12,13, are not displayed fine now. also Play store has some resolution issues, like recommended developer icon !
I tried different resolutions (380,400,420,460) all with the same results.
Any clues ?
Click to expand...
Click to collapse
hasenbein196601 said:
Don't change DPI globally, that's problem-prone. Instead, install Xposed with module "App settings" and change DPI only for those apps where you want it. (Another advantage is that you even additionally have more flexible options, like changing text size or using the app's tablet UI etc.)
Click to expand...
Click to collapse
I changed it globally with the app "Le DPI Changer" to 360 and don't have any problems in any app.
440 is great..
i have set the dpi to 380 and have problems in the following apps:
twitter: pictures in tweets have corrupted thumbnails
whatsapp: when you want to crop a picture, it is zoomed in very much and you cannot zoom out so you can only crop 10% of an image
imgur: corrupted thumbnnails too
music player (poweramp) cover art in player notification is zoomed
i think oxygen os handles dpi differently, as i couldnt even find dpi setting in build.prop
i hope someone can fix this bc i would like to stay on oxygen until cm ports etc have dash charging
As I said: No global DPI, but Xposed module "App settings". Then you avoid any problems.
~MaX~ said:
i have set the dpi to 380 and have problems in the following apps:
twitter: pictures in tweets have corrupted thumbnails
whatsapp: when you want to crop a picture, it is zoomed in very much and you cannot zoom out so you can only crop 10% of an image
imgur: corrupted thumbnnails too
music player (poweramp) cover art in player notification is zoomed
i think oxygen os handles dpi differently, as i couldnt even find dpi setting in build.prop
i hope someone can fix this bc i would like to stay on oxygen until cm ports etc have dash charging
Click to expand...
Click to collapse
Hmm from the four apps you mentioned I only use WhatsApp, and I just tested out the cropping of a selfie, normal picture and a gallery picture, it works fine for me.
I'm on 360dpi.
Does anyone know the stock dpi value?
numbere said:
Does anyone know the stock dpi value?
Click to expand...
Click to collapse
480
Sent from my ONEPLUS A3003 using Tapatalk
I'm noticing font is pretty big in comparison to another 1080p device I have in my possession. It's DPI is set at 420 and what I'd consider perfect.
crysen said:
I changed it globally with the app "Le DPI Changer" to 360 and don't have any problems in any app.
Click to expand...
Click to collapse
Which method in the app did you use? I moved the DPI slider in the app, applied it, rebooted, but nothing changed...
Sent from my ONEPLUS A3000 using Tapatalk
rickyx32 said:
Which method in the app did you use? I moved the DPI slider in the app, applied it, rebooted, but nothing changed...
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Oh right, forgot to mention, use the other method, the slider also didn't work for me.
Users with issues,
try this method:
Create a file called local.prop in the root/data folder with this text in it:
qemu.sf.lcd_density=xxx
xxx = your dpi value
Permissions of that file should be:
rw-r-r--
Reboot.
I did not test it yet on OxygenOS as my device is not unlocked, nor rooted yet.
AcmE85 said:
Users with issues,
try this method:
Create a file called local.prop in the root/data folder with this text in it:
qemu.sf.lcd_density=xxx
xxx = your dpi value
Permissions of that file should be:
rw-r-r--
Reboot.
I did not test it yet on OxygenOS as my device is not unlocked, nor rooted yet.
Click to expand...
Click to collapse
That file already exists on mine and already has the desired DPI but it's not having any effect...
rickyx32 said:
That file already exists on mine and already has the desired DPI but it's not having any effect...
Click to expand...
Click to collapse
Use the Le dpi changer from google play, set dpi value and hit build.prop button. Accept it and reboot.
OP3 by TT
i tried to change dpi with ledpi and now my build.prop file is empty and broken. can someone upload build.prop from latest oxygen os please?
EDIT: default.prop in root can be used as a new build.prop in case u get the same problem as me, no need for upload
Anyone know where I can change DPI manually? I can't find the code in the build.prop. I don't want to rely on whack apps or toolkits...
Sent from my ONEPLUS A3000 using Tapatalk
rickyx32 said:
Anyone know where I can change DPI manually? I can't find the code in the build.prop. I don't want to rely on whack apps or toolkits...
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
it doesn't exist on builb.prop of OP3, I added it manually.
Code:
ro.sf.lcd_density=400
crysen said:
Hmm from the four apps you mentioned I only use WhatsApp, and I just tested out the cropping of a selfie, normal picture and a gallery picture, it works fine for me.
I'm on 360dpi.
Click to expand...
Click to collapse
i always had the cropping problem with WhatsApp using custom dpi. try to set a new profile picture. always zoomed and no chance zooming out. you have to change the dpi back to 480 to change your profile picture, but otherwise i have had no problems with 380 dpi.
My only qualm about this phone was the abnormally large text and padding in various apps, 440 dpi is a perfect adjustment, haven't seen any graphical glitches as of yet.

Camera Doesn't Work (Related to DPI Changing)

So i am running into a very strange issue that i haven't been able to find much information on. I am running the latest OOS (3.1.2) rooted, i had changed the DPI a few days ago using build prop editor and everything seemed to be working just fine, except my camera, it suddenly would freeze when a picture is taken, crash, and not produce a picture, and sometimes the picture would be just green.
Here is what iv'e tried:
removed the line from build prop editor and rebooted to get to stock DPI
changed the DPI to stock with the toolkit, then back to a different DPI, then back to stock.
removed the camera app cache
factory reset the phone
Strangely enough the camera in HDR mode appears to work just fine, but it doesn't appear to work in any other mode (including video).
Using the camera with flash always turned on in pretty much any mode seems to also work.
Atlantisman said:
So i am running into a very strange issue that i haven't been able to find much information on. I am running the latest OOS (3.1.2) rooted, i had changed the DPI a few days ago using build prop editor and everything seemed to be working just fine, except my camera, it suddenly would freeze when a picture is taken, crash, and not produce a picture, and sometimes the picture would be just green.
Here is what iv'e tried:
removed the line from build prop editor and rebooted to get to stock DPI
changed the DPI to stock with the toolkit, then back to a different DPI, then back to stock.
removed the camera app cache
factory reset the phone
Strangely enough the camera in HDR mode appears to work just fine, but it doesn't appear to work in any other mode (including video).
Click to expand...
Click to collapse
I posted about this issue a few days ago http://forum.xda-developers.com/oneplus-3/help/weird-camera-bug-t3404660
mr.shme said:
I posted about this issue a few days ago http://forum.xda-developers.com/oneplus-3/help/weird-camera-bug-t3404660
Click to expand...
Click to collapse
Sorry, didn't notice that.
I flashed back to bone stock OOS 3.1.2 and everything seems to be working now... I will attempted to change the DPI again via the toolkit.
I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.
That's why I always say that global DPI change is not a good idea, period.
Much better and additionally more flexible is using the Xposed module "App Settings" where you can run every app at an individual DPI setting and tweak some more things (e. g. having an app run with its tablet UI).
I had the same issue on OOS 3.1.3 rooted and DPI changed.
I enabled RAW mode and it fixed the issue.
crumble6 said:
I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.
Click to expand...
Click to collapse
What DPI value did you set it to? No issues with camera, icons, widgets, etc?
jiznon said:
What DPI value did you set it to? No issues with camera, icons, widgets, etc?
Click to expand...
Click to collapse
400. No issues at all except that when I use "large text" captions in snapchat they display fine on my screen but the text is much smaller and out of position on my friends' phones. Literally not a single other problem with any app I've tried though. I've heard 380 works good too. Tempted to try it but tbh I'm happy at 400 for now.
crumble6 said:
I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.
Click to expand...
Click to collapse
crumble6 said:
400. No issues at all except that when I use "large text" captions in snapchat they display fine on my screen but the text is much smaller and out of position on my friends' phones. Literally not a single other problem with any app I've tried though. I've heard 380 works good too. Tempted to try it but tbh I'm happy at 400 for now.
Click to expand...
Click to collapse
Thanks for the quick reply. So far my experience has been frustrating.
1) Changed DPI to 400 via build.prop edit. Resulted in camera issues. Could not reset DPI or change to any other value. Had to reflash OOS 3.1.3 to fix.
2) Did some research. Heard a OP3 toolkit here on xda could change DPI without issue (I believe it just uses the adb method) . Used it to change to 400. Camera is fine, but I experience wonky sizing issues with widgets, icons on notification banners, twitter photo previews, and a few other little text size issues. Tried using the toolkit to return to default DPI but it simply doesn't change anything.
3) Per your account of this app, I tried it but it us unable to make any change. Looks like I may have to reflash AGAIN, and attempt the Le DPI Changer again.
Bah.
jiznon said:
Thanks for the quick reply. So far my experience has been frustrating.
1) Changed DPI to 400 via build.prop edit. Resulted in camera issues. Could not reset DPI or change to any other value. Had to reflash OOS 3.1.3 to fix.
2) Did some research. Heard a OP3 toolkit here on xda could change DPI without issue (I believe it just uses the adb method) . Used it to change to 400. Camera is fine, but I experience wonky sizong issues with widgets, icons on notification banners, and a few other little text size issues. Tried using the toolkit to return to default DPI but it simply doesn't change anything.
3) Per your account of this app, I tried it but it us unable to make any change. Looks like I may have to reflash AGAIN, and attempt the Le DPI Changer again.
Bah.
Click to expand...
Click to collapse
Sorry, I should have mentioned. I am using Nova launcher and have changed the grid size of the desktop to 11 x 7. Things will probably behave weird if you are using the oneplus launcher.
crumble6 said:
Sorry, I should have mentioned. I am using Nova launcher and have changed the grid size of the desktop to 11 x 7. Things will probably behave weird if you are using the oneplus launcher.
Click to expand...
Click to collapse
No worries. I am also using Nova Launcher with custom grid size. Only issues on my desktop is wonky icon size with Chronus widget.
jiznon said:
No worries. I am also using Nova Launcher with custom grid size. Only issues on my desktop is wonky icon size with Chronus widget.
Click to expand...
Click to collapse
I find enabling widget overlap in Nova and then playing around with resizing widgets I can usually get them looking right in the end.
I had already posted this here but it seemed like Nobody besides me had this problem.
http://forum.xda-developers.com/oneplus-3/help/camera-issues-root-t3409764
I'm glad this issue is getting attention!
running 340 dpi, works fine for me. did it with le dpi changer
Running 290 all good using le dpi changer ?
Sent from my ONEPLUS3
I'm starting to wonder there is a magic DPI number that doesn't break the camera!! Time to test!
I found this solution on the oneplus 3 reddit. Camera works perfectly and there are no weird icons!
https://www.reddit.com/r/oneplus/comments/4satgq/changing_op3_dpi_using_buildprop_without_breaking/
Basically use qemu.sf.lcd_density=xxx instead of ro.sf.lcd_density=xxx in your build.prop!
I'm using 420 and all is awesome now!!
Huge thanks to this guy for posting the solution!!
ro.sf.lcd_density=400 in build.prop works just fine on my device running stock OOS 3.2.1.
Only manual mode is slightly misaligned inside the camera app.
Trying qemu.sf.lcd_density=400 gives me the same result btw.
I never had issues with green photos in HQ or other weird behaviour.
Running dpi 400 via manual build.prop edit since day one
and only had to repeat this after each ota.

Categories

Resources