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.
Related
Hi all. I'm having an issue with a 727R. I replaced a broken screen and now can't get the screen to stay on. Its a non rooted, factory 2.3.5 phone. When I turn it on, the sghi-727r screen pops up for several seconds and then dissappears, phone vibrates once, notification sounds appear shortly and all touch functions appear to work (by sound and haptic feedback). For all intents and purposes, this phone is on and working perfectly...if you're blind lol. I know the replacement screen works because it works perfectly if I go into download (odin) mode. I've been searching threads and haven't been able to come up with a solution, as most of the other blank screens are from bad flashes. Keep in mind that I am also testing this with the casing removed as it is a repair for a friend (if that makes any difference). Any help or ideas would be greatly appreciated and thanks in advance.
Is the brightness maybe turned ALL the way down? When it finishes booting shine a flashlite on the screen and tell me if u can see text, icons etc...
I'll do that as soon as I get home this afternoon. I could only hope that's all it is, but i'm a little skeptical that I could be so lucky. forgot to mention that I have also odin flashed the stock rom back on just in case of software corruption. I would also think that I would get full boot logo's during the boot sequence, but hey!....its definately worth a shot! I've seen stranger things . Thanks for the quick response.
norm182 said:
I'll do that as soon as I get home this afternoon. I could only hope that's all it is, but i'm a little skeptical that I could be so lucky. forgot to mention that I have also odin flashed the stock rom back on just in case of software corruption. I would also think that I would get full boot logo's during the boot sequence, but hey!....its definately worth a shot! I've seen stranger things . Thanks for the quick response.
Click to expand...
Click to collapse
No worries, keep us informed. I didn't even bother to ask because I just assumed someone at your level who can change a screen would intuitively know to Odin stock... I was right :good:
It a ribbon cable issue when I swap dismantling my SR's I ran into that twice swapped out screen and no issues after
Sent from my SGH-I727 using Tapatalk 2
crashpsycho said:
It a ribbon cable issue when I swap dismantling my SR's I ran into that twice swapped out screen and no issues after
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
So you had display for start of boot and d/l mode? If so, then I'll go no farther until I get another replacement screen.:crying:. Come to think of it, when plugged in and off, the charge symbol shows up for a second and its discoloured (almost like its made of vertical lines that are pinks and grays). You may have just saved me a lot of time. I was leaning toward trying to adb error logs in hopes of finding something. Other than that it was going to be a reflow on the gpu since the phone did do a leap of faith from 6 ft up....and lost lol.
icenight89 said:
Is the brightness maybe turned ALL the way down? When it finishes booting shine a flashlite on the screen and tell me if u can see text, icons etc...
Click to expand...
Click to collapse
No dice icenight. Tried out of hope but its completely black. I was really hoping for maybe a fault that could be fixed with a flash.....whoa is me....looks like I may be sending screen back and getting another. I cant send it out for another day so if anyone has any other ideas, or wishes to guinea pig this unit until one comes in, feel free to chime in. And thanks for the responses so far!
crashpsycho said:
It a ribbon cable issue when I swap dismantling my SR's I ran into that twice swapped out screen and no issues after
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
And the winner is....Crashpsycho! After months of trying to find a replacement, i finally got my hands on two of them for a decent price. Popped one in, odin'd jb stock and voila! perfect phone again. Thanks Crash!
Afternoon all. I know the title might seem like a BSOD post but my situation is different. I've searched but can't come up with anything.
When I turn my phone on, it completes the boot but the screen never appears. How do I know it's on? Three things, the ROM I'm using, Eagle'sBlood I think, has an engine revving theme instead of standard Android chime. Second,the menu, home, back space and search buttons on the G2X body illuminate. Lastly, if I swipe in the area where I think the unlock icon should be, the phone unlocks. If I hold down the power button and wait for the shutdown notice, I can guess the 'Do You want to shut down' and 'confirm shut down' icons and the phone turns off.
I've tried removing the battery, SD card, sim card and rebooting in each variation but with no luck. The phone has been rooted for over a year and so I tried booting into CWM (powerbutton, down volume). I think I'm getting into CWM fully but without the ability to see the screen I can't navigate.
This started happening yesterday. I was listen to Pandora and using a GPS app to track my run. The battery died during. I plugged it in for several hours but haven't seen the screen display since.
Any suggestions? If this is a hardware issue I'll get a new phone but without being able to see the screen, I'm not sure how to diagnose the problem. Other than rooting and changing the ROM, the phone is stock. The issue I had before this is the battery icon doesn't display. It just shows a battery outline with a ?-mark inside. The battery level only shows when the phone is charging and powered off.
Your help is greatly appreciated.
G2X - LG P999DW
Rooted
ROM: Eagles Blood (unsure of version)
maurice
Really sounds like a dead lcd or maybe just the backlights. I don't really know how the backlight works on this phone but typically if there is video but no light you can put a flashlight onto the screen and barely make out the display around the flashlight. Either way it sounds like hardware.
Twitch - Thanks for the reply. I'm not 100% sure what you mean by backlights though. When the phone is on and the screen is not asleep I see lights around the edges but the screen itself is black. For my own knowledge is LCD and 'digitizer' synonymous? I saw another thread describing how to replace the digitizer for $60-75.
I'll try checking it with a flashlight when I get home.
TwitchyEye said:
Really sounds like a dead lcd or maybe just the backlights. I don't really know how the backlight works on this phone but typically if there is video but no light you can put a flashlight onto the screen and barely make out the display around the flashlight. Either way it sounds like hardware.
Click to expand...
Click to collapse
I know there is an opinion thing but what is a good upgrade from the G2x for a non-hardcore user? I rooted and changed the ROM b/c you guys made it so easy to do, not b/c I was looking for the phone to do more than it already does. Up until this, and the battery display issue, and a wifi issue I forgot to mention, I've been happy with the G2x but there is no reason to spend $100+ repairing a 2+ year old phone that I pickup used off CList in Q1, 2012 if I can find something better on the used market for $200
maurice
Yeah I'm not too sure how these phones are set up, I have more experience with lcd monitors and such. But I think it is all in one piece on phones.
If you're looking to upgrade pretty much anything that came after the g2x likely has a lot more to offer in development. Good thing about this phone is everything is an upgrade. I have a samsung galaxy s 4g that's nearly 3 years old and single core but it runs 4.3 like a boss! Aside from GPS...
Flashlight didn't show any screen images. I think the next step is just trying to guess my way into debug mode and connect via uSB to my laptop and retrieve data before dumping the phone or trying to replace the lcd/digitizer. I saw an app mentioned in another post that should allow me to mirror my phones screen on a laptop. We'll see.
TwitchyEye said:
Yeah I'm not too sure how these phones are set up, I have more experience with lcd monitors and such. But I think it is all in one piece on phones.
If you're looking to upgrade pretty much anything that came after the g2x likely has a lot more to offer in development. Good thing about this phone is everything is an upgrade. I have a samsung galaxy s 4g that's nearly 3 years old and single core but it runs 4.3 like a boss! Aside from GPS...
Click to expand...
Click to collapse
Thanks again. Anyone else had this issue?
last chance
Last chance in case anyone has any great ideas. I'll be ordering a new LCD and digitizer (probably don't need both) but would prefer not to spend the coin if that isn't my problem. all suggestions welcome
Hmmm, this an odd and aggravating problem you have here lol. I've ran two versions of eaglesblood, their CM7 version on 2.3.4 and their ICS AOSP version on 4.0.4 and have never heard an engine revving in any boot animation so I'm not sure what rom you're running either. Have you tried the hard reboot? While the phone is on at the home screen (if you think you're there I guess) hold the power button and the volumeUP button and the phone will reboot. I've read on here from a more experienced user before that doing this clears or does something to the caches that makes for a more complete reboot or "reset" of the phone's condition. Try that and see what happens. The only other option I would try to take is to flash a new rom and before doing so doing a COMPLETE wipe (to include format /system) and full instillation of a new rom, gapps and kernel. Can you see any images if you boot into CWM when shining a light on the phone's screen?
Maybe I'm wrong about the ROM. The flash screen shows the android graphic in electric blue and a comet type animation zooms around. During the zooming, the sound is an engine revving. I was using the ROM for 2-3 months before this issue popped up so I doubt it is the cause just wanted to give those more knowledgeable than myself as much info as possible
Pain-N-Panic said:
Can you see any images if you boot into CWM when shining a light on the phone's screen?
Click to expand...
Click to collapse
That's my real problem, I can' t see anything! With the phone on, when I hit the power button and unlock the screen (guessing), the only illumination is the menu, home, back space and search buttons on the G2X body. I can tell from the haptic feedback once the phone is unlocked and I can occasionally guess the proper location to shutdown.
I tried the hard restart (Power, Up) but same result. I've downloaded an app called MobileGo for the computer that displays the phone screen but I can't get USB debugging turned on.
I have noticed another odd issue. With the phone turned on and the SIM card installed, when I call myself from a LAN line it goes straight to vmail. I know the SIM is good b/c I've been using an old nokia candy bar phone with the same SIM while troubleshooting. When re-inserting a SIM card, is there anything the user needs to do for the phone to recognize the SIM? Just wondering if this 'direct to vmail' is another sign of ............something.
Thanks
Sometimes when I take out the sim card my apn gets messed up. Ideally you'd just go into settings and load default apn and it'll work again.
But calling should work.
Seems like a busted screen from everything being described here.
Try connecting to a tv using hdmi... maybe the ROM would allow it to display. Worth a shot.
Sent from my LG-P999 using xda app-developers app
also if you could get airdroid installed on tthe phone you might be able to do something with that. Cool little app that lets you control the phone through your PC using the same wifi network.
Sent from my LG-P999 using xda premium
It's alive!!
My phone is alive, or at least it was.
I followed the directions on the youtube video I found to take the G2X apart and the first thing I noticed was the corrosion on LCD connector. I'd already purchased the LCD so instead of cleaning the old we just replaced it. The new screen worked, unfortunately I couldn't get a signal so we took it apart again to clean off corrosion on all the connectors. I'll let it sit for a few days to make sure everything is dry.
Don't be a fool like me, if you're going to do anything with your phone that might cause it to get wet, especially sweat, put it in a baggie or something. I'll post a follow-up if the thorough cleaning does any good.
I'm pulling for ya man, best of luck!
It works!!
The G2X is up and running again! :good:
Pain-N-Panic said:
I'm pulling for ya man, best of luck!
Click to expand...
Click to collapse
For anyone else that runs across this thread, unless the digitizer or LCD is physically damaged I'd disassemble the phone and check for corrosion before buying new parts. I used the new LCD but that b/c I'm not going through the trouble of returning a $16 item.
Wi-fi still doesn't seem to be working, which is odd. Wi-fi stopped working two months ago, it doesn't even show available networks, but worked for a few minutes when I originally replaced the LCD last weekend. Both antennae are connected but oh well. if I had to choose network vs wi-fi connectivity, I'll take network!
Thanks again for all the help
:good:
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Saad S. said:
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Click to expand...
Click to collapse
Has this happened after you flashed a rom or.. ??
semirr said:
Has this happened after you flashed a rom or.. ??
Click to expand...
Click to collapse
Yes after I flashed the rom but not directly after. But after a good 1 month.
Saad S. said:
Yes after I flashed the rom but not directly after. But after a good 1 month.
Click to expand...
Click to collapse
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
semirr said:
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
Click to expand...
Click to collapse
Is it possible that a driver update could fix this, if so then how?
Saad S. said:
Is it possible that a driver update could fix this, if so then how?
Click to expand...
Click to collapse
Hmm i dont think that a driver could be the problem. And if it is i dont know how you could fix it Google it
I hate to be the bringer of bad news - but your screen is toast. Fortunately you can replace the touch and display components all at once.
http://www.amazon.com/Skiliwah-Digitizer-Assembly-Google-nexus5/dp/B00HN0U168
Here is what you need to perform the repairs - and here are the procedures for disassembly.
https://www.ifixit.com/Teardown/Disassembling+Nexus+5+Display+Teardown+-+liquid+damage/32410
Trust me, it's not that difficult. Unfortunately, it's a bit pricey ($60 for the screen and digitizer), nevertheless much cheaper than a new device or sending your device in for repairs.
Rma
Problem Solved
The screen isn't toast, neither is the digitizer. I have 2 of these phones. The parts which cause problems like this are the main board and the ribbon with the USB connector on it, which also attaches the screen & digitizer to the main board. One was showing lines exactly like this, & also no touch. I put a replacement main board in. Works great now. The other, wouldn't even turn on. I put the main board from the first phone in the second one, it still wouldn't turn on. I replaced the ribbon cable, it turns on and perfectly replicates the issue from the first phone. So now, I have one fully functioning LG Nexus 5, and another which turns on with the same problem as yours. This is good, I started out with 2 of them that were useless to me. So, it appears that your display and touch issues are caused solely by a bad main board. A replacement main board costs somewhere around $75. After swapping stuff around, I have 2 bad main boards, 1 bad USB ribbon & 1 working phone of 2. Not bad, not bad at all.
My Nexus 5 is 6 months old, it hasn't fallen hard, doesn't have a scratch on it, but today the auto-rotate feature was not working. I didn't gave it much thought, but next time I picked up my phone, the whole screen was upside down (see picture attached) and had huge lines all over it, making it very hard to figure out or read anything, and the place were all the buttons should have been were OK, instead of following the change-upside down, so to write a 'A', I have to press 'L' and so on, for everything. Basically impossible to do.
I did a hard reboot to factory settings, and even on the recovery screen everything was upside down, and nothing changed after it.
I have been searching for people with the same issue and I found nearly none or no answers to that thread.
Has anyone experienced the same issue, and what was it in the end?
My phone is under warranty from LG still, but Im afraid if I send it for repair, they will just say is a broken screen, therefore making me pay for it (around 150). If anyone thinks otherwise please say so.
I have found the same issue for other phones (older) and some people say is a broken or faulty Flex Cable. Can this be possible? (I could repair that myself)
Any thoughts on this?
Thanks!
valentinitag said:
My Nexus 5 is 6 months old, it hasn't fallen hard, doesn't have a scratch on it, but today the auto-rotate feature was not working. I didn't gave it much thought, but next time I picked up my phone, the whole screen was upside down (see picture attached) and had huge lines all over it, making it very hard to figure out or read anything, and the place were all the buttons should have been were OK, instead of following the change-upside down, so to write a 'A', I have to press 'L' and so on, for everything. Basically impossible to do.
I did a hard reboot to factory settings, and even on the recovery screen everything was upside down, and nothing changed after it.
I have been searching for people with the same issue and I found nearly none or no answers to that thread.
Has anyone experienced the same issue, and what was it in the end?
My phone is under warranty from LG still, but Im afraid if I send it for repair, they will just say is a broken screen, therefore making me pay for it (around 150). If anyone thinks otherwise please say so.
I have found the same issue for other phones (older) and some people say is a broken or faulty Flex Cable. Can this be possible? (I could repair that myself)
Any thoughts on this?
Thanks!
Click to expand...
Click to collapse
If you have warranty take it to LG.
It will be an expensive way to find out what is fauilty, the motherboard or the screen.
I'm new to this forum and this is my 2nd attempt to get help to solve my problem. I have read ALL the rules posted in the XDA New User Guide - Getting Started On XDA, as well as all of the linked pages that are suggested to read before posting. It was very informative but I'm more confused then ever about the right place to seek help. This is all very overwhelming and I'm afraid I'm going to say something to offend someone or post in the wrong place and get in trouble, or worse, ignored. I suspect I did just that in my last post because I never got a response. I apologize in advance if I have done something wrong.
Ok, I'll do my best to explain my problem. I have an LG K20 Plus (I'll refer to this as my original phone) that I bought, brand new, from T-Mobile in May. In August I cracked the screen but continued to use it because besides the crack, it worked fine. By September the crack had worsened significantly and I decided to replace the outer glass as I had successfully done that with my older LG G3.
In that process, while trying to get that dreadful glue off, I scraped off some of the black stuff under the glue on the LCD which caused a white spot, about the size of a 1/2 dollar, on my screen. Although it was bothersome, the phone itself still worked fine. I continued to use it while I searched for the easiest way to fix it within my budget. After reading posts here and realizing it would work, I bought a used LG K20 Plus (I'll refer to this as my used phone) with a bad esn. The plan was to put my original logic board into the used phone and be on my way. That didn't happen.
When the used phone arrived, I turned it on to verify everything worked. I then put my original logic board into the used phone and turned it on. I saw my orignal wallpaper and was so happy I had my phone back. Then I tried to swipe to unlock and nothing happened. I booted it up a couple more times and still nothing. I connected a mouse via an OTG cable and verified that there were no more obvious issues with the phone except the digitizer. To confirm the dispaly wasn't faulty on the used phone, I put the used logic board back into the used phone it came with and booted it up. The digitizer was back to working again. I ran through as much as I could on a locked phone and the digitizer worked like new.
I, carefully, put my original logic board back into the used phone and, again, no touch capability. Again, I researched this problem to no avail. I realized I was way over my head and I decided to ask for help instead of making things worse by trying to fix it without knowing what I was doing. So, I put the phone in a drawer and asked for help here. That was a month ago. I know you are all very busy and, like I said earlier, I'm sure it's my fault and I messed up somewhere because my post didn't receive any replies.
I can't use my original phone because I have no touch ability and I can't use the used phone because it has an esn lock. At this point I decided to try and (I'm sure I'm using the wrong terminology here) flash the used phone and root it to bypass the bad esn lock. After researching that and seeing the word "illegal" A LOT, I decided I just didn't know if it was legal or not, so I decided to not take the risk of doing something that may get me into trouble.
At this point I decided I didn't have much to lose so I backed up my original phone and, with only the display of the used phone attached, I started the process of flashing it with TWRP and rooting it via this guide https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248 So, it is now successfully rooted but it still has no touch ability. The really weird thing is, while I was in TWRP Recovery mode, the touch ability worked again. But as soon as I rebooted the phone into regular mode, the digitizer stopped working again. I'm so confused and I don't even no where to start looking because I can't define the problem or the exact thing that is failing. I don't even know if it's hardware or software related.
So, I guess my question is, does anybody have any experience with this kind of problem you could share with me. I'd settle for someone being patient enough to explain to me exactly what is going on so I could research it better myself. Asking for help was not my first step. I have been looking and looking for 6 weeks now. I'm way out of my league with this stuff. It's really difficult to find a solution to a problem you don't quite understand. It's a little bit like being told to look up a word in the dictionary to find the spelling.
*LG K20 Plus
*LG-TP260
*T-Mobile
*Rooted
Baseband: MPSS.JO.
2.0c1.2-00012-8937_GENNS_PACK-1.85468.1
I think it's my original ROM
Kernel Version 3.18.31
I flashed TWRP
USB debugging enabled
OEM Lock Off
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
zelendel said:
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
Click to expand...
Click to collapse
I'm so sorry but I have run into a few problems .. firstly, on my phone I have to use a mouse connected via OTG cable because I have no touch ability and my usb connection is set to "charge only". Apparently you can't change that until the phone is plugged in and obviously I need the mouse so I can't connect to computer. I downloaded an app called LogCatX and made a log file but I don't know how to attach a file and when I copy/paste it into the reply it says it is too long and reduce by 30000 characters. Any advice?
HelpNeededPlz said:
I'm so sorry but I have run into a few problems .. firstly, on my phone I have to use a mouse connected via OTG cable because I have no touch ability and my usb connection is set to "charge only". Apparently you can't change that until the phone is plugged in and obviously I need the mouse so I can't connect to computer. I downloaded an app called LogCatX and made a log file but I don't know how to attach a file and when I copy/paste it into the reply it says it is too long and reduce by 30000 characters. Any advice?
Click to expand...
Click to collapse
I think the new touch screen will need a calibration.
PS: i liked how you explained your problem
Sorry for my confusion but I'm not sure if you were telling me what I should do to figure out where the incompatibility issue may be or if you were asking me to upload the catlog so you could look at it and help me. I don't know what a catlog is, nor how to interpret it. At any rate, 6 hours later, I have, finally, figured out how to upload a file. :victory: I've been looking at how to fix a kernel incompatibility issue and I've read you can flash a custom kernel. If I did something like that, would that resolve my problem. Are they specific to the version of operating system your phone has (ie nougat, marshmallow etc) or do you need to use one for your specific phone model? Would flashing a custom ROM do the same thing? And is that model specific or OS specific? Where would I go to find something like that?
NOTE... In looking for differences in my phone to try and figure out where this kernel compatibility issue might be, I noticed that there are two different numbers on the midframe of my phones. I don't know if this means anything. I'm just trying to help someone help me.
zelendel said:
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
Click to expand...
Click to collapse
Hello? Was this the extent of your help? I'm not sure if you were asking me to run a catlog to upload so you could help me figure out what was wrong or if you were just telling me what to do and then moving on. Because if it was the later, all you've done is piled more stuff on my steadily growing mound of confusion. To make matters worse, my posts is showing as getting a response, so, I fear, nobody else will look at it and I will be left in the same place as before. If someone happens upon this post, could you give me advice that will actually help me solve my problem, along with instructions on how to do whatever I need to do. Thank you in advance. Until then, I'll be anxiously awaiting your reply....