Related
Basically about 2 months ago I rooted the phone and put in cyangen mod, everything was fine until the touch screen stopped working. Most of the time it was brief but sometimes the touch screen just wouldn't work for a whole day and then start working again. Thinking I had done the root wrong I unrooted the phone back to it's orginal. However the problem still showed up despite that. I recently updated it to the donut update, and that's when the problem got worse. Now the touch screen won't work and when I go to the contacts using the trackball I get an error. And anytime i recieve a phone call I get the same error. Thinking it was a software problem and factory reset the phone and scaled it back to rc29. But still the touch screen doesn't work, and now because of that I am stuck on the setup screen at the beginning which ask you to touch the android to continue (which I can't). I have wiped and factory reset the g1 many times, and usually that has made the touch screen work again, but now it seems to not work at all. I deducted over the last couple of days that it must be the power adapter causing all of this. Since I got the touch screen working yesterday and had no problems the entire day. Then a hour after I put it on the charger the touch screen stopped working again and hasn't worked since. Is there anything that can be done at this point to fix it? I read somewhere about a script that makes the g1 touch screen work again but haven't been able to find it.
Same problem
I'm having a near identical problem. Most all of the symptoms are the same - except my touchscreen has only worked for a few seconds on one occasion after the initial failure. I've tried wiping, and about 3 different mods (JaCx, Cyan, Enomther). None have helped, and currently I'm stuck at the same point where it's asking me to touch the Android to begin, and I can't. The only difference is that I didn't unroot. So I'm going to try a few more roms, but I doubt I'll have any luck. My phone was also put on a charger that wasn't made for the g1. I began to notice the problem thereafter. Not sure why, but that certainly seems like the only reasonable variable which could be causing this.
Anyone out there have any ideas? It'd be much appreciated.
Have you guys dropped your phone recently? I'd like to share my story as well. Two weeks ago, I dropped the phone on hard tile while it was still in its leather/suade case. I picked it up and instantly found the touch capabilities were gone (with screen open or closed). After many soft resets and not knowing how else to fix it, I also decided to revert back to rc29 from cyanogenmod. Still no go, after being stuck at the setup screen. I disassembled the phone, using the G1 service manual, to make sure none of the ribbons were knocked loose and examined the lcd and digitizer for any cracks. No problems that I could see. Disassembled, and reassembled the phone a few more times and still with no avail.
If you were one of the first to receive a g1, such as myself, oct 22nd is the last day of your 1 yr warranty. So give t-mobile a call, and submit a claim before then if you want to take advantage of it. Make sure you reflash to stock image, and that there are no signs of visible damage on the phone or else the warranty will be void. Good luck.
Edit: If your phone's touch screen is working at random times, I'm suspecting its a hardware problem, most likely a damaged or worn out flex cable from opening and closing the screen. Try slowly opening the screen and touching the screen at the same time to see if anything happens.
When I was waiting for my G1 I came on this forum (Had a Diamond before so knew about it anyway) and found a topic discussing problems like this... If you have an Early G1 then I'm guessing this is the problem...
There is some sort of design flaw with the ribbon cable connecting the Touch Screen to the Mainboard catching onto the sliding mechanism. This eventually destroys the cable and causes the touchscreen to stop working. On Later models they've fixed it by taping the ribbon cable down instead of letting it hang loose.
In short... you need to unroot your phone and take it back to T-Mobile.
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
gat0rjay said:
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
Click to expand...
Click to collapse
I realize this is an old thread but did you ever get the issue figured out? My phone did this just last night
Alright as suggested earlier in the thread it was a hardware issue. I found that my touchscreen had become unplugged and was causing the errors.
Sorry to bring this guy back from the dead but I figured I would educate a few people one a common touch-screen problem.
Yeah, 90% of the time it's the adapter you're using. Being a G1 owner with lots of mini-USB chargers i found the same problem. Also being a tech rep at t-mobile, i've had lots of calls revolving around this and fixing it.
The G1 uses a 1000mA charger (1A). For me, the touch-screen going haywire/unresponsive seemed to get more severe as the the chargers specs went lower. An old Motorola charger at 500mA was ridiculous. Talking to customers with the exact symptoms and hardware, eventually lost all functionality of the touch screen.
On a side note, it's not just the G1 that has problems with the wrong charger. A linksys router I have has a standard power port connection type in the back but requires a bigger amp adapter. hooking the wrong one up will cause complete failure. In many situations, not enough energy is just as detrimental as too much energy. One last example: Take a big 10" sub driver, hook it up to a crappy 300W amp, you get an overheated coil and eventually a busted driver.
So, lesson is, just because it fits doesn't mean it's safe to use. I never mix and match adapters with any device ever because of the risk of damage.
So its been about a year and half since I received this phone for my birthday, and from this moment on, I am 90% sure that these companies design these phones to fall apart after a while so you buy a new one.
Please to not be intimidated by the length of the problems, I really doent want to waste a $600 nice phone. Please help.....
List of problems:
So on one random day, while I was using my phone with EnergyROM sense 6.1 (Not even 6.5 (Windows 6.5.5)) the phone stopped rotating when I flipped the keyboard, as in the screen will not rotate when I try to use the keyboard. The touch screen also becomes uncalibrated, and even when I recalibrate it, it still acts very funky (have to click lower than button or higher, depending on its mood). I did absolutely nothing different with my phone that day, but I did not call my phone dead right away, so I decided to update the ROM with the latest sense 6.5 ROM to see if the OS is corrupt or over-cached. This did not fix the problem.
Also, another very weird thing is the phone's screen will illuminate (I guess backlight), but no picture will show when turned on after sleep mode, and I have to click the top button again to sleep and awake it to get a picture. When flipped, the screen doesn't even fully illuminate, and literally dies down to a black screen (half of the pixels are bright, and then it just fails).
Any help would be very appreciated. What I am thinking of is wiping the phone 100%, and not even leaving a rom on it. I heard there is a command that deletes the junk off your phone from a previous ROM to your updated ROM is clutter free. Any other suggestions?
Edit: I hard reset my phone, and nothing is fixed; I still cannot flip screen into landscape mode.
The "command" you are talking about is called "task 29", look for it in the ROM section.
It sounds like hardware problems, i've had mine for about 1 year and a half as well and no problems besides a couple of scratches.
The flex cable connecting LCD and board might be out of order.... I had the same issue.
palmwangja said:
The flex cable connecting LCD and board might be out of order.... I had the same issue.
Click to expand...
Click to collapse
Yeah I heard about that problem. I will first task 29 it, but are there any guides to take apart and fix the flex cable, or even just unplugging it and plugging it back in?
Also, what did you do with your broken phone? Did you buy a new one or get it fixed?
Thanks for the feed back both of you.
my X1 also aged same as yours and it still runs flawlessly now. so it might depends on how you used and keep it
as for the "wiping off the phone" its called task 29, and is encouraged to do before you flash a new ROM, have you did it before flashing energyROM?
rhadrio said:
my X1 also aged same as yours and it still runs flawlessly now. so it might depends on how you used and keep it
as for the "wiping off the phone" its called task 29, and is encouraged to do before you flash a new ROM, have you did it before flashing energyROM?
Click to expand...
Click to collapse
No, but I just did now, but it seems to be a hardware problem because nothing seems to be working properly still. This is some serious BS because I am very over protected with this phone, just to prevent stuff like this to happen. I have never dropped it ONCE, and it seemed to just wear out by itself. The lenses covering the camera is cracked also, and the screen is all screwed up, and I didnt do absolutely nothing abusive to it, I am 110% sure of this.
Any suggestions on how to fix hardware/ ribbon connected to the screen problem?
Order a new cable and replace it.
If you search on Youtube for the video on how to disassemble x1 there is a complete guide that shows you. Its pretty easy and all you need to do is, take the flex cable out and carefully plug it back in. Then carefully put your X1 back together and hopefully you issue will be fixed. If it still persist, then try and get the flex cable changed.
Since the last few days I've been getting some strange issues with my touchscreen. Sometimes parts of the screen (or the full screen) do not respond, and even the softbuttons are affected. When I take the phone out of my pocket, it either responds normally (I use pattern lock) or tries to use the emergency dialer or emergency contacts, and sometimes even tries to call a number from the emergency dialer (number 2 and luckily not 112..)
When in the launcher, it sometimes opens an app (like my calendar) and slowly scrolls either sideways or vertically. Turning the screen off and on again once or twice usually solves it for a (short) while.
I've already read some threads about it and ruled out the following causes:
The phone is not connected to any charger when this happens.
It still happens after cleaning the screen (just with a cloth, no liquids)
It still happens after disabling CPU Tuner. I didn't overlock the system, but used some custom power settings and different governors which apparently can also affect this behaviour.
The battery is still original since nowadays I prefer to use external chargers instead of buying a big battery for every new phone
The only things that changed recently are:
I installed the OwnCloud app, but that doesn't seem related.
We moved to another office building, in which the carpet generates more static electricity.
I gained some weight which may put a bit more pressure in my pant pockets than before
It started happening a few days ago, after using the .215 ICS leak for a few weeks without issue. I seem to get the problem less at home than I do at work, which makes me think it's either the static electricity or CPU governor (since battery percentage is lower by the time I get home again, so it might use a different governor). However, I've been using CPU Tuner for quite some time before this issue started, and the issue persists after disabling it.
So I am guessing it's any of the following causes:
Static electricity
Keeping the phone in my pant pockets which may put some pressure on the screen
A problem with the battery or screen somehow (moisture?)
Some other hardware issue
Some software issue
Does anybody have any tips or other ideas about this? Thanks in advance.
Edit: I enabled some development options to show touch pointer location (white dot) and trails. Screenshot added. Phantom touches seem to be focused in the bottom center part of the phone, which is probably around where I grap it when I take it out of my pocket. Trails usually disappear the next time you touch the screen, but in this case the trails kept growing / adding. I made some real swipes (upper half of the screen) and they 'stuck' without the phone responding to them (the application did not scroll) due to the parallel phantom touches in the bottom. In this case the phantom touches blocked my real input, in other cases they cause some behaviour (scrolling etc.). However, sometimes when the screen is not responding, there are no phantom touches visible in this display mode.
Edit 2:The no-touch input problem seems to be 'triggered' most of the time I open the keyboard. Sometimes this is followed by the phantom touches, but usually they start occuring in the portrait mode lock screen.
Sjaakbanaan said:
Since the last few days I've been getting some strange issues with my touchscreen. Sometimes parts of the screen (or the full screen) do not respond, and even the softbuttons are affected. When I take the phone out of my pocket, it either responds normally (I use pattern lock) or tries to use the emergency dialer or emergency contacts, and sometimes even tries to call a number from the emergency dialer (number 2 and luckily not 112..)
When in the launcher, it sometimes opens an app (like my calendar) and slowly scrolls either sideways or vertically. Turning the screen off and on again once or twice usually solves it for a (short) while.
I've already read some threads about it and ruled out the following causes:
The phone is not connected to any charger when this happens.
It still happens after cleaning the screen (just with a cloth, no liquids)
It still happens after disabling CPU Tuner. I didn't overlock the system, but used some custom power settings and different governors which apparently can also affect this behaviour.
The battery is still original since nowadays I prefer to use external chargers instead of buying a big battery for every new phone
The only things that changed recently are:
I installed the OwnCloud app, but that doesn't seem related.
We moved to another office building, in which the carpet generates more static electricity.
I gained some weight which may put a bit more pressure in my pant pockets than before
It started happening a few days ago, after using the .215 ICS leak for a few weeks without issue. I seem to get the problem less at home than I do at work, which makes me think it's either the static electricity or CPU governor (since battery percentage is lower by the time I get home again, so it might use a different governor). However, I've been using CPU Tuner for quite some time before this issue started, and the issue persists after disabling it.
So I am guessing it's any of the following causes:
Static electricity
Keeping the phone in my pant pockets which may put some pressure on the screen
A problem with the battery or screen somehow (moisture?)
Some other hardware issue
Some software issue
Does anybody have any tips or other ideas about this? Thanks in advance.
Edit: I enabled some development options to show touch pointer location (white dot) and trails. Screenshot added. Phantom touches seem to be focused in the bottom center part of the phone, which is probably around where I grap it when I take it out of my pocket. Trails usually disappear the next time you touch the screen, but in this case the trails kept growing / adding. I made some real swipes (upper half of the screen) and they 'stuck' without the phone responding to them (the application did not scroll) due to the parallel phantom touches in the bottom. In this case the phantom touches blocked my real input, in other cases they cause some behaviour (scrolling etc.). However, sometimes when the screen is not responding, there are no phantom touches visible in this display mode.
Edit 2:The no-touch input problem seems to be 'triggered' most of the time I open the keyboard. Sometimes this is followed by the phantom touches, but usually they start occuring in the portrait mode lock screen.
Click to expand...
Click to collapse
clean you phone with an air duster than a alcohol swab make sure you dry it quickly and use 72% not 90%. make sure you get the corners... get a screen protector and apply that as well. then sbf to 217... and wipe data,,,, that should work.
if not it could be the ribbon cable,,, it may be frayed...
how to fix
http://forum.xda-developers.com/showthread.php?t=1584260
where to get the part
http://cellphone-repair-shop.com/motorola-droid-4-lcd-screen/
myfishbear said:
clean you phone with an air duster than a alcohol swab make sure you dry it quickly and use 72% not 90%. make sure you get the corners... get a screen protector and apply that as well. then sbf to 217... and wipe data,,,, that should work.
if not it could be the ribbon cable,,, it may be frayed...
how to fix
http://forum.xda-developers.com/showthread.php?t=1584260
where to get the part
http://cellphone-repair-shop.com/motorola-droid-4-lcd-screen/
Click to expand...
Click to collapse
Thank you, let me try that. Couldn't find the right alcohol pct. so I'd have to use some generic screen cleaning liquid, would that be okay as well?
My screen was having issues too. So I turned the dot thing on from the dev part as well. The dot seems to freeze as I'm opening my keyboard. And the dot stays frozen in place until I close the scree again. Any ideas on how to fix it? Also if the screen is open and I touch a spot nothing happens, but then when I close the screen it will sense correctly where I touched while it was open.
Sounds like the same problem, so I'm getting the feeling it might be due to the connectors rather than the screen digitizer itself. After cleaning it, I didn't have any issues for a while, but they started occurring again now.
The replacement part is not available right now, a bit expensive, and excludes the price for the required tools which I don't have yet. Warranty may be tricky as I didn't get my phone from Verizon directly. So if it turns out to be a connector issue I will say goodbye to the Droid family and just get another non-QWERTY phone.. at least until Motorola starts selling them (as 'Milestone' since 'Droid' is a Verizon brand) in Europe again. The Droid 4 is the best phone I ever had, this is potentially making it unusable for me though. Glad I didn't order a Lapdock yet!
Motorola will repair your phone for 168... out of warranty and all... I found this cheaper and easier then fixing it myself and guaranteed done right in 5-7 days..
Sent from my DROID4 using xda app-developers app
Mine is still within the one year warranty. So I want to send it in. But I'm afraid they will check for the root stuff and they will consider voiding my warranty because I was rooted. I unrooted and did a factory reset to see if it would fix the issue. So this is my only chance left. I heard clearing the data wouldn't remove the qe process they use to know that I'm rooted. So I'm not sure if its worth the chance.
Flash SBF restores everything to my knowledge. No way to see what happened before the SBF flash.
I read in the original post for the DROID 4 ICS root tool that a sbf will not remove the part that says you were rooted at one point. I checked that first. An sbf flash is really easy. I was really hoping that it would work.
they dont take the time to check that stuff... if you sbf they wont know a thing...
bty found what u need on the cheap
Motorola DROID 4 XT894 Flex Cable Ribbon 27$
http://www.ebay.com/itm/Motorola-DROID-4-XT894-Flex-Cable-Ribbon-/150849219594
If they don't check it then why should I even bother? Does an sbf change something a factory reset doesn't? I've already reset it. I'll look into the fix though. It will depend on if I have the tools to do it or not.
SBF/fastboot will revert rom changes.
About that ribbon cable how would that work as the lcd is fused to the cable?
The Old One said:
SBF/fastboot will revert rom changes.
About that ribbon cable how would that work as the lcd is fused to the cable?
Click to expand...
Click to collapse
Cant be... it is glued in place and has connectors... how else could he sell you the cable by itself... http://www.ifixit.com/Teardown/Motorola-Droid-4-Teardown/7759/1
Just to weigh in on the whole root checking thing, SBFing or fastbooting back to stock DOES NOT remove evidence of root. qe still picks it up somehow in stock recovery.
That being said, they cannot void your hardware warranty for software modifications, it's the law (in the U.S.)
Of course, if you somehow softbrick your phone, they have no obligation to help you.
Edit: Just to clarify, I tried this myself just this morning. Full SBF back to stock + a factory reset, and qe shows 0/1, which indicates currently unrooted but previously rooted. No idea how their security works, but it does.
podspi said:
Just to weigh in on the whole root checking thing, SBFing or fastbooting back to stock DOES NOT remove evidence of root. qe still picks it up somehow in stock recovery.
That being said, they cannot void your hardware warranty for software modifications, it's the law (in the U.S.)
Of course, if you somehow softbrick your phone, they have no obligation to help you.
Edit: Just to clarify, I tried this myself just this morning. Full SBF back to stock + a factory reset, and qe shows 0/1, which indicates currently unrooted but previously rooted. No idea how their security works, but it does.
Click to expand...
Click to collapse
your right but most ppl dont inspect the phone that hardcore... it takes time, and time is money
Yes
Sent from my DROID4 using xda premium
myfishbear said:
your right but most ppl dont inspect the phone that hardcore... it takes time, and time is money
Click to expand...
Click to collapse
I agree it's probably not anything most people need to worry about... I still plan on sending my D4 in before the warranty is up, I've been having terrible wifi + 4G drops, even on stock (that's why I fastbooted in the first place)
I am a bit nervous though, because I've heard horror stories about Moto replacements. That being said, if Ops phone is under warranty, I'd send it in rather than trying to repair it. If it isn't under warranty, then I'd go for the flex cable, the Moto phones are built well and reasonably easy to work on.
Sent from my Galaxy Nexus using xda app-developers app
I probably have some kind of warranty with the seller, not with Moto directly as I have no way of obtaining a QWERTY phone from them (they don't sell those in Europe for some reason). But I really can't miss my phone for an extended period of time, so I'd either need to switch to an old one while I'm waiting, or get a new one.
Since I don't have the tools available to open the phone properly and I don't want to spend any more money on this thing, I'll probably sit it out until it breaks. For now, switching the screen on and off one or two times seems to 'solve' it.
Sjaakbanaan said:
I probably have some kind of warranty with the seller, not with Moto directly as I have no way of obtaining a QWERTY phone from them (they don't sell those in Europe for some reason). But I really can't miss my phone for an extended period of time, so I'd either need to switch to an old one while I'm waiting, or get a new one.
Since I don't have the tools available to open the phone properly and I don't want to spend any more money on this thing, I'll probably sit it out until it breaks. For now, switching the screen on and off one or two times seems to 'solve' it.
Click to expand...
Click to collapse
all u need is a $0.60 guitar pic and a t5 screwdriver(can find at home improvement store). none of those silly tools they try to sell you help that much
myfishbear said:
all u need is a $0.60 guitar pic and a t5 screwdriver(can find at home improvement store). none of those silly tools they try to sell you help that much
Click to expand...
Click to collapse
I still have tons of guitar picks so I just ordered a Torx set for this and future problems.. hope that pushing the connector around a bit can solve it already.
Hey Xda,
I'm certainly not a newbie to flashing/modding but this one puzzles me quite a bit:
Today I got a Galaxy Note from a good friend of mine, the device is still running on stock ROM and has never been rooted.
When I try to boot up the device you'll hear the usual boot sound and after a while the softkeys backlights will light up, while the screen won't. My friend reported to me that he had issues in the past connecting the device to any given windows PC, as they won't even recognize the device. I however can't verify this as I'm using arch Linux on almost all of my workstations.
The main objectives are:
- backing up the entire internal storage, because my friend produces music and there are lots of samples/unfinished tracks on this device
-eventually get this device working again.
The main problem is deciding whether the device has defective hardware or just somehow screwed up firmware.
The gameplan so far is backing the device up via adb if nothing else is working and then reflash the whole damn thing, if there is still no improvement I guess the hardware is to blame.
Any constructive advices on your end? It would be much appreciated as this seems to be a fairly common problem. Anyways I'll keep you up to date
Are there any touch haptic responses on the screen? Then this could be an issue of corrupt or wrong bootloader installed.
Try booting into recovery and/or download mode.
And check for a battery icon while charging and off.
A problem with the boot loader on stock android without even root sounds unlikely.
If the screen stays black, i thinks its very likely that the connector from the display came loose.
lucky you, the note is not that hard to take apart, and the connection should snap back in no problem. In fact, i think that should be stap one, check the connection.
About connecting to the pc, that could be more difficult. From the description i think the usb board is in need of replacement. Also a relatively common, cheap and easy fix, but make sure you get the same revision as the one you have now.
---------- Post added at 02:05 AM ---------- Previous post was at 01:49 AM ----------
Another idea would be to connect an mhl cable and use that to see what should be on the screen. This depends on the usb port being fine, but may be worth trying anyway.
So for the purpose of continuity I'll post any useful links I used along the way.
At first I'll back the device up. This will be no problem as adb works just fine on my Linux box with this device. The next step would be trying this:
http://forum.xda-developers.com/showpost.php?p=25202942&postcount=7
If that does not work I'm assuming defective hardware/or bad connection due to dust. I'll disassemble the device like this:
http://m.youtube.com/watch?v=N6CJy7...kZ4-Yg&usg=AFQjCNGp378LsVHTIBkf62THSVDqsWM7uQ
And clean up the connector/ribbon plug with isopropyl alcohol
I managed to reset my old account so I'll be posting from this one, not to cause any confusion...
if you are getting charging animation
or galaxy note logo on bootup
then you need to flash an alternate kernel or reflash original
else forsure there's something went wrong with your hardware
Note 9 Exynos Purchased in India.
But my audio has stopped working.
I spent days and nights trying to see if anybody else has faced a similar situation and could not find much info.
XDA gurus my last hope.
Samsung's support is bad. here. The less said the better.
I finally pulled the trigger and did a factory re-set. That too did not help.
Here is a funny thing.
I can shoot pictures but I can't shoot Video.
If I plug my headphones in nothing happens.
The only thing that works is blue tooth headset but not for calls.
If I can figure out what parts need changing I can order them. And try replacing them.
The only Part I could find is this.
https://shopee.com.my/Krcb-98512-Fo...CUD07XjfwNIQZ3inXJADNm-X84Ea9PHVLt7NMgOSL74Fo
Update:
I finally tracked the problem down to the latest update. Soon after the update. Phone started to get hot. And also charging took longer than normal. Audio slowly stoped working.
You can try the following diagnostic tools, if anything to confirm if you have a hardware issue:
1) Dial *#0*# on you dialler and you get Test Mode from where you can test various hardware, including audio
2) In Samsung Members app go to Phone Care and select Interactive Tests. There you can find another set of hardware diagnostics that you may find useful.
Good luck!
Sent from my SM-N960F using Tapatalk
Done sir.
Im pretty sure the Audio IC is blown.
Just need to confirm the part number to order.
kta said:
You can try the following diagnostic tools, if anything to confirm if you have a hardware issue:
1) Dial *#0*# on you dialler and you get Test Mode from where you can test various hardware, including audio
2) In Samsung Members app go to Phone Care and select Interactive Tests. There you can find another set of hardware diagnostics that you may find useful.
Good luck!
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
Just in case somebody else has this problem I am sharing info as I find it.
It would seem the IC needed is MAX98512
And you can download the full Note 9 schematic from my google drive here.
https://drive.google.com/file/d/15MPFlmcnupHqU_4ZAkPOyWo5QeBj9XI-/view?usp=sharing
How do I figure out which IC to change. 98512 or 9896B
Could not find any info online. Other than 98512 is an audio amp and 9896B is audio IC.
Further reading & research seems to link this to the latest Android 10 update.
A lot of other people have faced similar problems on various phones. And 90% of the time the only solution is to have the mainboard replaced.
Just google android 10 updates broke my phone.
So far I have done 3 factory data re-sets. Each time trying something new like this time I did not update from backup. Still, my max98512 seems to be the problem.
I have placed an order for new chips from aliexpress.
Not being able to roll back really suck.
So I got this idea. To figure out if its a software issue or a hardware issue. Need to see if the device drivers are loading or not.
This info can be found by bootin up into recovery mode then view log. Open log last-kmsg
Its a pain to read. And I have not figured out a way to access the data via adb most of the instructions do not work on non rooted phones.
Can anybody with a working note see if the get this message in their log.
star-madera sound: Failed to parse codec DAI for uaif -517
@34%
max98512 6-0039 failed to read [0x0402][-121]
[max98512 _debug] max98512_i2c_probe: failed to read 0x402 [-121]
max98512: probe of 6-0039 failed with error -121
@56%
ALSA DEVICE LIST
no soundcards found
warning unable to open console
I need to know what is the text that shows up on the line after ALSA DEVICE LIST on a working phone.
The TWO ICS handling audio are max98512 and CS47L90 Ignore my earlier comments Indian Note 9 is different audio IC.
By this I can figure out if its a file corruption issue or a hardware failure issue.
RonChinoy said:
So I got this idea. To figure out if its a software issue or a hardware issue. Need to see if the device drivers are loading or not.
This info can be found by bootin up into recovery mode then view log. Open log last-kmsg
Its a pain to read. And I have not figured out a way to access the data via adb most of the instructions do not work on non rooted phones.
Can anybody with a working note see if the get this message in their log.
star-madera sound: Failed to parse codec DAI for uaif -517
@34%
max98512 6-0039 failed to read [0x0402][-121]
[max98512 _debug] max98512_i2c_probe: failed to read 0x402 [-121]
max98512: probe of 6-0039 failed with error -121
@56%
ALSA DEVICE LIST
no soundcards found
warning unable to open console
I need to know what is the text that shows up on the line after ALSA DEVICE LIST on a working phone.
The TWO ICS handling audio are max98512 and CS47L90 Ignore my earlier comments Indian Note 9 is different audio IC.
By this I can figure out if its a file corruption issue or a hardware failure issue.
Click to expand...
Click to collapse
Following here, my father Note 9 same problem and he think it very very bad work by Samsung to put out such devices to break after only 1.5 year of use, His old Nexus 4 is still working and running Android 9 custom ROM thanks to XDA Developer!
Samsung have done something bad, and it is to charge same amount to repair the phone as buying a new phone
So instead of repairing dead audio Note 9 at Samsung its better to do it unofficially I think :silly:
silvaBR said:
Following here, my father Note 9 same problem and he think it very very bad work by Samsung to put out such devices to break after only 1.5 year of use, His old Nexus 4 is still working and running Android 9 custom ROM thanks to XDA Developer!
Samsung have done something bad, and it is to charge same amount to repair the phone as buying a new phone
So instead of repairing dead audio Note 9 at Samsung its better to do it unofficially I think :silly:
Click to expand...
Click to collapse
How much did they quote because one guy was quoted 18,000 I was quoted 26,500,
Yes I agree we save up for years or take out 2-3 year EMI to pay for these phones and then they don't last even 2 years. Samsung can not even explain why it failed. My Water sensor is not tripped. Phone has never been dropped or has a single scratch on it.
Im now using a 5 year old one plus that saw my daughter thru school and collage and its still going strong. Even after multiple drops in water.
Anyway if your interested I am importing all the Audio ICs 10 of each and plan to repair it myself.
The problem with getting outside guys to work on it is they try to reball the existing IC. And if that does not work They put in used parts.
Lets see if this is a s/w issue or a hardware issue if we can get a last_kmesg log file from a working phone we should be good to go.
I found this in the log.
audio_hw_proxy_9810: fast_out-proxy_open_playback_stream: PCM Device is not ready with Sampling_Rate(48000) error(cannot open device '/dev/snd/pcmC0D2p': No such file or directory)!
I really want to go back to Android 9. I don't even mind triping my Knox now.
RonChinoy said:
So I got this idea. To figure out if its a software issue or a hardware issue. Need to see if the device drivers are loading or not.
This info can be found by bootin up into recovery mode then view log. Open log last-kmsg
Its a pain to read. And I have not figured out a way to access the data via adb most of the instructions do not work on non rooted phones.
Can anybody with a working note see if the get this message in their log.
star-madera sound: Failed to parse codec DAI for uaif -517
@34%
max98512 6-0039 failed to read [0x0402][-121]
[max98512 _debug] max98512_i2c_probe: failed to read 0x402 [-121]
max98512: probe of 6-0039 failed with error -121
@56%
ALSA DEVICE LIST
no soundcards found
warning unable to open console
I need to know what is the text that shows up on the line after ALSA DEVICE LIST on a working phone.
The TWO ICS handling audio are max98512 and CS47L90 Ignore my earlier comments Indian Note 9 is different audio IC.
By this I can figure out if its a file corruption issue or a hardware failure issue.
Click to expand...
Click to collapse
hi, please guide me how to read logs. I have note 9 SM-N960F on android Pie Indian firmware.
@34% it is showing some frequency logs and 56% about some gamma values and pannel .
---------- Post added at 11:25 AM ---------- Previous post was at 11:04 AM ----------
here i found this method on samsung website to dump the logs.
SysDump tool:
Launch the Phone app.
Enter *#9900# to launch the SysDump tool.
If the Debug Level is Disabled/LOW, tap to select MID. This restarts the device.
Reproduce the issue that you would like to troubleshoot.
Repeat steps 1 to 2 to launch the SysDump tool.
Tap Run dumpstate/logcat.
Tap Copy to sdcard. This copies a timestamped .log file to the folder /log, which you can access through My Files in your personal space.
You can send the file to Knox Support, using one of these methods:
well found max98512 6-0039
for "ALSA DEVICE LIST" please share pic, it may help to find it.
The way I got to see my last_Kmesg was to go into system recovery i.e. power on with 3 buttons pressed. You get the menu which allows you to re-set the phone or wipe cache partition in that screen there is an option to view logs. From there I read the log.
Its a tiny font and took me 2 hours lol.
But chk this out. Just google Just google android 10 mic fix or android 10 audio problems.
And you will see that a lot of phones have been hit by this.
Not just samsung. But many brands. Some have found solutions some have not.
I think the first step for us is to figure out how to go back to Android 9.
If even after doing that the problem is not resolved then we have to replace the Audio ICs.
I belive the problem was caused by the update. And then it gets bad to the point where it destroys the audio IC.
Pixel phones had a similar problem where the android 10 spoilt sensors at the hardware level.
I was not able to find a directory /log or any files following your steps.
When you google Note 9 audio IC you get this link.
https://www.deviceparts.com/9896b-audio-ic-for-samsung-galaxy-note-9-ori.html
I have placed the order for this along with Max98512 but I can not find any reference to the 9896b IC is any of the Samsung Service manuals.
Lets focus on how to roll back to android 9. Because I think there were some massive changes to how audio is handled in android 10 and that is what spoilt our phones.
Basically due to overheating after the update. It was a crapshoot to see which IC lost contact.
Some people lost on display IC and some on Audio.
My Max98512 IC has arrived.
As to Samsung Claiming offically in writing to me that there were no Audio related problems reported after the update.
Show the lying [email protected]#[email protected]@ this simple google link.
https://www.google.com/search?newwi...TIuMZgBAKABAaoBB2d3cy13aXrAAQE&sclient=psy-ab
Can we use this method to roll back to Android 9 ? I heard rollback is not possible. ?.
Can somebody clarify ?.
https://www.rprna.com/news/how-to-rollback-from-one-ui-2-0-beta-android-10-to-one-ui-1-1-android-9/
it only possible if you have beta version of andriod 10 installed in your phone. if you have updated to stable version of andriod 10 then it is not possible.
Munawar Mehmood said:
it only possible if you have beta version of andriod 10 installed in your phone. if you have updated to stable version of andriod 10 then it is not possible.
Click to expand...
Click to collapse
a. I hope the Deves on XDA can fix this problem and figure out a way for us to roll back.
b. We put enough pressure on Samsung to allow us to roll back. Which I doubt as so many failures suits their agenda of getting you to buy a new phone.
c. We just address the parts that have failed and hope that they last.
==========================
Latest Update:
I was able to get my back cover off. Without cracking the glass or scratching anything it took me an hour but I took it slow on purpose.
Right chuffed with myself. Next step is to chk the speakers with a Multi Meter Then extract the board and inspect it. Water sensors are ok they were not tripped.
The Fingerprint flex was a nightmare to get off in the end it popped off on its own. And the flex nearly tore but did not.
The next step is to try and extract the mainboard and do a physical inspection and look for any damaged parts and to try and locate the Max98512 and the Audio Codec chip.
Im struggling here without the schematics. But my suspicion was right there is heating up all over the board. At the audio and you can see where the solder paste balls have separated from components. I see it near the display chips and near the audio chips.
There are tiny balls of melted solder all over the board.
Everything from the main chips to small components like SMD caps and resistors have over heated and shed these tiny balls of lead all over the board.
Im working without a microscope using a plastic pocket scope we use to read plugs.
Plan is to clean out all these melted balls and then put some flux and re-flow the lead. The Max98512 I will have to lift to see what the heat has done to the pads below.
I can't see any conformal coating on the board. This means if you live in places like India were we see humidity off 80-90% it can wreak havoc with your phone without even tripping the water sensors.
Today's plan is to pull the main board off. Wash it in Iso. Then used compressed air to blow off all the tiny balls of lead. Then fresh flux and lead. And then if I can get it to work. To coat the complete mainboard in a moisture-proof conformal coating.
I can't imagine why they would not coat the boards.
If you open up a Honda ECU after 25 years you will find that the board is still shiny. The lead looks fresh. And the reason is that they use a conformal coating.
And the reason why the audio and display ICs are getting hit the worst is that they have zero heat sinks. Im no expert but why would you run an Audio Amplifier IC with no heat sink. Makes zero sense to me.
============================
If you have an audio problem and are working with the 98512 here are the other parts you will need around it. These are the supporting components.
SCH Part # Part Desc
C8004 2203-009859 / 22000nF,20%,10V,X5R,TP,1608,T (Damaged)
C8002 2203-009858 / 10000nF,20%,10V,X5R,TP,1005,T
L8002 2703-005505 / 1uH,20%,2016,T1,0.043Ohm,42
Top
R8052 2007-007741 / 10KOHM,1%,1/20W,TP,0603
C8006 2203-007796 / 1000NF/1uf,20%,10V,X5R,TP,0603,0.
C8014 2203-008860 / 1000NF,20%,16V,X5R,TP,0603,0.
Btm
C8000 2203-008097 / 100NF/0.1uf ,10%,25V,X5R,TP,0603,0.3
C8002 2203-009859 /22000nF /22uf,20%,10V,X5R,TP,1608,T
C8004*2203-009858 /10000nF / 10uf,20%,10V,X5R,TP,1005,T
C8077 2203-008466 / 0.033nF,5%,16V,C0G,TP,0402,0.
C8003 2203-007621 / 100nF,10%,6.3V,X5R,TP,0402,T0
Thanks guys I solved my problem.
Purchased a Microscope, a soldering station, and a Max98512 AMP IC.
It took me 3 months but I did it.
I did try taking it to a shop. He soldered the IC on so poorly that the phone stopped booting up. And one 10K resistor blew. So decided to do it myself. Samsung Service will not do board level repair. ANd those out there offering this service 90% are uneducated without the right tools for the job.