Hello hello,
I changed the DPI of the phone to 480 (not rooted, only with adb command), and now, I get this problem, sometimes the images are zoomed in or zoomed out.
For example (see the screenshots below), on the 9gag app, in the comments, every profile pic is zoomed out, and the rest of the block is colorized by the last pixel of the profile pic.
Another example (for the zoom in), is when I open an image with ES Explorer's Image Browser, it's zoomed in and I can't move across the picture, neither zoom out.
It's not on every program, for example with Gallery, Google Photos, or usual pictures (like going through Chrome or 9gag posts), everything is fine.
It's clearly the DPI matter, since when I go back to 560, everything goes back to normal.
Do you have an idea about this problem ?
Thanks a lot for your help!
https://goo.gl/photos/FsWySABAaYRTyw8JA
https://goo.gl/photos/BhSRTvEcSLM8dzUQA
EDIT: I see that you are not rooted. I don't think you can fix the DPI without root, because you need to edit the build.prop file in order to fix your issue. So to my knowledge, you have to root or change your DPI back to 560.
Download Kernel Aduitor and go to build.prop editor. Search for lcd_density and make sure that value also says 480. If it does, you may need to find a different DPI.
I had the same issue on DPI 500 but the solution above fixed it.
I recently had this problem and couldn't find a fix or details on it anywhere. What happens is that there are 2 methods of changing DPI, the non-root and the root method. The root method is more reliable as it modifies build.prop, and the non-root method causes problems with other apps and rendering. I solved it by resetting my build.prop file and going back to stock DPI.
Alright, so root it will be.
Huh, by rooting, I'll lose the warranty right? It may not be a good idea for me ...
Thanks for your answers!
Sent from my XT1572 using XDA Free mobile app
pef6000 said:
Alright, so root it will be.
Huh, by rooting, I'll lose the warranty right? It may not be a good idea for me ...
Thanks for your answers!
Sent from my XT1572 using XDA Free mobile app
Click to expand...
Click to collapse
The only way to root to my knowledge is by unlocking the bootloader, which does void your warranty. BUT, it doesn't void your warranty for a hardware defect. So if your battery randomly explodes, you would still be covered. Your software warranty is void. I think it's worth it because I've never had software issues with phones, only hardware issues with the Nexus 6.
chris23445 said:
The only way to root to my knowledge is by unlocking the bootloader, which does void your warranty. BUT, it doesn't void your warranty for a hardware defect. So if your battery randomly explodes, you would still be covered. Your software warranty is void. I think it's worth it because I've never had software issues with phones, only hardware issues with the Nexus 6.
Click to expand...
Click to collapse
Oh really ? Is this warranty thing applicable everywhere ? I'm from Belgium, so I don't know if it works that way too. (even though it seems pretty logical).
Thanks for the info !
pef6000 said:
Oh really ? Is this warranty thing applicable everywhere ? I'm from Belgium, so I don't know if it works that way too. (even though it seems pretty logical).
Thanks for the info !
Click to expand...
Click to collapse
Not sure about international warranties, sorry. No problem at all! Hopefully someone can help you with international warranty info.
Related
Hi,
I have a Samsung Galaxy Y. It's been behaving a little weird. The camera take photos upside down i.e. I have to hold the phone upside down for the photo to be upright. Why is this? and how can I solve it?
Note: I have tried resetting to factory settings but it of no use. The problem remains.
Thank you.
ya it's just a wrong or corrupted apk.......
use the attached apk and put it to system/app and set permission's if u don't know how to do it search the forum " how to replace system apps"
and that's all ur problem will be solved...... have nice day and good luck :good:
shivamsejal said:
use the attached apk and put it to system/app and set permission's if u don't know how to do it search the forum " how to replace system apps"
and that's all ur problem will be solved...... have nice day and good luck :good:
Click to expand...
Click to collapse
Guys, anything else?
scotyard said:
Guys, anything else?
Click to expand...
Click to collapse
caused by either a hardware or just a faulty camera app,
try doing what he said,
if that does not work,
try re-flashing to stock,
if still does not work,
it is a hardware issue and needs to be repaired by a licensed technician
deathnotice01 said:
caused by either a hardware or just a faulty camera app,
try doing what he said,
if that does not work,
try re-flashing to stock,
if still does not work,
it is a hardware issue and needs to be repaired by a licensed technician
Click to expand...
Click to collapse
Ah I see. There was no physical damage to the device so it has to be an app related issue or the HW has gone bonkers.
1) Also, could this be related to the fact that even in games, I have to tilt the phone a little to the other side to go straight.
2) Thank you to shivamsejal for the app but is there any risk in replacing a system app by an app provided by a new member? If yes, what kind of risks? Also, do I install it using astro?
Thank you
Let me elaborate:
So earlier today I was messing around with Density Changer while going to Kingsville to see my brother. I was messing around with the DPI value, changing it from 480 to 420 and such. I changed it to 520 and, like normal, asked me to reboot. I rebooted.
The phone started up a lot longer than usual. I thought that this was just a simple glitch, but it took longer for a reason. The time and date on my lock screen wasn't working. Messaging, Contacts, Camera, Samsung keyboard, and the sort wasn't working. Worst of all, TouchWiz wasn't working either. In panic, I tried to open Density Changer from settings but couldn't. I reset my phone to the factory settings. It was rather quick to format (I didn't have much except for some PSP roms and gallery images). I was relieved for a bit, but when it booted it was still unfunctional, not to mention the keyboard still didn't work, so I had to skip a ton of steps. Since TouchWiz was still broken, I set the home screen to Easy Mode. When I looked around with Easy Mode, I realized that you can run apps there without it crashing. I felt so dumb. So now I can't log in to the Play Store to undo what I did, I don't have the app anymore, TouchWiz won't work, I don't even know if I can recieve messages, yada yada. I feel like I am so screwed.
TL;DR changed the DPI from 480 to 520, all hell went loose. did factory reset in panic, even more screw.
Does anyone know what I can do instead of sending it for repair? I don't think AT&T will be able to repair it anyways-- just to give me a new phone.
Try download the last official att rom and use odin. You can find it here in XDA forum. Good luck
Sent from my SGH-I337M using XDA Premium 4 mobile app
wawis said:
Try download the last official att rom and use odin. You can find it here in XDA forum. Good luck
Sent from my SGH-I337M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I appreciate that you want to help! It means a lot. But before I attempt this, does this change absolutely EVERYTHING to default? I think the reason why my phone got so messed up was because the DPI was too high. :/
Do you know what firmware you're on? And if you have a custom recovery did you make a nandroid before you started messing around? If you did, like you should have, just restore that.
Dabreaker9 said:
I appreciate that you want to help! It means a lot. But before I attempt this, does this change absolutely EVERYTHING to default? I think the reason why my phone got so messed up was because the DPI was too high. :/
Click to expand...
Click to collapse
MAKE SURE YOUR NOT ON THE MF3 UPDATE. IF YOU ARE DO NOT ATTEMPT.
If your running MDL or lower, then download the MDL package and flash it with odin. It will indeed make everything stock.
MDL Package
http://www.androidfilehost.com/?fid=23134718111253756
Odin
http://www.androidfilehost.com/?fid=23134718111253763
1. Place phone in download mode
2. Hook to computer via USB
3. Open Odin
4. Click the PDA button and place the MDL file you just downloaded there.
5. Click start.
The process will take a few minutes, so don't panic. Let me know if that fixed it.
Shoot, man. I'm on the MF3 update. I have root though, will that help with fixing it?
jd1639 said:
Do you know what firmware you're on? And if you have a custom recovery did you make a nandroid before you started messing around? If you did, like you should have, just restore that.
Click to expand...
Click to collapse
I'm on the MF3 firmware. I didn't make any custom recovery file things.
Dabreaker9 said:
I'm on the MF3 firmware. I didn't make any custom recovery file things.
Click to expand...
Click to collapse
Go to a Best Buy that has a Samsung Experience booth and see if they will restore factory MF3 for you. Then, I suggest you don't do ANYTHING to your phone but use it for calls and stock abilities.
it really amazes me just how many people in the past few days have screwed up their phones, and the ONLY reason is because they didn't read
deadenz said:
it really amazes me just how many people in the past few days have screwed up their phones, and the ONLY reason is because they didn't read
Click to expand...
Click to collapse
Yep, the more popular the phone, the more people that get a hold of it that shouldn't be doing anything with it except making calls. Laziness and ignorance will create a brick every time. The truly funny part is how quick they run here to make a post for people to fix their screw-ups, but they wouldn't come here to take a little time and effort to learn and read about what to do and how to do it in the first place.
deadenz said:
it really amazes me just how many people in the past few days have screwed up their phones, and the ONLY reason is because they didn't read
Click to expand...
Click to collapse
Hey, now. I almost have it fixed. I just need the .apk file for Density Changer so I can install it, paste "480" into the box and reboot. Would someone be so kind to do it for me? This laptop is a school laptop which has Fortinet as an antivirus and a website restrictor. I would do it myself but my parents are considering taking me to AT&T ASAP when I go back home tomorrow.
But, yeah. I should have read on. I know that bigger values made the screen smaller, but I guess the S4 goes crazy when that happens.
Dabreaker9 said:
Let me elaborate:
So earlier today I was messing around with Density Changer while going to Kingsville to see my brother. I was messing around with the DPI value, changing it from 480 to 420 and such. I changed it to 520 and, like normal, asked me to reboot. I rebooted.
The phone started up a lot longer than usual. I thought that this was just a simple glitch, but it took longer for a reason. The time and date on my lock screen wasn't working. Messaging, Contacts, Camera, Samsung keyboard, and the sort wasn't working. Worst of all, TouchWiz wasn't working either. In panic, I tried to open Density Changer from settings but couldn't. I reset my phone to the factory settings. It was rather quick to format (I didn't have much except for some PSP roms and gallery images). I was relieved for a bit, but when it booted it was still unfunctional, not to mention the keyboard still didn't work, so I had to skip a ton of steps. Since TouchWiz was still broken, I set the home screen to Easy Mode. When I looked around with Easy Mode, I realized that you can run apps there without it crashing. I felt so dumb. So now I can't log in to the Play Store to undo what I did, I don't have the app anymore, TouchWiz won't work, I don't even know if I can recieve messages, yada yada. I feel like I am so screwed.
TL;DR changed the DPI from 480 to 520, all hell went loose. did factory reset in panic, even more screw.
Does anyone know what I can do instead of sending it for repair? I don't think AT&T will be able to repair it anyways-- just to give me a new phone.
Click to expand...
Click to collapse
You can try using a root level file explorer to navigate to /system, long press build.prop to open with a text editor, find the following line and change it to 480, then reboot. Root Explorer or ES File Explorer will do what you need.
ro.sf.lcd_density=480
upndwn4par said:
You can try using a root level file explorer to navigate to /system, long press build.prop to open with a text editor, find the following line and change it to 480, then reboot. Root Explorer or ES File Explorer will do what you need.
ro.sf.lcd_density=480
Click to expand...
Click to collapse
Keyboard doesn't work. I was almost going to do that until I realized it. I'm just looking around for any DPI changing applications that allow it to any number (LCD Density Changer only allows it to 280).
I would set it to 280 if I could handle the small-ass icons. I can't, so I'm not gonna bother with that.
scott14719 said:
Yep, the more popular the phone, the more people that get a hold of it that shouldn't be doing anything with it except making calls. Laziness and ignorance will create a brick every time. The truly funny part is how quick they run here to make a post for people to fix their screw-ups, but they wouldn't come here to take a little time and effort to learn and read about what to do and how to do it in the first place.
Click to expand...
Click to collapse
God damn, man. You say it like you've never messed up something on your phone before. I know, I'm a **** for not reading if it was safe, but I'm almost positive you've messed up one way or another before?
Dabreaker9 said:
Keyboard doesn't work. I was almost going to do that until I realized it. I'm just looking around for any DPI changing applications that allow it to any number (LCD Density Changer only allows it to 280).
I would set it to 280 if I could handle the small-ass icons. I can't, so I'm not gonna bother with that.
Click to expand...
Click to collapse
Ooops. missed the keyboard part.
What ROM are you running? Stock MF3?
upndwn4par said:
Ooops. missed the keyboard part.
What ROM are you running? Stock MF3?
Click to expand...
Click to collapse
The default MF3, yeah. Fixed it with www-57.zip-pysha-re.co-m/v/78538033/file.html (remove those dashes). I went on Google Chrome and used voice recognition to get 460, pasted it in the DPI box, applied it. Everything's good now.
Dabreaker9 said:
God damn, man. You say it like you've never messed up something on your phone before. I know, I'm a **** for not reading if it was safe, but I'm almost positive you've messed up one way or another before?
Click to expand...
Click to collapse
Umm... Yeah Scott is a little grumpy when he sees things over and over again lol. I'm glad you were able to get it fixed.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Dabreaker9 said:
God damn, man. You say it like you've never messed up something on your phone before. I know, I'm a **** for not reading if it was safe, but I'm almost positive you've messed up one way or another before?
Click to expand...
Click to collapse
Well, it's really not about messing up. What is done is done. It's about learning from it and not doing it again. I can tell you are on the right path because you are trying to fix it. You screwed up... a lot of people screw up...what is important is not doing it again. Always read as much as you can about anything before you try it. It's just a phone and it is always replaceable but you can save yourself a lot of trouble by reading before doing. Like I said, i think you realize that. I'm sure you don't want to go through this type of trouble again to just get the phone working. What you did (change the dpi) isn't a big deal but it has big consequences. I was mostly referring to people that that try to "root", put custom recoveries on their phones, custom ROMs, etc. There is so much information about these things in the XDA forums it isn't funny, yet people think they don't need to read and learn about it or they think their time is too valuable. But as soon as they screw up (and they always do), all of the sudden, they find the time to come to XDA and beg for someone to fix their phone. As soon as someone points out that they should have read and learned in the first place, they get a smug attitude and act like people "owe" them a fix for their stupidity. Like I said, not necessarily your situation, but it happens all of the time regardless.
**Edit**
I'm am glad you fixed your phone and is is encouraging to see how much work and effort you put into fixing it. It would be nice if everyone put that kind of effort into fixing their phones. I have a feeling you will do just fine with modifying your phone.
i'm having screen issues (phone keep face dialing even though screen is off). i think i need a replacement device. i'm with verizon.
i am rooted, have cwr installed, and have a debloated version of 12b installed.
do i need to go through the hassle of putting the phone back into its factory state before taking it in for replacement, or do they not really care about that anymore and i can just take it in as-is?
thanks for the info!
I'm living in Europe, Sweden, in here we actually have an EU-directive that states the owners right to run the firmware of their own choice and that manufacturers must prove that any such custom software IS the reason a device has failed before voiding any warranties.
But still, I ALWAYS return to stock before any service is done, just to get out of the hassle of explaining this to service companies.
Return to stock, that's what I've have done.
Be happy. It's much more fun that way.
Kaherdin, I live in Denmark and I would love to know where I can find that written black on white
Sent from my LG-D802 using XDA Premium 4 mobile app
---------- Post added at 07:05 PM ---------- Previous post was at 07:02 PM ----------
Found the thread, but didn't find the original EU statement: http://forum.xda-developers.com/showthread.php?t=1998801
Sent from my LG-D802 using XDA Premium 4 mobile app
byproxy said:
i'm having screen issues (phone keep face dialing even though screen is off). i think i need a replacement device. i'm with verizon.
i am rooted, have cwr installed, and have a debloated version of 12b installed.
do i need to go through the hassle of putting the phone back into its factory state before taking it in for replacement, or do they not really care about that anymore and i can just take it in as-is?
thanks for the info!
Click to expand...
Click to collapse
Just as @Kaherdin said, to avoid any hassle with service reps, just reflash stock ROM and you should be good to go.
Can you perform a sensor test? Seems to me your proximity sensor might be an issue. It's somewhere in the hidden menu, not exactly sure where. Also, see if the problem persists after flashing back to stock.
robogo1982 said:
Can you perform a sensor test? Seems to me your proximity sensor might be an issue. It's somewhere in the hidden menu, not exactly sure where. Also, see if the problem persists after flashing back to stock.
Click to expand...
Click to collapse
can you tell me how to get to hidden menu? i tried two different codes from two different threads and neither worked. would LOVE to be able to perform a sensor test.
thanks!!
@byproxy sure. Open the dialer and type 3845#*xxx# where xxx is the model number of your phone. Verizon iz VS980, so I think 980 should work. I really can't say, I have an international D802, so I don't know :/
EDIT: found it.
HiddenMenu and Dialer access enabler
- For some reason, Verizon omitted the HiddenMenus. The apk was absent and they disabled access to most secret codes via the dialer. This adds the newest version of LG's HiddenMenu/AAT apks and enables access via the following dialer codes:
##LGSERVICEMENU - Gets you into the main LG HiddenMenu
##PROGRAM - Verizon's specific menu
##AATEST - AAT menu
##FEATURE - Another VZW menu
##DEBUG
##HELPHELP
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=2567709&page=1
thanks!!!
robogo1982 said:
@byproxy sure. Open the dialer and type 3845#*xxx# where xxx is the model number of your phone. Verizon iz VS980, so I think 980 should work. I really can't say, I have an international D802, so I don't know :/
EDIT: found it.
forum.xda-developers.com/showthread.php?t=2567709&page=1
Click to expand...
Click to collapse
byproxy said:
thanks!!!
Click to expand...
Click to collapse
Did you test it? Does it work properly? Try running all of the hardware tests.
Hi Guys
This is weird. My shiny new Note 3 is about three weeks old. It's working 99.9% perfectly except for a slight sound problem. The problem is that when it is connected to a charging dock it USED to play a tone. Now it just vibrates slightly (but still charges). I also noticed that my camera doesn't make a shutter sound when I take a photo. I wondered whether the two issues are related in some way?.
All other sounds seem to be working OK on the Note3 (so it's not a volume setting) and I have checked whether option for the dock 'making a sound' is switched on. Additionally, there doesn't appear to be an option in the camera settings to switch on/off the sound, so it can't be that.
OK none of this is a major problem, but it is a bit of a niggle!
I hate niggly things! .
Anyone have any ideas?
Thanks
You made any changes recently?
Hiya
Yes, gazillions of changes due to installing apps! Too numerous to narrow it down to a specific action
Cheers
Sent from my SM-N9005 using XDA Premium HD app
stevep said:
Hiya
Yes, gazillions of changes due to installing apps! Too numerous to narrow it down to a specific action
Cheers
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
If you can't/won't narrow it down, how is anyone else supposed to?
Do you have these checked files in the screenshot?
Thank you. That looks like a useful screenshot - where do I go to check if the sound file is checked as in your screenshot? I guess thats your file manager isn't it? I'm using ES explorer and the phone isn't rooted. Do you happen to know which folder these sound files live? I did a file search and it couldn't find any of the files shown in your screenshot
Cheers
stevep said:
Thank you. That looks like a useful screenshot - where do I go to check if the sound file is checked as in your screenshot? I guess thats your file manager isn't it? I'm using ES explorer and the phone isn't rooted. Do you happen to know which folder these sound files live? I did a file search and it couldn't find any of the files shown in your screenshot
Cheers
Click to expand...
Click to collapse
I use Root Explorer, those files are in system>media>audio >ui.
However, as far as I know you can't access the system folder unless you're rooted, so I think it's unlikely that you've deleted them.
Lost Sound
B3311 said:
I use Root Explorer, those files are in system>media>audio >ui.
However, as far as I know you can't access the system folder unless you're rooted, so I think it's unlikely that you've deleted them.
Click to expand...
Click to collapse
Thanks again - at least I know i probably haven't deleted them. I don't suppose there's a way of 'force reinstalling' the stock camera app is there?
stevep said:
Thanks again - at least I know i probably haven't deleted them. I don't suppose there's a way of 'force reinstalling' the stock camera app is there?
Click to expand...
Click to collapse
No idea, sorry. I rooted mine 20 minutes after its first boot, hence clueless really uprooted devices
Lost Sound
B3311 said:
No idea, sorry. I rooted mine 20 minutes after its first boot, hence clueless really uprooted devices
Click to expand...
Click to collapse
OK case closed - I hard reset the phone, reinstalled all the original apps and the missing sounds are back. Sorted! Bit of a drastic measure though
Still don't know WHY the sound disappeared from just the docking process and the camera shutter, but it least it's all fine now
Thanks for all your help and suggestions.
Hey everyone. I am having a issue with my phone when trying to take a screenshot. It will not allow me to take a screenshot, saying "Prevented by security policy." I discovered this when trying to take a screencap inside the Playstation app, but the Playstation Store part of it. As I understand it, this is a restriction by the individual app. How can I bypass this? I already tried some overlay apps like "Touchshot," which the result is either when I open the PS Store, it force quits Touchshot, or it will take a picture but everything is black.
I am not rooted, and would hope to find a solution without rooting. I also saw solutions that involve hooking up the phone to a PC, which I also would like to try to avoid as well. Is this restriction exclusive to the S7/Samsung phones, or it this a universal Android problem? If not, which phones do not have this problem?
If I have to root the phone to do it, is there currently an S7 Edge root that does not trip Knox? Anything else I should know?
Thanks for any help you can give!
stevens_k said:
Hey everyone. I am having a issue with my phone when trying to take a screenshot. It will not allow me to take a screenshot, saying "Prevented by security policy." I discovered this when trying to take a screencap inside the Playstation app, but the Playstation Store part of it. As I understand it, this is a restriction by the individual app. How can I bypass this? I already tried some overlay apps like "Touchshot," which the result is either when I open the PS Store, it force quits Touchshot, or it will take a picture but everything is black.
I am not rooted, and would hope to find a solution without rooting. I also saw solutions that involve hooking up the phone to a PC, which I also would like to try to avoid as well. Is this restriction exclusive to the S7/Samsung phones, or it this a universal Android problem? If not, which phones do not have this problem?
If I have to root the phone to do it, is there currently an S7 Edge root that does not trip Knox? Anything else I should know?
Thanks for any help you can give!
Click to expand...
Click to collapse
No workaround for this, rooted or otherwise, that I'm aware of.
dynospectrum said:
No workaround for this, rooted or otherwise, that I'm aware of.
Click to expand...
Click to collapse
Well there is a way to do it if you are rooted. But since I am not, I was trying to deal with it that way...
Is there even a root for the S7 without tripping Knox yet? If there was, I might root it.
Anyway, thanks for the reply!