So I got this phone from my girlfriend, looks like a really decent piece of kit when it works, I would love to use this as a backup/secondary phone, but I've run into a really weird issue. I've scoured the interwebs looking for a fix, but so far seems I'm the only one.
Basically what happens is this. On first power-up, the phone works fine, screen looks good, everything is like normal. The problem starts when I try pull the phone out of standby after short-pressing the power button. Once the phone comes out of standby, it looks like the resolution of the screen halves itself, so I get all icons/graphical elements overlaid over each other. I have pictures of the issue, just waiting till I get my post count up.
I've flashed a ROM, hard reset, soft reset, cleaned connections, I'm sort of out of options here. Any ideas XDA'ers?
Cheers,
Droidzor said:
So I got this phone from my girlfriend, looks like a really decent piece of kit when it works, I would love to use this as a backup/secondary phone, but I've run into a really weird issue. I've scoured the interwebs looking for a fix, but so far seems I'm the only one.
Basically what happens is this. On first power-up, the phone works fine, screen looks good, everything is like normal. The problem starts when I try pull the phone out of standby after short-pressing the power button. Once the phone comes out of standby, it looks like the resolution of the screen halves itself, so I get all icons/graphical elements overlaid over each other. I have pictures of the issue, just waiting till I get my post count up.
I've flashed a ROM, hard reset, soft reset, cleaned connections, I'm sort of out of options here. Any ideas XDA'ers?
Cheers,
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
I'm sorry to hear about your trouble. There is no forum specifically for the Galaxy Music but you may want to ask your question with all relevant details in the friendly general Android Q&A, Help & Troubleshooting forum at http://forum.xda-developers.com/android/help. That's a good place to start where members familiar with your device might be able to advise you. Since your device is not widely used, please be patient and give the experts plenty of time to respond.
Good luck!
Related
I'm fixing an infuse for a friend who needed the screen replaced simple enough job so I thought as I repair phones and electronics as kind of a hobby. However the replacement screen isn't responding to any kind of touch at all. It displays the puzzle piece lock screen and everything else even shows there's been some missed calls ect. yet will not respond to any kind of touch. I think it's a calibration issue but I can't get passed the lock screen so there's no way to change the setting. Honestly I'm most worried about all the media on the phone most (pics, videos, contacts, ect )
If there is a way I can retrieve that off the internal storage I'll feel better about taking drastic measures. Other things I've noticed is an unusualy long boot up time hanging at the white Samsung letters but this is the first time I've dealt with an infuse so I'm not to sure on that.
Any advice is appreciated.
Thanks,
s1im
There are different versions of screens or maybe it was revisions. At least for the LCD +digitizer assembly. Rev.6.1 and 6.2 and 6.3 if I remember correctly.
Edit....here is a link for reference, also two of the screens were interchangeable but not all three. Sorry I don't remember which ones.
http://item.mobileweb.ebay.com/viewitem?itemId=180914982430&siteId=0&isClassified=false
Edit....my statement regarding interchangeability may not be true. The screen I bought could be used as a replacement for two of the rev numbers. That could mean that it is backward compatible but the other one isn't forward compatible.
The link said this item has been removed, but to be clear your saying not all revisions of screens can be used as replacements that you must find out which rev your original screen is?
s1imch4anc3 said:
The link said this item has been removed, but to be clear your saying not all revisions of screens can be used as replacements that you must find out which rev your original screen is?
Click to expand...
Click to collapse
Correct mine had a sticker on it.
Bummer I have no idea what kind of screen she had I threw it away as a jumbled mess is there any other way to find out what screen it was... either way thanks for the replies
Wish I could answer that, but here is another screenshot. It shows one for 6.0/6.1 and another for 6.2 so my original numbers were off. Did the new one say what it is?
Do you know of any way to retrieve the pics and other media off the phone without being able to unlock the screen
s1imch4anc3 said:
Do you know of any way to retrieve the pics and other media off the phone without being able to unlock the screen
Click to expand...
Click to collapse
Just guessing but maybe adb. You could try to edit the title of your thread or start a new one about this question.
Edit..I have an idea but first a few questions , is this phone stock, and would you be comfortable flashing a kernel if it is? This will give you CWM recovery which has mount USB storage as an option in it. All this can be done with the physical buttons, power and volumes.
I found something that may work without having to make software modifications so I'm going to try that first and if not I'll get back to you...
To answer your questions tho the phone is stock and I've rooted /flashed a couple phones with no problems before so I'm OK with giving it a try
Again I'd like to thank you for your continuous help
You should be able to pull everything you need with adb...but the problem is, is adv enabled? And can you pull a whole directory? I doubt you know individual file names for each media file, not to mention that would be a long tedious process as there are likely well over a 100 if not in the 1000s of music/pics/vids
Well..looks like you can pull a whole.directory (sdcard)
this thread may help http://forum.xda-developers.com/showthread.php?t=744454
Btw...you don't have to be rooted to adv pull
Sent from my HTC PH39100 using Tapatalk 2
UPDATE: I took the phone back apart finally after some grueling hours of adb research that lead me almost in circles and found that the replacement LCD is a rev 6.2 and that the revs 6.0/6.1 are the universal more common screens in the u.s. infuse. I decided to return the screen and get the other rev in hope it will be that easy...
I'd like to thank the 2 above members that gave me help especially adfergurson for sticking with me and my ?s I will post back when the next screen comes in to confirm it worked for anyone else needing this as future reference
s1imch4anc3 said:
UPDATE: I took the phone back apart finally after some grueling hours of adb research that lead me almost in circles and found that the replacement LCD is a rev 6.2 and that the revs 6.0/6.1 are the universal more common screens in the u.s. infuse. I decided to return the screen and get the other rev in hope it will be that easy...
I'd like to thank the 2 above members that gave me help especially adfergurson for sticking with me and my ?s I will post back when the next screen comes in to confirm it worked for anyone else needing this as future reference
Click to expand...
Click to collapse
ADB was the first thing I thought of, but flashing a kernel with custom recovery in Odin should allow you to get into USB storage. I am not familiar with the stock recovery but you could see what options are there. I believe it would be from device powered off hold volume up+volume down+ power buttons then release power at Samsung screen.
Were you able to resolve the screen issue with the different version? I am having the same problem.
Hi,
Let me apologize in advance if this question seems familiar, my Google-fu is good and I've read hundreds of posts, thousands probably over the past year looking into this, so I'm finally posting out of well, not desperation exactly, but curiosity.
I have an S3 HTC One S, Ville C2 with TWRP recovery, (the only recovery that works), and Um let's see Luxandroid v4 giving Android v4.1.1 htc sense 4+ software version number 3.19.720.100
If I run the battery down, (I try not to), the phone won't start for a few days.
Well, not true, it is will start, it just won't display anything. I can run adb and see the phone, and it used to restart proper, display and all if I just rebooted it via adb.
That stopped. Now I have to wait until the battery is about 30% at least, this can take several days, start adb, give adb reboot, hold the volume up, and, justy lately, dance naked in the rain around a freshly made clay idol of the Gnome God, Jim, because it's a bit haphazard. (Obviously in the summer this is harder as it rains less.)
It's a completely robust phone the rest of the time, except for the occasional reboot when I've got all the mapping, phone, blue-tooth etc. on. It waits until I'm on the motorway to do this.
Main thing is, I thought it was related to some bug that I used to read about six months ago but which seems to have disappeared from searches. It's definitely is on, but the screen display isn't, "backlighting" isn't. (I know it's not back lit, but in the dark I can see very faintly that these is a display, of sorts).
Why is it doing this?
Can I put is back to stock reliably and would that work to stop this nuisance?
Is there a big words and picture version of putting it back to stock floating about somewhere and I've missed it?
Will I ever be able to put KitKat on it?
I'm not expecting instant answers or any answers, I just thought it was worth asking in the place where all the experts are. (Because I lurk here a lot, I screw up my Nexus 7 (2013) from time to time too).
I do program and teach for a living so I can follow reasonably complicated instructions.
Thanks,
Ania
I've got from someone two Galaxy S Duos 2 S7582.
One had its screen with a huge crack (but worked fine), and the other has a perfect screen but wasn't being able to charge nor start with the first one's battery.
I mean, If I started the first one, it would boot in less than a minute. (Samsung screen with its model, and then Samsung animated logo with blue fading in the background right before finishing booting). While charging it showed the sign of an empty battery for a few seconds, and then the current status of the battery.
The second one if started would only boot till the first samsung screen showing its model, and stay there forever. (at least three hours) While charging it always shows the sign of an empty battery, and goes off once every few seconds.
Huge idea I had "Why not just switch the inside of the working one to the frame of the one with the perfect screen".
So I went to youtube, looked after a video, and found one explaining the process, which is quite simple.
I did It and now the one with the perfect screen still doesn't boot at all, just like before (even with the other's interior). It stays in the same screen forever, and with the same same charging problem.
The second, which supposedly is made with the faulty screen and the faulty interior, does boot after loads of time, but its so slow that it hurts. And by slow i mean, at least half an hour to boot, and totally unusable.
I did reset it to factory with vol up+home+power menu, but i could not even manage to select the language since it only recognised my finger once, took several minutes to pull the language drop-box, and after it did nothing else, like if it crashed.
Why is this happening? I was quite cautious, and both interiors suffered no damage.
From what I can tell, the one that had a perfect screen (with its original interior) seems to have felt in water. At least the interior has a little bit of something white in some part of its frame and in the chips that were there.
But the screen seemed to work just fine, so putting a good interior there should work, no?
Any idea?
Tried switching them back. Everything in the original hardware, but now both have the same non-booting problem.
Not slow boots, no boot at all. It gets stuck in the samsung model image.
Is it possible that some piece of non-working hardware could have damaged the working one? I've been quite cautious, I don't thing that the handling is the problem.
Weird thing is that if the screen, and the board were working, the only thing there that could be damaged were the sensors, either the ones in the screen, or in the shell.
Hi, thank you for using XDA Assist. The purpose of XDA assist is to point you in the right direction to get help on XDA for your problem. Unfortunately there really is no hardware repair section on XDA. You might try ifixit.
jd1639 said:
Hi, thank you for using XDA Assist. The purpose of XDA assist is to point you in the right direction to get help on XDA for your problem. Unfortunately there really is no hardware repair section on XDA. You might try ifixit.
Click to expand...
Click to collapse
Thanks for the sugestion.
I didn't knew if it was totally an hardware fault, nor where to ask.
I'll try there
I bought a new tablet and the specs were great but there was a problem with it. It kept freezing every now and then. I talked to the seller and he insisted that do an upgrade which I refused to do because it causes a lot of problems. They refused to negotiate anything until I do the upgrade so I did it. Everything went well when I burnt it but once I put the sd in the tablet and the screen turned white then started fading into black around the edges until it all became black. After a while it turned off so I took the sd out and turned it on and I've heard the sound that plays whenever I turn it on but the screen was white and then black just before.
The tablet is on I'm sure of it but the screen doesn't show anything. It's not off though. I mean there's a light coming out of it. I tried the power and volume buttons but when it turns on the screen doesn't show anything.
When I connected the tablet to the computer it was normal. My previous data was deleted which means that the flashing worked I think because it looked like it was formatted. Everything is fine except for the screen.
I'm sorry for the long post but all the other solutions I found were related to dropping the phone or something and even the ones related to the firmware were different. I hope you can help me with this specific case. I can upload photos or a video if that would help.
Thanks in advance.
Hello and thank you for using XDA Assist,
please ask in our Android Q&A section:
Android Q&A, Help & Troubleshooting
The experts there should be able to help you.
Kind regards & good luck
Trafalgar Square
XDA Assist
Hi everyone, first I sincerely apologise if I'm posting this in the wrong forum (and if so please direct me to the proper place). If it's okay, here goes:
I would greatly appreciate your help. I have this Chinese made car Headunit in my car (running android jellybean 4.2.2). I've had it for about a year and a half or so. A couple of months ago, the screen began to be unresponsive - after boot up. It is quite frustrating, as the unit itself is actually working.. but the screen just does not respond. This happens randomly! Sometimes you have to restart it several times before it works normally. And it does work normally sometimes, though there is no apparent order. It seems to just be quite random. I tried using one of the screen calibration apps from the appstore. It seemed to make a very minor difference (or perhaps not!). The problem is still very much there.
Sometimes, while it's unresponsive, if you touch an app icon and leave the unit alone, after some time the app would eventually open - though the time it takes to do that greatly varies. At this point, the screen may then work - sometimes normally, but in many cases, abnormally or unpredictably. In some cases it will not work at all.
Please does anyone know what is responsible for this and if/how it can possibly be fixed?
One more thing I should add is that I suspect this started to happen as a result of an unsuccessful attempt to root the device. Could that be the reason... and/or is there any hope... i.e. can it possibly be fixed?
I have also done a factory restore.. but it still does this! Please help
Listner said:
Hi everyone, first I sincerely apologise if I'm posting this in the wrong forum (and if so please direct me to the proper place). If it's okay, here goes:
I would greatly appreciate your help. I have this Chinese made car Headunit in my car (running android jellybean 4.2.2). I've had it for about a year and a half or so. A couple of months ago, the screen began to be unresponsive - after boot up. It is quite frustrating, as the unit itself is actually working.. but the screen just does not respond. This happens randomly! Sometimes you have to restart it several times before it works normally. And it does work normally sometimes, though there is no apparent order. It seems to just be quite random. I tried using one of the screen calibration apps from the appstore. It seemed to make a very minor difference (or perhaps not!). The problem is still very much there.
Sometimes, while it's unresponsive, if you touch an app icon and leave the unit alone, after some time the app would eventually open - though the time it takes to do that greatly varies. At this point, the screen may then work - sometimes normally, but in many cases, abnormally or unpredictably. In some cases it will not work at all.
Please does anyone know what is responsible for this and if/how it can possibly be fixed?
One more thing I should add is that I suspect this started to happen as a result of an unsuccessful attempt to root the device. Could that be the reason... and/or is there any hope... i.e. can it possibly be fixed?
I have also done a factory restore.. but it still does this! Please help
Click to expand...
Click to collapse
Greetings and welcome to assist. Unfortunately any modifications made to the system by the attempted root won't be undone by a factory reset. If you try asking here and give the full details of your model
https://forum.xda-developers.com/android-auto/android-head-units
hopefully the experts there can help you
Good Luck
Sawdoctor
Thank you very much Sawdoctor! I have now posted this at the link you kindly provided. Have a great night