been through several reboots and taking battery out and resetting the phone. cant figure out if its hardware or software related thats making the touchscreen stop working. i tried going back to Winmo and still touchscreen isnt working. i think the phone got a little wet the day it stopped working, but was in my pocket all day. (not drenched... my pants were just damp). anyway when android boots up i get this...
no irqf_trigger set_type function for irq 190 (kaisergpio)
msm_i2c msm_i2c.0: error waiting for notbusy
would this be something that i could replace and it still work? ive tried taking out the battery and holding down the power button to discharge the phone compeletely. i am running dzo's froyo and the latest 7_26 kaiser nbh. i removed the overclock and nothing seems to help. this is the part i was looking at (http://cgi.ebay.com/HTC-8925-Tilt-TyTN-II-Kaiser-LCD-Digitizer-Touch-Screen-/170469159819?cmd=ViewItem&pt=PDA_Accessories&hash=item27b0c0f38b)
any help is appriciated
It does sound like a touchscreen failure, and moisture is the biggest cause of mobile phone failures, believe me, my workplace can get as many as 230 mainboards a day from repair facilities, most are obvious liquid damaged, and we wash them, dry them and send them back.
However lcd's and touchscreen are a totally different matter, you cannot wash them, that destroys them, so the only thing that can be done is replacement usually.
The link looks to me to be a full kaiser replacement screen assembly, and at a good price too, but be aware that the problem may be the connector itself, where the screen joins the flexi, since most often moisture affects these rather than anything else, due to the small gaps between the pins which are perfect for shorting out when they get wet, if you remove the screen carefully, and closely examine the connectors they may have a fine greyish furry coating, if so a light brush with fine bristle brush should get rid of most of the short, allowing it to work again, if you are going to be disassembling the phone to fix the screen, it's worth trying this first.
You could also try putting the phone in a warm place for a day before doing this, just to make sure it's completely dry.
Got the same problem on froyo, but I didn't got it wet. It looks like there's something bad with froyo, but I don't know what exactly. I think getting back to the stock firmware would help. I will try it tomorrow, because my USB socket is broken for a long bit of time, so I was flashing from SD card, but my reader broke too :/
I had the same problem with touchscreen on froyo with the same errors. I thought my kaiser was going dead, but helps me taking battery out. Now everything is ok.
Don't know if anyone else is experiencing this with their Play but as of a week or two ago the backlight started acting strange. The backlight will randomly stay off when I push the power button with the slider gamepad closed. Only way to make it come on is to pop out the slider. It seems to be random, and if I push on the slider edge slightly with my thumb with the slider closed the backlight randomly flickers, ranging from slight to severe.
The display is still working despite the backlight issues, I can open apps, and use the phone normally but the backlight flickers on and off. Makes it especially hard to use the phone in the dark.
Phone has never been dropped once.
I've replicated this problem with a variety of roms, both custom and stock. It's definitely not app related or even custom kernel related. It happens on a fresh wipe with stock rom with stock kernel. It happens on CM7 with custom kernel.
I'm curious if anybody else is experiencing this. It would tell me if it's just an isolated incident or if others are having this problem.
Sounds like a faulty connection to the backlight to me.
I had the same problem 2 days ago. Then I couldn't get my phone screen on at all!
I sent my phone back to Sony, even thought I bought it second hand. Phoned them up and talked to them. They asked what time of year I bought it so I said around August and then they gave me the address to send it to. Now I'm just waiting to see what happens next.
If your going to send your phone to Sony for repair then make sure you put the fresh firmware back on and un-root your phone as that breaks the warranty (unless they don't know about it)
Hope I helped you. If I did then click the thanks button
Sounds like a faulty ribbon cable to me. (cable that connects the screen to the rest of the phone)
You wouldn't need to drop it for that to go bad, It could just be a case of opening and closing the gamepad or lot.
Yeah good thoughts, most likely the ribbon. That really sucks because I've only had the phone for 7 months, and I've taken excellent care of it. Sounds like a major design oversight.
Mine is probably near complete failure at this point. It's taking a lot more effort to keep the screen on now. Fearing soon it won't work at all.
In hopes that this might help someone else down the line, I was able to fix my problem. Yesterday the screen pretty much quit and I had no choice but to try and solve it myself or buy a new phone.
Using this disassembly video as a visual aid I carefully pulled my phone apart: http://www.youtube.com/watch?v=-3n5ZfkqhzE
You'll need a torx T5 tool to pull out all the screws but they are cheap.
Underneath the phone and jammed into the screen ribbon was a rather thick hair just hanging out. Somehow it buried itself in there. I removed it, unplugged and replugged the screen ribbon and cleaned the dusty inside with a q-tip and reassembled it all together.
It works fine now, so hopefully this helps someone else avoid having to pony up for a new phone. For those under warranty probably best to send back but for those like me with no warranty it's worth the shot.
Like many of you, I've been having some trouble turning on bluetooth and it's been getting more difficult to get the bluetooth turned on. I don't have any other problems with other features, like GPS or wireless connections, but more often than not, I cannot get the bluetooth to turn on unless I reboot and toggle airplane mode a bunch of times.
As the first step in trouble shooting the problem, I decided to go back to a stock ROM since that has seemed to work for others. I deleted all of my user data and formatted system, cache, data and davlik cache before each ROM load. I first tried the stock Gingerbread ROM but the Bluetooth was still not working consistently. I then tried the ICS stock ROM but again the bluetooth did not work correctly. On each ROM, I tested the bluetooth thoroughly by power cycling the phone, using airplane mode, and trying to toggle bluetooth repeatedly. I was able to turn the bluetooth on in each ROM but it would only come on about 10% of the time and there did not appear to be a pattern of reboots or software manipulation that I could do which would cause it to turn on. Nothing seem to work so I suspected there must be a hardware problem.
I opened up the phone tonight and on a hunch, I reseated the antenna (the white antenna on the right side of the phone when it's laying on its face) by removing it and reattaching it to the board by the two ends of the antenna but did not remove it from the middle clip. I'm not sure what happened, but when I restarted, I had no wireless service which made me think I was buying a new phone tomorrow :crying: but the bluetooth was working every time! I opened the phone back up and totally removed the antenna and reseated it. This time when the phone started, I had great wireless signal and the bluetooth worked perfectly. Granted, it's only been a few hours but it's never worked so consistently since I reseated the antenna. No idea if this will last but it seems like in my case, there was an issue with the connection to the antenna. I'm not even sure if that antenna is used for the bluetooth or not.
If this works for the next couple of days, I might try buying a new antenna. If you decide to remove the antenna, make sure that you use a needle nose pliers to remove the two ends of the antenna. You do not want to pull the antenna off by the wire. Also, if you reseat it, make sure there is equal slack on each side from the middle clip because the antenna needs to fit between the two golden lines printed on the case. Otherwise, when you put the case together, it will pinch the antenna. As with all hardware changes, THERE IS A CHANCE THAT THIS WILL SERIOUSLY DAMAGE THE PHONE'S ABILITY TO RECEIVE WIRELESS SIGNAL. I thought for a few minutes I would be at T Mobile tomorrow buying a replacement.
I'll report back if this works long term. Sorry if someone already mentioned this as a solution. I did quite a bit of searching and had never heard of someone trying this.
The attachments show the location of the antenna in the case and the close up of the antenna. If you remove the back cover and unscrew the panel from the back, the antenna is right there.
Bluetooth seems to be a reoccurring issue in a lot of custom roms...for some people anyway.
If you want it to work flawlessly, as well as everything else, there's always stock 4.1.2.
Sent from my Moto X cell phone telephone.....
I tried going back to the stock gingerbread and ICS. I knew that bluetooth worked when I had the stock gingerbread ROM but now in the stock gingerbread ROM, bluetooth no longer turned on consistently. I wiped everything on the phone when I went back to the stock ROM and it just did not work. That's what made me think that there was a hardware problem and possibly a poor or loose connection.
I'm not 100% convinced that reseating the antenna worked because I don't know if bluetooth even uses that antenna but I wanted to post my experience with it. I would go back to a stock ROM first to make sure that it doesn't work there before messing around with the hardware.
My phone is a T-Mobile galaxy s2 sgh-t989
I had my phone on my table, and my air conditioner decided to leak water out of the front, instead of the back. When I woke up, I noticed it, so I took my battery out of the phone. It wasn't completely soaked, but there was a decent amount of water inside the case and sub-frame (think that's what its called). Didn't have rice, since we recently cooked the last of it, so I wrapped my phone parts in some paper towels, and then put in vermiculite to draw our moisture. Once the phone was put back together, it appeared to work fine, but when I would click text messages, it would free up, and most often turn the phone off. Before this problem, my phones WiFi wouldn't turn on (common problem, from what I read). Last night, I did a factory reset, and the WiFi started working. The texting also worked, until the help popup came up (from when you first start using your phones features). When that popped up, it lagged out, and turned off. I did another factory reset, and now the WiFi still works, and the texting works fine, but the phone calling is messed up. I can make a call, and answer a call, but the screen freezes up. After I hang up, it says something along the lines of "android.phone isn't responding" and asks if I want to close it or wait. I was wondering if any of you have any simple solutions. My father works on phones (not for a living), and says that maybe there is still some moisture in it. I, however, think that some of the files somehow got corrupted. Thanks for your time.
I would try a clean install of 4.1.2 with Odin. If it still acts up, it's likely the water damage. And there's not much you can do about that. The phone isn't worth the repair bill anymore, in my opinion. Also... With water, you often fix one hardware component, only to find something else not working.
Good luck!
I've had this tablet (SM-P600) for almost a year now & it has worked perfectly. Over the last week or so, the WiFi has been randomly turning on & off. Not just losing signal, but actually showing as off in the menus. As of this morning, wifi will not turn on at all. Just says "turning on" on the screen & sits. Never gets to the next screen showing all the open networks.
Everything is fully backed up so I went into recovery tonight. Did the full factory reset and wipe procedures. Tablet boots back like it is as supposed to, but wifi wont turn on when getting to that screen in the initial setup.
Tablet has been well cared in a case, not dropped, and not gotten wet. However I am still positive this is a hardware issue.
Any ideas for things I might try? Help!! Thx in advance
I've the same problem with my galaxy note 10.1 2014 edition SM-P605 :crying: Still haven't found solution
I am almost 100% certain this is some type of hardware problem. I tried flashing about 3 different ROM's and 3 different kernels, all of which successfully booted up. I finished by doing a 100% re-wipe (data & system included) & reinstalling a pure stock kernel and firmware. On every single revision, the words "turning on" would appear when clicking the WiFi option, but then it would get stuck. Message would eventually clear & I could continue using everything on the tablet . . . . . . . just no WiFi or Bluetooth functionality.
Final attempt was to gently remove the back cover. When lightly tapping around different points on the MoBo, the names of my local wireless networks would OCCASIONALLY appear. At one point they locked in & I really thought I had it. However, the whole thing disconnected again after a few minutes & I was back to square 1. :crying:
I never could figure out the perfect sweet spot to pinpoint the problem. My guess now is either a chip or ribbon cable that isn't seated properly, but I poked and pushed (gently!) on everything that was visible without removing any hardware other than just the back cover. Does anyone have a link to the layout of the motherboard that shows EXACTLY which piece is the WiFi/BT module? I did find an online disassembly tutorial with a random Google search, but for some reason they failed to identify this particular module.
Sorry for the long post, but I feel I am SO CLOSE to figuring this out once and for all. Just need a little more tech help to push across the goal line. Thanks!!
~Vol
Vol4Ever said:
I've had this tablet for almost a year now & it has worked perfectly. Over the last week or so, the WiFi has been randomly turning on & off. Not just losing signal, but actually showing as off in the menus. As of this morning, wifi will not turn on at all. Just says "turning on" on the screen & sits. Never gets to the next screen showing all the open networks.
Everything is fully backed up so I went into recovery tonight. Did the full factory reset and wipe procedures. Tablet boots back like it is as supposed to, but wifi wont turn on when getting to that screen in the initial setup.
Tablet has been well cared in a case, not dropped, and not gotten wet. However I am still positive this is a hardware issue.
Any ideas for things I might try? Help!! Thx in advance
Click to expand...
Click to collapse
What model is your tablet?
This was sent from my Lenovo A850 via XDA mobile app.
irfanadli97 said:
What model is your tablet?
Click to expand...
Click to collapse
Sorry about that. It's just the initial release plain jane WiFi model. SM-P600
Update:
After a little more poking and prodding on the MoBo, I'm starting to see activity. Tablet will finally connect again, but will only hold the connection for 10-15 seconds and then drop back out. A few seconds later the cycle repeats.
I really wish I could find a good hi-res photo of the motherboard to help. HAS to be a simple loose connection, or maybe a not-so-good solder point somewhere???
Vol4Ever said:
Sorry about that. It's just the initial release plain jane WiFi model. SM-P600
Click to expand...
Click to collapse
......
never heard of 'em, is it a cheapo tablet? In my country there's a store of them (Allwinner 6.6" tablet with microSD slot, 2gb internal w/o bluetooth WIFI ONLY INTENDED FOR CASUAL GAMING, or should I call it kids only tablet, RM130 ($35))
That thing has a cheap plasticy housing, unneat design but has a pretty good performance (it plays dead trigger pretty well)
This was sent from my Lenovo A850 via XDA mobile app.
irfanadli97 said:
......
never heard of 'em, is it a cheapo tablet?
Click to expand...
Click to collapse
SM-P600 is Samsung's actual model number for the WiFi only version of the 2014 Galaxy Note 10.1. Most definitely NOT a cheapo tablet!! Although this wifi issue makes me wonder. I had the functionality back for about a day or so, and then it disappeared again. This has to be a simple case of a loose connector, but I sure can't find it. Ugh. Utterly frustrating.
oo...my bad
maybe software issue
This was sent from my Lenovo A850 via XDA mobile app.
What firmware version are you using because I am having the same issue. I manually updated to the september update (P600UEUCNI1) for the wifi version and started experiencing the same issue.
Same here. I think it's an issue with NII firmware.
*****PARTIAL solution*****
I have proven 100% that mine is problematic hardware . . . . . NOT software or kernel. For the time being my WiFi is back up & seemingly stable. I had to remove the back from the tablet for the fix. You have to be *extremely* careful, but it just snaps off with no screws. Lots of YouTube videos if you choose to attempt, but please don't say I didn't give you fair warning!
The reason I say partial solution is that I haven't pinpointed the exact location of the short. I am 99% sure it is somewhere on the extreme upper left hand corner as you face the front of the tablet. There are a couple of ribbon connectors in that area, and a few snap on type connectors that look like little motherboard chips. After gently poking & prodding the ribbons and disconnecting & reconnecting the snap connectors (being CAREFUL; I cannot stress this enough), my WiFi reappeared.
My final tip is to keep the screen on the page that shows the list of available networks. If you are having the same problem I was, this screen will just show "turning on" and nothing else for the WiFi. While poking around, I would occasionally see the list of networks pop up & then go back off. I finally hit whatever the magic spot is, and the networks held. Snapped the back cover on again, and I've been online for probably 4-5 days now without a single hiccup.
And before I get flamed, I know how dangerous it is to poke around with a powered, exposed tablet. There are probably certain points that could make connection and FRY the entire thing in an instant. I was just willing to take the risk as my tablet was useless without network capability. I had nothing to lose. I would recommend at least trying to poke & prod with the tablet OFF a few times to be safe, but I personally got tired of rebooting over & over & over & over. My luck sucks. With the tablet ON, I was at least able to monitor when something was happening.
Good luck if you attempt it!!
~Vol
Vol4Ever said:
I've had this tablet (SM-P600) for almost a year now & it has worked perfectly. Over the last week or so, the WiFi has been randomly turning on & off. Not just losing signal, but actually showing as off in the menus. As of this morning, wifi will not turn on at all. Just says "turning on" on the screen & sits. Never gets to the next screen showing all the open networks.
Everything is fully backed up so I went into recovery tonight. Did the full factory reset and wipe procedures. Tablet boots back like it is as supposed to, but wifi wont turn on when getting to that screen in the initial setup.
Tablet has been well cared in a case, not dropped, and not gotten wet. However I am still positive this is a hardware issue.
Any ideas for things I might try? Help!! Thx in advance
Click to expand...
Click to collapse
I bought my Note in March of this year, I started having the WiFi issue after the April firmware update. At first I would get the Connected to... message at random times, even though I had full signal strength. At the end of September, I started losing connection at random times and in the middle of October, I had to send it in to Best Buy's Geek Squad service to have them repair it. It is a hardware issue, as the no matter what firmware version I use, it will never connect to the router. I know it, Geek Squad is aware of it, as I have sent it in for repair twice so far. I would have to send it in a third time before they will think about replacing it with a new Note. I will admit, that before I updated it in May, I did root it, because I tried to remove the Business Week+ and New York Times apps, as I never used either one of them. I tried disabling them, only to have them reactivate and update themselves.
Damn, what I read here is not good news. My SM-P605's died yesterday.
With Tapatalk on my Galaxy Note 10.1 (2014)
Hardware issue for sure. Same problem with mine. Opened the back case, disconnected the upper right (as your looking at the screen) small ribbon, reconnected, and boom, perfect wifi once again!
The EZ Package Disabler app is fine for debloating rooted and non-rooted devices with Touchwiz roms. It uses Knox, so that mustn't be removed. The apps are still on the system partition, but are completely dead now. While other apps, especually for non-rooted devices kill the system apps during boit and try to prevent their restart. But during boot the whole stuff is active until the app kicks in, allowing the system apps to receive updates, communicate, spam free flash mem etc.
The app wirks the same way on my rooted P605 and unrooted S5. And gives a reason to buy Samsung stuff, unlike Touchwiz and its bloatware. As far as custom roms go, i found that of my old LG L9 much better. Even if the early roms were AOSP 4.0.4 based, then 4.1.3, they had already had the fresh & bright look & feel of the future Kitkat, and a few useful enhancements like an integrated backup tool, which was more simple, but for me as useful as TB.
As for the main problem here, i think using a case with a hardened backside, and not one if these with a big hole(though being better than nothing), prevents oroblens like battery, display and seemingly wifi connectors loosening. Or bad solder joints. The backplate of the note gives thru any pressure on the back, especially in the middle area. It then rests on the battery, metal shields, connectors and stuff. This seems to generate enough wear over time for problems. The same back plate on a much smaller device(my S5, but that has a subchassis covering the innards, too) would be much stiffer, and my 7" tablet has an aluminium unibody case, such trouble is unknown there.
Hi Gents..
same problem here... I used to own a SM-600 purchased in 2014 unfortunately I lost it... (the first tablet worked without any proble until I lost it...) than I managed to found the same modell brand new on amazon... it worked for 2 weeks and 2 days ago wifi died... but funny enough not straight away.... first couple time just switched off the wifi... I managed to switch simply back... next day it only worked if restarted the device... now factory reset nothing... If it is hardware related why worked 2 weeks witout any problem? If it is software related why not working after software reset? Only installed a few apps from the store.. the device did not overheated or physically damaged...
I have the exact same problem.
Since I bought this a long time ago, I have to pay for the repair. I just want to know if it is worth it. How much did it cost you (if you bothered)?
In my opinion it would be foolish to spend a dime to repair a 4 year old tablet. If the battery is original, it may well be near the end of its useful life as well. FWIW, I bought this tablet used about 8 months ago and have not experienced this wifi problem.
It's still so well equipped, that you can't simply replace with a modern entry level or midline tablet, but with a top of the line one, so a repair is well an option.
I just don't have a clue about the SoCs performance level. To which current ones it would equal and where things get better. I can only compare it to my similarly(Snapdragon 801) equipped phone and my cheap 7" tablet's quad core Mediatek SoC, and that is considerably worse, though being three years newer.