Related
If you are an Epic Touch user that is experiencing the LOS (Loss of Signal) issue please click on the link below and report in that thread with Sprint.
http://community.sprint.com/baw/message/339779
If you do end up posting on the Sprint site please do post in this thread as well...
Also it was just pointed out that there also is a Samsung support Twitter @ www.twitter.com/samsungsupport
(Please also contact there if you experience LOS)
If you would like to follow this up with a call to tech support, it will help. Try and get transferred to advanced tech support.
This needs to happen from as many people experiencing this as possible!
Don't be lazy!
Thx!
There is another thread 11 down from this one(and multiple other ones further in the forum). The search button works wonders if you use it :-D
Sent from my SPH-D710 using XDA App
Double post
Sent from my SPH-D710 using XDA App
graffixnyc said:
There is another thread 11 down from this one(and multiple other ones further in the forum). The search button works wonders if you use it :-D
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I don't think those other threads were specifically aimed at getting people to do this
I have been told by a reliable source that sprint is aware there is an issue and their engineers are working diligently to find a fix.
Sent from my SPH-D710 using Tapatalk
graffixnyc said:
There is another thread 11 down from this one(and multiple other ones further in the forum). The search button works wonders if you use it :-D
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Anything is better than "is our phone compatible with random tech blog rumor" threads.
Sent from my SPH-D710 using Tapatalk
kingsway8605 said:
I have been told by a reliable source that sprint is aware there is an issue and their engineers are working diligently to find a fix.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I hope your reliable source wasn't a Sprint CSR.
Those of us coming from the Moment were constantly being told that by Sprint regarding the radio lock up issue. They never did fix it. It wasn't until the devs at SDX got 2.2 onto the phone that the issue went away.
I have also found that tweeting complaints to www.twitter.com/samsungsupport during business hours will get a quick response, which results in escalation of real issues.
adma84 said:
I have also found that tweeting complaints to www.twitter.com/samsungsupport during business hours will get a quick response, which results in escalation of real issues.
Click to expand...
Click to collapse
Nice find! Thx!
i just got off the phone with sprint and they told me that samsung pushed an update on friday to fix a delay in receiving text messages which has borked the internal antenna. that would explain why i only started having problems yesterday.... sprint will give you a ticket number and they will fix your phone for free at a store.
call up and get it fixed.
its only going to get worse!
dtr145r said:
i just got off the phone with sprint and they told me that samsung pushed an update on friday to fix a delay in receiving text messages which has borked the internal antenna. that would explain why i only started having problems yesterday.... sprint will give you a ticket number and they will fix your phone for free at a store.
call up and get it fixed.
its only going to get worse!
Click to expand...
Click to collapse
This is false. The issue has been going long since before Friday.
It will be fixed in the first update though.
... and here I was thinking about exchanging my 3D for a GS2... it seems the signal problems are widespread to all phones. :/
Droga said:
... and here I was thinking about exchanging my 3D for a GS2... it seems the signal problems are widespread to all phones. :/
Click to expand...
Click to collapse
Its not a showstopper and it doesnt happen on all devices. So if it happens when you get it use your 30 swap to get a new replacement. It hasnt happened on mine at all. Also there is going to be a fix... So, with all of that said I cannot think of a single thing that should cause anyone to decide not to get this and choose another phone. Thx
DeeXii said:
Its not a showstopper and it doesnt happen on all devices. So if it happens when you get it use your 30 swap to get a new replacement.
Click to expand...
Click to collapse
It is a 14-day swap unless you bought your device pre-launch.
This is a total show stopper, I have 2 of these and they both do it constantly. I cant even surf for more then 10 minutes without it happening to both units. I cant make calls, I cant receive calls, cant go online, cant use streaming music, cant use navigation. total waste at this point. I love the phone physically and its great when on WiFi but that's only 1/4 of the day. I am not taking a chance of getting stuck with a phone that I cant even make calls on. maybe I will try again once everything gets fixed but for now its not worth the trouble.
davedave1234 said:
This is a total show stopper, I have 2 of these and they both do it constantly. I cant even surf for more then 10 minutes without it happening to both units. I cant make calls, I cant receive calls, cant go online, cant use streaming music, cant use navigation. total waste at this point. I love the phone physically and its great when on WiFi but that's only 1/4 of the day. I am not taking a chance of getting stuck with a phone that I cant even make calls on. maybe I will try again once everything gets fixed but for now its not worth the trouble.
Click to expand...
Click to collapse
You have something seriously wrong with yours then. I've had mine since launch and it's done it twice. You should exchange yours.
I rooted my phone and got this for the first time the next day. Hasn't happened before that. Didn't even know what you guys were seeing until it happened. I just got a zero with a line across the middle of it in my top bar and my signal bar and data icon were gone.
Is that what people are getting also that have not rooted their phone? When I say not rooted, not the people who rooted then installed the stock kernal back on. People who never rooted in the first place. That is what I would like to know.
Mine did it once before rooting, once after.
And yes, it happened just like you described. I thought rooting and flashing Zedo v3 fixed it, but it didn't.
clamknuckle said:
Mine did it once before rooting, once after.
And yes, it happened just like you described. I thought rooting and flashing Zedo v3 fixed it, but it didn't.
Click to expand...
Click to collapse
Cool, I hope it is device problem and not just a rooting problem. This way we can get a fix for it from Samsung, hopefully.
I have it on good authority it will be fixed in the first software update from Sprint. No idea when that will be though. It's not a rooting problem.
Hi there,
first of all i apologize for my poor english. Got my Galaxy Nexus for a week and i'm not very excited about ICS. I expected great battery life and a few bugs but i've seen a lot. There's an annoying one : sometime my phone seem to live without my touch. If i'm with keyboard on it starts to type messages like "dajhfhakjerehk" then it go on the home and start open apps randomly without my touch. Seems like the volume bug but different; anyone experiencing this issue ?
I hope that's only software, otherwise i had to bring the phone back to the seller very soon.. I wish that 4.0.3 will be released soon so i can decide if it's software or hardware problem.
Thank you all in advance.
I have the same problem with mine, it doesn't happen often though and I can't reproduce it on queue but I have had my phone for 3 weeks now and it has happened happened several times so it's not just a one time thing.
guidocioni said:
Hi there,
first of all i apologize for my poor english. Got my Galaxy Nexus for a week and i'm not very excited about ICS. I expected great battery life and a few bugs but i've seen a lot. There's an annoying one : sometime my phone seem to live without my touch. If i'm with keyboard on it starts to type messages like "dajhfhakjerehk" then it go on the home and start open apps randomly without my touch. Seems like the volume bug but different; anyone experiencing this issue ?
I hope that's only software, otherwise i had to bring the phone back to the seller very soon.. I wish that 4.0.3 will be released soon so i can decide if it's software or hardware problem.
Thank you all in advance.
Click to expand...
Click to collapse
If you're running stock software and this happens frequently I think you should return your device for a new one - sounds like a faulty digitiser to me...
Snoemannen said:
I have the same problem with mine, it doesn't happen often though and I can't reproduce it on queue but I have had my phone for 3 weeks now and it has happened happened several times so it's not just a one time thing.
Click to expand...
Click to collapse
So i'm not the only one.. I can't reproduce me as well : sometime not happen for 2 days , sometine twice a day..
djmcnz said:
If you're running stock software and this happens frequently I think you should return your device for a new one - sounds like a faulty digitiser to me...
Click to expand...
Click to collapse
If it was the digitiser i think that it would stop always, not randomly every 2 o 3 day.. That's my opinion
djmcnz said:
If you're running stock software and this happens frequently I think you should return your device for a new one - sounds like a faulty digitiser to me...
Click to expand...
Click to collapse
It only happens every other day or even more rarely and it just for a short period so I'm not sure what is doing it.
I also have the more common multi-touch bug after using some 3D games like Heavy Gunner so I'm more inclined to believe that it is something that triggers it similar to that than for the digitizer to be faulty, but that might just be me trying to convince myself that it will be fixed since I don't want to go through the hassle to replace the phone.
Hopefully google will release the next update again soon, be it 4.0.2 again or .3 or whatever, I'm still on ad yakjuxw with 4.0.1 so I was going to wait untill I get the update before I take any action.
Snoemannen said:
It only happens every other day or even more rarely and it just for a short period so I'm not sure what is doing it.
I also have the more common multi-touch bug after using some 3D games like Heavy Gunner so I'm more inclined to believe that it is something that triggers it similar to that than for the digitizer to be faulty, but that might just be me trying to convince myself that it will be fixed since I don't want to go through the hassle to replace the phone.
Hopefully google will release the next update again soon, be it 4.0.2 again or .3 or whatever, I'm still on ad yakjuxw with 4.0.1 so I was going to wait untill I get the update before I take any action.
Click to expand...
Click to collapse
me too , let's wait
It's all about the 4.0.1. I had that issue before, now it works fine with 4.0.2. Just update and that problem will disappear.
Sent from my Galaxy Nexus using xda premium
I have the exact same problem, and I must say I am so relieved to see it's just a software bug! Thanks, Rilazi
sorry for bumping this thread but the issue it's very annoying.. I can't even use my phone, it start doing things himself!! How can i do ?
Hi everyone. I, as many others, have been having an issue with my microphone cutting out during a phone call. I have a roooted Verizon Galaxy Nexus running the 4.0.4 leak, but it appears that for everyone who is having this issue it doesn't matter which ROM you're running or even if you're rooted or not.
[EDIT]: It per one of the posters below, this is not so much a "microphone" issue as it is an "outbound audio" issue. Unfortunately I can't edit the subject name to refer to this, but for me personally when I've been doing google searches on this issue the first word that came to mind anyway was the word "microphone" or "mic" anyway.[/EDIT]
People have been trying different things like flashing different radios, muting and unmuting, turning off voice privacy, etc., but it seems that nothing helps. Not even several hardware replacements or sim card replacements.
However, I did notice a pattern from different forums, etc. It seems that some people either have the problem all the time, or not at all, and it seems that some people reported that traveling to different metro regions affected whether or not they had the issue.
So I was curious to see if the pattern has to do with geographical location as an issue with Verizon's network, vs. hardware/software issues.
This poll has 50 possible answers, 1 for each state. Please answer this poll ONLY if you ARE experiencing this issue, and please only vote for your state if you live in the state's capital. For example, I live in the Denver metro area, so I would vote for Colorado. However, if I lived in Fort Collins or Grand Junction, I would NOT vote at all.
If you have traveled and visited another state's capital and have had this issue there, you can go ahead and vote for it as well.
It will be interesting to see if we have a lot of hits in certain major metro areas and none in others.
[EDIT2] Also, if you don't have the problem at all, go ahead and post a comment with your location. In fact, it would be interesting to see if people don't have the problem but others in the same city do. [/EDIT2]
Thanks!
I thought I had this issue just turns out my pinkie was covering the microphone its king of poor positioning watch, the way u hold the phone after changing the way I hold it no one complains they can't hear me
Sent from my Galaxy Nexus using XDA
TLDR: I kept having people telling me that I sounded like a robot.
Sent from my Galaxy Nexus using XDA
I had this problem on back to back to back phone calls this morning. Horrible.
Sent from my Galaxy Nexus using Tapatalk
My wife and I are both having the issue in Richmond, VA but I could only vote once for myself. She has reverted to an old droid x as she cant rely on the phone anymore.
Might be a little late, but maybe we should collect ZIP codes instead? Then we could use this tool: http://batchgeo.com/
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
I voted. I'm in South Carolina. I'm pretty sure it's NOT a regional problem though.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If holding the phone different worked for you, then you don't have the issue this is referring to. This issue can happen with a wired headset, Bluetooth headset, on speaker phone, which none of these would be affected by how you are holding the phone considering you aren't using the mic on the phone. The people on the other end hear a series of clicking sounds, then no audio.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
I had the same problem on my 2 rogers GNs(GSM version)
after I upgrade my baseband to i9250xxkk6, the problem gone
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
I'm in Raleigh, NC.
I got my phone on release day and noticed this problem a few days later. I've since replaced the phone, then the SIM card (a theory that it was SIM-card related was floated over at AF).
After changing the SIM card the problem seemed to go away for a couple of weeks, but it came back with a vengeance.
I hate the idea of getting a "refurb" from Verizon (I put refurb in quotes because, based on the FIVE refurb'ed Incredibles I had, I'm pretty sure they don't do anything except replace the glass if it's scratched), but I guess a functional refurb would be better than an aggravating semi-functional new phone.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Click to expand...
Click to collapse
I can't help but be reminded of Steve Jobs.... "You're holding it wrong!"
I'm glad your phone is working properly but, as others have noted, this is most definitely not the problem we're talking about.
gabe23 said:
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
Click to expand...
Click to collapse
Thanks for clarifying, I edited my original post, unfortunately I can't edit the subject name, but you're right, it's outbound audio and not mic. Thanks again!
adrynalyne said:
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
Click to expand...
Click to collapse
You're right, I was caught up in it at the moment and thought it would just be interesting to see how the issue maps out, but this little poll in no way is a troubleshooting tool, more of a type of infographic maybe?
The only fix is going to be a software update from el goog. can't wait for it!!!
I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
Flashing a new rom/radio does not help. I'm running nothing stock (leaked radios, CM9 Kang Nightly, Franco Nightly) and I still have this issue.
Good to know I'm not alone, Minnesota is currently winning! :-\ :-(
AnotherHiggins said:
I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
Click to expand...
Click to collapse
I was told the same thing by VZW support, but mid-march... which is NOW! I'm really getting sick of this. Ready for the fix and some info.
I have the same problem on the GSM version. Also Raleigh, NC.
I've been having an issue with my softkeys (settings, home, etc...). They will randomly press opening settings, going back and opening the recent apps. Usually it does a combination of all of them and the only way to fix it is to turn off the screen and turn it back on.
I first thought this was a rom problem and switched to a new one. This didn't help so I believe it has to do with hardware. I looked up online and people say that it is a screen or battery problem. So I flashed to stock ICS and brought it into sprint, the guy was nice and stuff but he said he couldn't do anything unless we could make it happen. It wouldn't do it, so he couldn't do anything about it.
I'm wondering if it actually is a software issue or something that I'd be able to fix myself. Has anyone had any problems like this? It's not too often but often enough to be annoying. Any help would be nice.
Thanks in advance
I've heard pepper have issues with soft keys in low signal areas but never heard of that issue.. When you left the store did you have the problem on stock ics still
-TeaM VeNuM Like A Boss
Well, I flashed back to Paranoid when I got back home and so far I've had no problems. I haven't been using my phone though, I'll have to see how this goes.
MiguelHogue said:
I've heard pepper have issues with soft keys in low signal areas but never heard of that issue.. When you left the store did you have the problem on stock ics still
-TeaM VeNuM Like A Boss
Click to expand...
Click to collapse
I have the issue of menus open and close in all apps and from home screen in low to no signal areas. Some times making the phone unusable. If I turn mobile data off seems to cure the random menu opening issue... Becomes 1/2 a phone... No data and 10 a month for... What oh ya high speeds data... Used to get 10 Meg download on 4G until a couple months ago.. Now only getting 700K, I think the Sprint tower near my house was stolen lol is that a word? FI27 is out, might help. My phone has been flagged for liquid damage so hard to find out if it's a hardware problem causing the menu issues. My upgrade isn't until May so I will make the most till then. NOTE 2? Little Rant in your thread OP... Sorry
Sent from my SPH-D710 using Tapatalk 2
I don't mind the rant
I think it may have something to do with signal however. I was at work today and I got a bunch of random presses again. There was a good sized storm and I only had a bar or two. I'm also still wondering if it is software but I cant even stand to use stock ICS to see if it happens, if I couldn't use custom roms I don't think I would even own an android phone.
I was at the gym last night... 1 to no bars, menus and soft keys started poping like crazy... Turned off mobile networks.. 3G data and not one more Phantom menu press... If I wasn't so lazy I would use a custom prl and roam control... Bet that would cure my low signal areas. I will test that theory soon.
I had same menu action when I Odin stock el29 GB, with all modems I flashed
Sent from my SPH-D710 using Tapatalk 2
Xynche said:
I don't mind the rant
I think it may have something to do with signal however. I was at work today and I got a bunch of random presses again. There was a good sized storm and I only had a bar or two. I'm also still wondering if it is software but I cant even stand to use stock ICS to see if it happens, if I couldn't use custom roms I don't think I would even own an android phone.
Click to expand...
Click to collapse
I have use menu other Android devices my first phone was a Samsung moment, i rooted all my phones and i 've never had this problem, i even called Samsung and they say its sprints network not software or hardware, so i will take my phone to another store to see if i have better luck
I was experiencing the same problem on Gamer Mod. Even reflashed after fully wiping everything and still had it happening... was using apex launcher...but never happened to me before. Anyway wiped again and flashed back to blue kuban and its gone.
Shame because I really liked gamer mod.
Sent from my SPH-D710 using XDA
I don't see how a network can cause an issue like this though.
Also, I've tried wiping and flashing multiple roms on everything from GB to JB and still the same thing.
It is a low signal issue. The end. Only solution.. Get it replaced. My co worker had it. So I had first hand experience with it.
Sent from my SPH-D710 using xda app-developers app
When I brought it in he said he can only do something if we could duplicate the problem. Should I call Sprints call center and see what they can do? Would they already know about the problem or are they going to pretend like they've never had an issue like it. Do I have to flash back to stock ICS or do they not care? Sorry about the questions, I'm just pretty new to having my own phone plan and my own problems and don't really know how to deal with them yet.
Xynche said:
When I brought it in he said he can only do something if we could duplicate the problem. Should I call Sprints call center and see what they can do? Would they already know about the problem or are they going to pretend like they've never had an issue like it. Do I have to flash back to stock ICS or do they not care? Sorry about the questions, I'm just pretty new to having my own phone plan and my own problems and don't really know how to deal with them yet.
Click to expand...
Click to collapse
You have to unroot the phone or they will say the rooting its causing this problem or even worse they will say it's big no no to root phones and they will invalidated your warranty, show them this video http://www.youtube.com/watch?v=xKG-iq4XezU so they get an idea what the problem is
That is really odd, hadn't heard of that before. I instantly thought hardware, but it sounds like it has been proven otherwise. Is your device under warranty? If so, could be worth the hassle of a replacement, otherwise sprint call center is pretty worthless in general. They will give you pre made responses and tell you they were not aware of any such issue unless you get someone who actually gives any kind of a crap haha. Good luck! Be sure to post any updates!
Xynche said:
When I brought it in he said he can only do something if we could duplicate the problem. Should I call Sprints call center and see what they can do? Would they already know about the problem or are they going to pretend like they've never had an issue like it. Do I have to flash back to stock ICS or do they not care? Sorry about the questions, I'm just pretty new to having my own phone plan and my own problems and don't really know how to deal with them yet.
Click to expand...
Click to collapse
The only way to duplicate the problem everytime on my phone is to go to a low signal area. Ask the Sprint tech to go with you maybe buy them a cup of coffee and a donut.
Sent from my SPH-D710 using Tapatalk 2
Xynche said:
I've been having an issue with my softkeys (settings, home, etc...). They will randomly press opening settings, going back and opening the recent apps. Usually it does a combination of all of them and the only way to fix it is to turn off the screen and turn it back on.
I first thought this was a rom problem and switched to a new one. This didn't help so I believe it has to do with hardware. I looked up online and people say that it is a screen or battery problem. So I flashed to stock ICS and brought it into sprint, the guy was nice and stuff but he said he couldn't do anything unless we could make it happen. It wouldn't do it, so he couldn't do anything about it.
I'm wondering if it actually is a software issue or something that I'd be able to fix myself. Has anyone had any problems like this? It's not too often but often enough to be annoying. Any help would be nice.
Thanks in advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1877155&highlight=ghost
Ok, before I call in I have one last question. Will they send me a loaner phone? I need my phone for work and what not so if I cant get something temporary then I'm not even going to be able to send it in.
Not sure if this will answer your question but a co-worker recently had to take his OG EVO in for service. They gave him a loaner phone, an EVO 3D.
My wife's E4GT had the same phantom soft key issue. It was recently replaced due to another unrelated issue and so far, no issues.
Sent using my HTC EVO 4G and a magic wand
Very last question, I promise. Should I call Sprint or call Samsung directly? I'm most likely going to try and get it replaced this weekend. Hoping that everything goes well.
Short of a sledge hammer or selling the phone is there any remedy?
Phantom keys were crazy on my phone yesterday. I hadn't seen the problem very much in a week or so. I have no idea what was going on, but cleared dalvik cache and that seemed to help. No problems with it today. I wish I could figure out a correlation besides poor signal.
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
I get this issue when playing a game or typing.
pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.
Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.
Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.
danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.