I've been having this issue for a few weeks now and it's only seemingly getting worse. HOWEVER.. I think I have an idea of what may be going on.
Can a bad USB cable cause this issue? Maybe some kind of static electricity build up or something. If anyone else out there has this issue can you weigh in? Are you using any damaged or 3rd party cables? My problems started around teh time i orderd a (samsung) micro usb cable for use in my car with a cig lighter power converter thingy that has a usb port on it.
to test I wiped the battery stats in CWM and it actually seemed to help.. until last night when I used the new cable in the car again and it went haywire. I wiped the battery again and ill avoid using the new cable to see if it helps any..
I happened to catch it on video last night so I'll post a link up later. I'd like to get to the bottom of this since sprint wants to charge me to replace the device -___- .
I dont see anything in there about what the actual random "problem" is. only problem I have with my menu button is that my "phone" icon is right above it and with my case on the phone it makes it harder for my fat thumb to just hit menu and I sometimes launch the dialer...
so uhhh.. what's the "problem?"
The menu key will randomly activate without me actually touching the screen. Like I said, I have it on video and I'll post it as soon as I get home so everyone can share thoughts on it.
it's exactly what it sounds like. I'll be using the device, sometimes just reading and sometimes not even holding the device at all (as demonstrated in the vid) and the menu key will activate rapidly and very randomly.
http://www.youtube.com/watch?v=0gP2Ju8Xvyo&feature=youtube_gdata_player
Here's the video as promised. Taken last night. It happened today as well even after flashing the lastest stock ek13.
Sent from my Xoom using xda premium
bumpity bump bump
Well, the Video is down. Id like to see if its the same problem as I have.
I believe It may be. Its quite annoying. The Menu Button just activates. I always assume that its just Oily or dirty, something is making it do it. But even after a wipe it does it and Only with the Menu Key. Not Home, Back, or Search. I also use the Matte Black back TPU case, no difference on or off. Cant find a Rhyme or reason.
Edit:
For the record, im also on FC24.
haven't seen the video but I noticed during LOS testing when the phone came out that I got random menu pop ups in low signal areas.
Sent from my SPH-D710 using xda premium
Amusing, it did it when I hit "post reply".
I get it off and on, be damned if I can figure out how to replicate. Just does it.
I was starting to think it was my screen protector, since it started around that time. Happens plugged in and unplugged. Can go days without, then it just happens. I do know it only started for me when I flashed ICS.
Have you tried reflashing and seeing if the problem still exists. Last week my phone was randomly doing stuff like that. I did a full wipe and reflashed and everything has been fine since.
I've flashed several ROMs and have had it.
I can say I have had it only on ICS, some more than others. Never tracked it closely, but have had it on the homescreen, browser. Only 2 times since Fd02.
Wish I knew how to make it happen. I will say signal/battery levels have no effect.
its likely there's a short or something. I would take it into sprint. There's no reason not to. If they can't fix it you'll get a new phone.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Here's what's worked for me on ALL Android phones that have had this problem, go to your custom recovery, and clear cache and dalvik cache and reboot... Your phone will take a few minutes to boot...
Sent from my Epic Touch running Blazer Rom via xda premium
I just got a refurb because of a blue led of death and mine is doing this as well. I've tried ICS roms, stock EL29, and even did a complete factory reset after flashing back to stock EL29 to no avail. It mainly occurs while I'm on a call or texting. It's driving me nuts and if it continues it's going back to Sprint.
I have been testing a theory relates to this.
Last night it was pretty bad, so I turned the setting for the hard buttons lights to "always off".
Hasn't happened since.
Only reason I tried this is that I noticed they came on right before the menu went nuts.
As I've said before, I don't think mine is a short since I NEVER had this occur when on gingerbread. Others may be, but I'm nearly certain mine is not.
If anyone else can try this to see if it does help, would be nice to see.
jfcooley said:
I have been testing a theory relates to this.
Last night it was pretty bad, so I turned the setting for the hard buttons lights to "always off".
Hasn't happened since.
Only reason I tried this is that I noticed they came on right before the menu went nuts.
As I've said before, I don't think mine is a short since I NEVER had this occur when on gingerbread. Others may be, but I'm nearly certain mine is not.
If anyone else can try this to see if it does help, would be nice to see.
Click to expand...
Click to collapse
I'll give that a shot, thanks!
Sent from my SPH-D710 using xda premium
Good idea. I'll try the always on setting and see if that helps as well, that way we'll cover both ways.
Doesn't work. Had it come back k last night.
Not sure what to try.
Mine did it a few times yesterday and I noticed when it did either the gps was trying to connect or it was trying to connect to wifi or 3g. Maybe a coincidence or not, who knows, but it's something else to look at.
My phone did the same thing, it isn't the USB cable nor the screen protector. Its a bug when signal drops below a certain level. However, I believe its a touchwiz issue as I have yet to have it happen on any AOSP rom, input anyone?
Sent from my SPH-D710 using XDA
Related
When my EVO is off, the home, menu, back, & search buttons stay (very dimly) lit all the time on my EVO. I can only see them if the room is very dark. I'm not sure, but this may somewhat contribute to the wretched battery life. Anyone else's EVO doing this?
are you sure you are not just seeing the silver background with the buttons
I had that happen to me once actually - but a quick power on and power off cycle fixed it. It's almost as if the lights didn't get the proper 'turn off' command that they're supposed to.
No, its definitely not the silver I'm seeing. I've tried turning if back on, then off... still there. I've even tried rebooting and they are still slightly glowing. The only thing that will stop it is when I charge it. But as soon as I unplug the cable, the issue returns. They work normally while I'm using the phone. I'm just worried about my battery life.
This is hapiningto me too, I just figured it was suppose to do this...
-------------------------------------
Sent via the XDA Tapatalk App on my EVO
widjit said:
This is hapiningto me too, I just figured it was suppose to do this...
Click to expand...
Click to collapse
Well at least I know I'm not just crazy now lol
So is anyone else having this problem or is this a "feature" for finding your phone in pitch black darkness?
I had this problem on my wife's phone. I returned it. I tried to take the battery in and out. I also did a hard reset but nothing seemed to fix it. I was told it was a hardware issue by reps at BB. Hope this helps. My wife's new phone does not do it.
Sent from my PC36100
Oh by the way I don't know if this is related or not but her phone was a 002 model and mine was a 003. Her new phone is a 003 and does not glow in the dark. Just thought I'd throw that out there.
Sent from my PC36100
cjrivera04 said:
I had this problem on my wife's phone. I returned it. I tried to take the battery in and out. I also did a hard reset but nothing seemed to fix it. I was told it was a hardware issue by reps at BB. Hope this helps. My wife's new phone does not do it.
Click to expand...
Click to collapse
Thanks for the info! Just curious if she has noticed better battery life with the new phone by any chance? If not, I'll probably just keep this one. My EVO is also a 002...
Hello all! Ive just recently got my Xperia arc, and flashed a nightly build of CM7 on it, number 20. Everything seemed to run smoothly, but just now screen started to behave very weird, it almost seem to have osme kind of "ghostly" second touch.
The upper part of the screen is almost impossible to use, when I try select an app to move it on the screen, by holding finger down, it just flickers for a second and gets deselected. If I manage to select it and drag+hold, it starts spazing out all over the screen, with screens switching between eachother by it self.
The problem is especially noticeable in games, where you usually have a joystick controller in bottom left corner. When using it, I usually trigger the buttons above it in the upper left corner which I am no where near at with my finger.
Is this a ROM issue, or hardware issue? Ive been using the rom for couple of days with no strange to it, and now this happens. Any ideas what the source can be?
ROM failure.
Sorry for bump, but apparently the problem remained. I changed to XDA rom, which too is based on CM7 thou and after a day I stumbled upon same problem of ghotsly second touch on screen.
I cant hold to move apps, cant precisely press a button in game on left side of screen, it then triggers some other button nearby. I do get haptic feedback from long press on a homescreen, but the "add new" menu popups only every few tries Any ideas of what may be causing this? I would really like to avoid the hassle of resetting the phone and sending it back for repairs :/
try stock one or miui.
It sounds a bit like your screen had a bad encounter with water...
Could this be the case?
iR¡[email protected]!* via Tapatalk
iridaki said:
It sounds a bit like your screen had a bad encounter with water...
Could this be the case?
iR¡[email protected]!* via Tapatalk
Click to expand...
Click to collapse
No, this phone is only few days old.
I think I am noticing a pattern.. screen behaves this way only late evenings, till next morning. I never noticed the issue during the day, but then it was there again for no reason after I left phone for couple of hours (it's past midnight here at the moment). Now when I think back, same was previous two evening, issue only noticeable during late evenings. Could my phone be possessed lol?
It's quite weird issue too. Upper half of the screen seems to have a ghost touch as I said. When trying to add a widget to upper screen, I only get a haptic feedback from long press. When playing games, all buttons on left side (landscape mode) get activated as soon I press one of them. Most weird of all, is that screens works perfectly in app drawer and settings, but not in app/homescreen. I will test how it is again tomorrow and report. If it works just fine again as if nothing happened I will be really puzzled.
Currently on CM7 Xda version, same was for official version. I am considering updating to MIUI, just gotta figure this radio difference stuff, but am becoming sceptic to whether this issue really lies with ROM and not app/settings.
Yep, issue is gone like nothing happened at the morning, this is is haunted ._.
I've figured the cause, it only happens when the phone is plugged in and charging. Beats me why thou, what remains to see now is if it is tied to the kernel or not. Posting it here in case others with similar problem stumble upon the thread.
Are you using the stock charger, i used to face bit similar problem when i used to connect my old HTC USB charger... later i discover the HTC charger was giving only 500mA , where as sony one is rated at 700mA.
mangemayur said:
Are you using the stock charger, i used to face bit similar problem when i used to connect my old HTC USB charger... later i discover the HTC charger was giving only 500mA , where as sony one is rated at 700mA.
Click to expand...
Click to collapse
Thanks for the tip! Turns out it didn't like my 1000mA charger I am using for all my usb stuff, but the stock on works perfect (it's 850mA).
I always had a problem with my menu button going off at random. So if anyone else has this problem here is a fix. U will need to open up ur phone and thanks to Samsung with out any void stickers. after removing the screws the bezel around the screen is just held in by clips. So you be left with glass and the board. Clean around the rim of the glass should have little dirt build up on the rubber sealant. Also I booted up with out the flex cable( linked to the touch button) connected and once booted up reinstall every thing and it work no more random menu pop ups
Sent from my SPH-D710 using XDA
Good info. But i thought it was caused when in low signal areas. Actually, i got my replacement refurb phone a couple months ago and it never had that menu problem until a week ago. So the dirt thing is possible
I just got this phone last week (used) and it has done it constantly when in low signal areas, like my job. However i put it on wifi at work Friday and it stopped. So i think it is related to poor 3g signal. Just my thoughts based on my experience.
Sent from my SPH-D710 using xda premium
menu button
I had the same problem on a brand new phone. It was 1 month old. It had it happen to will on wifi or will I
had full bars. I think the dirt problem is more the problem. I work in a shop with alot of dirt on the air.
Thanks for the info. I will know what to do if it happens on my refer phone.
if its a dirt issue why the need to reinstall software?
I cleaned my phone yesterday. Bought it from a chick that wore a lot of make up so it was pretty dirty. And so far no menu button misfires. May in fact be the dirt issue. Odd that it was really only going off during weak 3g signal times.
WOW, universal problem
I have been experiencing this on my new device for some time now. I thought I was alone but apparently others have it to then. Mine will go haywire all of a sudden to the point where the menu pops up and disappears up to 20 times by itself leaving the phone unusable and making the other haptic buttons non functioning. Usually requires quickly turning off the screen and popping back on. Drives me absolutely nuts to the point that I de-rooted and went back to absolute bone stock only to still have it happening.
Has to be dirt related. I thought maybe there was some voltage or heat problem that was causing it to fire. Has anyone had any luck fixing it without tearing the phone apart?
I want to smash this phone in low signal areas!! My NS4G gets better signal than this does in bad 3g areas. In California where I had full bar 4g this phone was perfection but once I got on the east coast (especially spots in NYC) I get so damn frustrated!!
I sure wish it was dirt causing it but I got it when my phone was new when I was LOS testing in dead spots the first month I had the phone
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Mine has been doing it since I got it. It is a refurb though as I bricked 2. The 2 previous phones didn't have the issue and it only does it when switching from 3g/4g to wifi or vice versa, or while switching data back on after a call. In my case it's definitely not dirt.
JohnCorleone said:
I want to smash this phone in low signal areas!! My NS4G gets better signal than this does in bad 3g areas. In California where I had full bar 4g this phone was perfection but once I got on the east coast (especially spots in NYC) I get so damn frustrated!!
I sure wish it was dirt causing it but I got it when my phone was new when I was LOS testing in dead spots the first month I had the phone
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Same always want to throw my phone at the wall when I'm in a low signal area and the menu button goes crazy!
Sent from my SPH-D710 using Tapatalk
will be trying this to see if it fixes it for me as well
I have this same issue with mine and will be trying this when i get some time. It's very random and very annoying.
have had this happen on 2 phones, finally on my 3rd replacement last week and it has been good so far....
This keeps happening to my phone, only most of the time it's the search button. Low-signal areas mostly, connecting to wifi stops it completely. I think it may have to do with using non-samsung chargers/cables.
Mine alternates form the menu button to the search button. Both equally annoying... I must have some special dirt in my phone
bryank930 said:
This keeps happening to my phone, only most of the time it's the search button. Low-signal areas mostly, connecting to wifi stops it completely. I think it may have to do with using non-samsung chargers/cables.
Click to expand...
Click to collapse
I notice it more in low-light situations than I do in low-signal situations. When I'm connected to WiFi, I don't see any lessening of the phantom menu button.
U guys could also try the second part which is to boot up without touch button connected then when booted connect it back via flex cable on the bottom... good luck
BTW opening ur phone isn't so bad no void stickers and after screws are just clips
Sent from my SPH-D710 using XDA
Damn guys I thought I was alone with this problem! I swear, I don't care how great the S3 is. If it has the same behavior its getting returned immediately. My GNex doesn't though so that's a good sign. I wonder if we could add menu buttons to the screen and disable soft keys and maybe it would get rid of this behavior. I have to see if a dev can make that happen
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Had this issue but only on some ics leaks never on gb
Sent from my SPH-D710 using XDA
Well, I'm gonna have to edit my comment from earlier in the thread. After about breaking mine in half and throwing it out the window yesterday, I decided to try taking it apart and looking around. I didn't see any dust, but once I reassembled it, the problem has not returned. It usually does it immediately when it reboots and continues until it has acquired a signal. I've tried my best to get it to go crazy and so far so good. Those having the problem may want to give it a try and see if it helps.
My brother in law who is rooted on Blue Kuban, My Sister in law who is completely stock EL29 and my self also rooted on Blue Kuban all experince this problem. we all have launch day phones. def seems to happen more for us in low signal areas. so annoying. for those that took the phone apart is there any chance of dust getting in and being seen or is it no big deal?
thanks
Hi, Everyone! This is my first post on here but I have spent the better part of the last week reading all the different threads. Yesterday my Samsung Epic 4G decided to go a little insane on me. It was working eprfectly fine (especially for a 2 year old phone) when all of a sudden my power button seemed to start cyling and the power off screen kept popping up and the volume keys did the same. I turned the phone off and even tried taking the battery out and giving it a rest but the problem persisted.
Another issue was that some of the numbers no longer worked correctly. The even numbers both on the touch screen and keypad would dial
"2468" instead of the corresponding number; very weird! The phone had never been rooted or modded at all. Well I was able to get into the phone after figuring out a way to input my passcode with the faulty numbers and I performed a hard reset. The phone is back to completely stock but the power button and camera button do nothing. The volume up button works well but the volume down (besides lowring the volume) button causes google search to pop up and then a bunch of letters and numbers to be typed in both the google search bar and in the message of box of the last person I texted. I can still use the phone by opening the key pad to wake the screen up and I can text and call fine as long as I don't touch the Volume Down button. Also, battery life is ridicolously low. I am up for upgrade but don;t really feel like upgrading to the S3 just yet. Sorry for the long post. I know it is against forum policy but I wanted to get the whole story out there. So here is what I am looking to do:
I want to root the phone and install one of the roms to maybe eek out a couple more weeks out of it. Again it works ok now, just the sliding out of the keypad and lack of power button sucks. The phone boots up if I take the battery out and put it back in wihtout touching the power button.
I have read up on Odin and that looks somewhat straightforward. Just trying to see what you think is my best course of action. Again, I do not have a power button working or camera button and a faulty Volume Down Button. Maybe I can do the whole slip in the battery while holding "1" to get it into download mode? This will be my first time rooting a phone so any help is great and appreciated. Thanks and again, sorry for the really long post!
I forgot to mention that the phone is currently running on Gingerbread 2.3.6. This may or may not make it more difficult to root.
Did the phone get wet at all? Use it in the rain?
Sent from my PantechP4100 using xda premium
kennyglass123 said:
Did the phone get wet at all? Use it in the rain?
Sent from my PantechP4100 using xda premium
Click to expand...
Click to collapse
was thinking this as well
It actually got wet about 1.5 years. I threw it in rice for about a week and never had any issues. The phone has never frozen or had issues the past year and a half. Yesterday it was in the kitchen charging (with a samsung charger but not one for this phone specifically) and it started doing the whole power button/power off screen flashing. I was able to get it in download mode earlier today but i don't know about recovery mode since the power button is dead. Maybe I should root it to see if its a hardware issue?
Edit: I forgot to mention that the phone gets really really hot while charging as well in the area above the battery. Hopefully nothing short-circuited.
It could take a while before the corrosin gets bad enough to affect your phone. I dropped a phone in the toilet once, and it was over 2 years before it crapped out. Took it apart and it looked like an old Chevy wheel well inside.
Sent from my SPH-D700 using Tapatalk 2
frostedunit said:
It could take a while before the corrosin gets bad enough to affect your phone. I dropped a phone in the toilet once, and it was over 2 years before it crapped out. Took it apart and it looked like an old Chevy wheel well inside.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
That is a good point. I never thought of that. It was also in the kitchen which was humid and hot as ever yesterday. Do you think any kind of root or rom could help me squeeze a little bit of life out of my old phone.
Raymos24 said:
That is a good point. I never thought of that. It was also in the kitchen which was humid and hot as ever yesterday. Do you think any kind of root or rom could help me squeeze a little bit of life out of my old phone.
Click to expand...
Click to collapse
Doubtful. If you're hardware's screwed, so are you.
Sent from my SPH-D700 using Tapatalk 2
So I left the phone alone for a couple days with the battery out. I go to turn it on today and it worked perfectly. Then after about 5 minutes the power button stopped working again, but everything else is ok. No random letters and numbers and the volume buttons work as well. Now, I'm kind of lost as to what to do. I do have a parts phone, same one as this. Maybe I need to replace the power button? It clicks and everything and even worked for a couple minutes but now is non-functional again.
I just got this tablet (to replace the garbage SGH-I467) a few days ago (Thu., May 15th). For the first couple of days it worked like a dream. However, the last 4 nights/3 days, I have been encountering some strange issues. What I will do here is describe the issues I've been having, what I have done in attempts to fix them, list some of the things I think may have caused it, and include any additional info/questions.
Before all that though, I would like to mention that I am not a developer, but I am a bit 'tech savvy' and am more familiar with/knowledgeable of technology than the average user. Also, I have spoken with Samsung tech support and even had the support guy access my Tab Pro 12.2 remotely (I will explain what I learned from that below). So, without further ado (I apologize in advance for the long winded nature of this post, but I want detailed):
The Issues:
1) Screen "flickering"—By flickering I mean that it is shutting off and turning on rather rapidly and sporadically, though inconsistently.
I first encountered the problem 3 days ago (the 18th).
Four nights ago (the 17th), before going to bed, I plugged the device into the same outlet I have used for all my mobile devices, when I woke up (on the 18th) the screen was doing exactly what I described. I hit the home button a few times and it stopped.
That night (the 18th) I plugged it back in to the usual spot before going to bed. The next morning (yesterday, the 19th), the screen was "flickering" again. I tried to press the home key a few times, as well as both the soft keys, nothing. In between "flickers" you can see the lock screen, where I have to enter a pin, but even while visible I can't type anything. So this time, to try to solve the problem, I held the power button + volume up to get to recovery and wiped the cache partition, rebooted the device, and viola, it worked again. Thinking that I may have to factory reset the device if the problem persists, I used Kies to backup all my data. I used the tablet the rest of the day, even plugged it in (in a different outlet than the one next to my bed) for a while and had no issues.
Last night (the 19th) I did pretty much the same thing, but this time, thinking that it might be an issue with the device getting too much power (the Quick Start Guide says: "Note: Connecting the travel adapter improperly may cause serious damage to the device."), I used a travel adapter from one of my other, USB 2.0 devices (the only difference between the adapters is the output: 2.0 = 5.0V—2.0A vs. 3.0 = 5.3V—2.0A, and output was specifically what I was concerned with). This morning (the 20th) the problem has returned, but now includes my second issue: the hard home button and both soft keys, back and recent apps, no longer function. So I immediately tried to wipe the cache partition and reboot, but this time it didn't work. Thankfully I had anticipated this yesterday and had that Kies backup, so I wiped the entire device back to factory settings. But alas, it was unsuccessful and the problem persists, including the loss of button functionality, with the exception of the power and volume buttons.
It is important to note that when I first got the Tab Pro 12.2 and set up the lock screen, I used the option that delays the actual locking of the device 10 minutes after screen timeout, but set it so that if I lock the screen with the power button it ISN'T delayed and immediately locks. That being said, a couple of times when the "flickering" stopped long enough to momentarily use the device, I was able to enter my pin and unlock. But when the screen starts flickering again, it locks the device, so the power button must be affected as well. Though since the first factory reset of the device, I haven't set up a pin. I have done several factory resets and none of them have worked. The best result has simply been limited (no back, recent apps or home key) and momentary functionality. I tried using Kies to do emergency firmware recovery, but every time I click the option it disconnects the device.
When Samsung tech support remotely accessed by device (I used one of the momentary functionality windows to download the required application) the agent was able to utilized soft and home key functionality, even though I couldn't. This tells me that it was hardware related, not related to UI/software.
So there are a couple of things I think may have caused/contributed to the problem:
The first, which I vaguely touched on above, is the power issue. Perhaps I have shorted the device out somehow. The outlet I use to charge things while I'm sleeping is on the wall behind my bed, so I have to use a common extension cord, one that has 3 outlets at the end. I have a light plugged into that and in the past have charged both my SGH-I467 (AT&T Note 8.0) and my SGH-I747 (AT&T S4 Active) with that cord and outlet. That is the only place I have charged the SM-T900 overnight, but none of the other power sources I have used have caused these issues.
The second possibility is a virus some sort. I have never used the Samsung app store on any of my other devices, but in order to update the Hancom Office suite I had to. Since I had an enjoyable time using it to that end, I decided to see what else I could find on Samsung's store. I downloaded a couple of things (the "Official Captain America game" and a couple wallpaper/theme apps) and was looking around the store to see if there was anything else I wanted to download. I found several apps that had reviews claiming they were trojans, so I immediately checked the reviews for the apps I had downloaded, but none of them had similar reviews. However, that does not mean they didn't have viruses.
So, what do the resident Android gurus of XDA think about these issues?
I tried searching all over the forums and elsewhere online for people having the same issues, but couldn't find anything. Have any of you ever encountered something similar to this?
Until recently, I hadn't ever heard of anyone getting a virus on an Android device. Are they common? What is the nature of Android viruses?
If these issues do have something to do with overcharging/shorting the device, how can I mitigate that problem? Tonight when I charge the tablet, instead of using the USB 3.0 charging cable, I am going to try just using the 2.0 cable. As I understand it, that can be done by simply plugging it into the right side of the port. Hopefully that will stop exacerbating the problem.
Again, I apologize for such a long winded post. I would like to thank you all in advance. If ever I have problems with an Android, you guys are the ones to ask!
*UPDATE* Before I started typing this I was attempting to run the Kies 'Firmware Upgrade and Initialization', as opposed to 'Emergency Firmware Recovery', to see if that too would disconnect the device. Unfortunately it said that my device needed to be charged first. So I shut it down and plugged it into a surge protected strip and began typing this post. Occasionally I would go over an check the charge. While it was shut down and charging I was able to use the home key to bring up the green battery. Once the charge looked like it was about 75% complete I turned it back on and lo and behold, the "flickering" issue looks resolved and so does the button issue. I can go back, enter the recent apps and task manager, and use the home key functions. For how long this will last, however, is unknown. I guess we'll see in the morning. I'll post what happens tomorrow.
What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk
RE: Case?
dodo99x said:
What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I am not using a case or cover at all...
same issues here
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.
VeinkWiles said:
So, what do the resident Android gurus of XDA think about these issues?
Click to expand...
Click to collapse
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.
Mike Austin said:
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.
Click to expand...
Click to collapse
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537
VeinkWiles said:
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537
Click to expand...
Click to collapse
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk
Re: developer settings; display touches
dottat said:
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Damn! That's an outstanding idea! The only downside is that last night I sent the tablet to Samsung's repair department, so I can't test that out. But once I get it back, if the problem persists I will definitely be doing that first. Thanks for the advice dottat.
Fw:Re: developer settings; display touches
mikegbg said:
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.
Click to expand...
Click to collapse
Hey dude, check out dottat's reply. He's got a really good idea that may shed some light on the source of the problem. Unfortunately, I can't try it out. If you do it, let me know how it goes. Maybe you can take some screenshots? Either way, hopefully you can get something out of it.