Related
Yesterday got new system update now all my browsers are forcing close all the time anyone else had this problem
I'm not having force close issues but I've had to reboot like three or four times for various reasons. Once every time I would open the browser I would only get an all black screen. And earlier my status bar(or whatever you call that black bar that runs across the whole bottom of the screen) got stuck at half size and unusable after an alert tried to come up. There were a few more issues.
Wonder If Acer Removed Update?
Acer often screws up their updates - has anyone in US received update lately?
Seems like some issues
docfreed said:
Acer often screws up their updates - has anyone in US received update lately?
Seems like some issues
Click to expand...
Click to collapse
I haven't go it yet.
docfreed said:
Acer often screws up their updates - has anyone in US received update lately?
Seems like some issues
Click to expand...
Click to collapse
Nope, no update.
Same, no update here.
rrand said:
I'm not having force close issues but I've had to reboot like three or four times for various reasons. Once every time I would open the browser I would only get an all black screen. And earlier my status bar(or whatever you call that black bar that runs across the whole bottom of the screen) got stuck at half size and unusable after an alert tried to come up. There were a few more issues.
Click to expand...
Click to collapse
Just an update on this. This hasn't happened again.
I got the update maybe a few days ago, haven't had any problems with it so far except once when the browser wouldn't open any new tabs, then force closed, but that only happened once, after that it was fine.
no update yet fl
I am still waiting to get the update. I hope it is out soon. I hate the headphone issue i cant use at night while my wife is sleeping and this is y i bought a tab
max69power said:
I am still waiting to get the update. I hope it is out soon. I hate the headphone issue i cant use at night while my wife is sleeping and this is y i bought a tab
Click to expand...
Click to collapse
I wish i could remember how i got around that issue. Did you check around?
The way around it is to play the music/movie without the headphones plugged in. Then, plug them in and the sound will stop playing from the speakers and just the headphones. If you plug them in first, they still play through the speakers.
[email protected] said:
The way around it is to play the music/movie without the headphones plugged in. Then, plug them in and the sound will stop playing from the speakers and just the headphones. If you plug them in first, they still play through the speakers.
Click to expand...
Click to collapse
Happened to me while on a cruise.
There I was grooving to the Best of the Monkeys while reading on the Kindle app bebooping my head.
Yeah I'm that kool
Sounds interesting! Sure hope that I'll get it soon! Does the 3.2.1 update do anything to make the UI more smooth and fluid? After getting an iPad last week, Ive really noticed how choppy the UI in Honeycomb is, and all of the occasional slowdowns a lot more...
I m in canada and hasnt get update yet. Still 3.2 hopefully Acer will put Acer's circle to this update. I m very interesting when using Acer circle in Acer W500 ( touch 5 fingers to screen and it will display ^^)
vszulc said:
Sounds interesting! Sure hope that I'll get it soon! Does the 3.2.1 update do anything to make the UI more smooth and fluid? After getting an iPad last week, Ive really noticed how choppy the UI in Honeycomb is, and all of the occasional slowdowns a lot more...
Click to expand...
Click to collapse
Unfortunately, no. :-(
No updates recently?
Sent from Wicced's rooted A100 16gb HoneyComb 3.2 using XDA PREMIUM
rrand said:
Unfortunately, no. :-(
Click to expand...
Click to collapse
I do not know about yours, but my A100 is not laggy...
Acer support told me that Canada should get the update for 3.21 late dec early january.And that update packages are rolled out by region,and schedule is set by Taiwan.
Nor very encouraging as to ICS update then,which they would not comment on
freqchris said:
Acer support told me that Canada should get the update for 3.21 late dec early january.And that update packages are rolled out by region,and schedule is set by Taiwan.
Nor very encouraging as to ICS update then,which they would not comment on
Click to expand...
Click to collapse
We like to dream
Honestly it makes me so angry. There's so much work that goes into the development of these devices. Can you imagine what it must feel like to pour your heart and soul into engineering & development work, only to have the support folks fail it so hard?
ICS should have been released a week after the sources became available.
The headphone problem should never have made it out of QA. But it also should have been fixed within days of it being reported, and pushed out, worldwide, the moment it passed QA. Instead, this Canadian still has not received it (though I'm applying it manually, right now). It's been months since this problem was reported.
I know no manufacturer is perfect, and there are a lot of products to manage, but this is just irresponsible. Come on, Acer. You're not a charity. We paid good money. Now support your devices.
Hi everyone,
New GN,
ITLF41
19250UGKL1
yakjuux
4.01
I've only unlocked it, haven't done anything else.
I was only replying to a text message and in the middle of text, GN froze and the screen went black with a white line across top of screen.
Seemed to occur while the auto-rotate function was trying to rotate screen.
I also noticed the auto rotate on my GN does not work well at all. Sometimes it does, sometimes it will not no matter how long I wait.
Nothing worked, had to pull battery.
Seems fine after replacing battery.
I wouldn't be concerned but for the fact that I was not using 3rd party apps or a different rom. The force 2d option is off.
Is maybe something funky with the GN auto-rotate feature in 4.01?
test4echo said:
Hi everyone,
New GN,
ITLF41
19250UGKL1
yakjuux
4.01
I've only unlocked it, haven't done anything else.
I was only replying to a text message and in the middle of text, GN froze and the screen went black with a white line across top of screen.
Seemed to occur while the auto-rotate function was trying to rotate screen.
I also noticed the auto rotate on my GN does not work well at all. Sometimes it does, sometimes it will not no matter how long I wait.
Nothing worked, had to pull battery.
Seems fine after replacing battery.
I wouldn't be concerned but for the fact that I was not using 3rd party apps or a different rom. The force 2d option is off.
Is maybe something funky with the GN auto-rotate feature in 4.01?
Click to expand...
Click to collapse
Yes, versions 4.0.2 and 4.0.3 fix a LOT of little issues with the GN. They really should've released the phone with one of those 2 versions rather than 4.0.1.
I don't think you should be too worried about battery pulls unless they happen more often than you like.
Just like a computer...rebooting or pulling the battery at least once a week is recommended!
sent from my Nexus Prime
Simer03 said:
Just like a computer...rebooting or pulling the battery at least once a week is recommended!
sent from my Nexus Prime
Click to expand...
Click to collapse
? when do you pull a battery out of a computer?
... haven't received a reboot since day one.
OJ in Compton said:
Yes, versions 4.0.2 and 4.0.3 fix a LOT of little issues with the GN. They really should've released the phone with one of those 2 versions rather than 4.0.1.
I don't think you should be too worried about battery pulls unless they happen more often than you like.
Click to expand...
Click to collapse
Ok great!
This is my first smart phone EVER....lol
Its a tough go catching up with all I've missed.
Thanks!
Simer03 said:
Just like a computer...rebooting or pulling the battery at least once a week is recommended!
sent from my Nexus Prime
Click to expand...
Click to collapse
You really shouldn't be forcefully pulling the battery every week, that's terrible advice!
Goddamn it.....that's why I said "reboot" first! Lol!
sent from my Nexus Prime
Simer03 said:
Just like a computer...rebooting or pulling the battery at least once a week is recommended!
sent from my Nexus Prime
Click to expand...
Click to collapse
I'm a Network Admin for a large School Board. I know its strange I know nothing about smart Phones but I do know much about Wireless/Routers/switches and Computers.
If your rebooting computers once a week something is amiss....lol
I have servers and clients that have uptimes of 1 year+ before an update requires me to down a server or re-image a client.
In my case, if what had happened to my NEW GN happened on one of my OES2 Linux servers, Id be scrambling until the issue was found and fixed and i'd be none to happy.
But alas, a server is not a cell phone.
I hope it was a just a freak isolated incident.
You guys...I wasn't saying that u HAD to...if u HAVE to, then there's problems....but if u do it just because, it'll get rid of the little things, like the bug he has
sent from my Nexus Prime
Simer03 said:
You guys...I wasn't saying that u HAD to...if u HAVE to, then there's problems....but if u do it just because, it'll get rid of the little things, like the bug he has
sent from my Nexus Prime
Click to expand...
Click to collapse
LMAO...agreed!
I work for tmobile, at&t and Verizon! I've dealt with dumb little bugs that people have....pulling the battery is the first thing I tell them to do and 99% of the time, it fixes their bug! So why not just save yourself the time and be one step ahead of the phone!?
sent from my Nexus Prime
Simer03 said:
I work for tmobile, at&t and Verizon! I've dealt with dumb little bugs that people have....pulling the battery is the first thing I tell them to do and 99% of the time, it fixes their bug! So why not just save yourself the time and be one step ahead of the phone!?
Click to expand...
Click to collapse
One very simple reason: If you pull the battery in a bad moment, e.g. right when the hardware is writing something to the Flash memory, you might (soft-) brick your phone and lose all the data on it.
Simer03 said:
I work for tmobile, at&t and Verizon! I've dealt with dumb little bugs that people have....pulling the battery is the first thing I tell them to do and 99% of the time, it fixes their bug! So why not just save yourself the time and be one step ahead of the phone!?
sent from my Nexus Prime
Click to expand...
Click to collapse
Well because,
If I have to keep pulling the battery (which is NOT occurring thankfully so far) then I would say something is wrong and its not just a software bug. I would call it a blue screen of death in computer terms.
That could be anything from a hardware fault (Memory/CPU/IO sub system..etc) That would for me, mean taking it back.
A hard reset may temporarily fix the issue. But it doesn't solve the underlying problems.
I'm hoping the error was a one off. If it never occurs again, then we're good to go.
If it does, its goin back.
Same thing happened to me, the weird thing is it happened right after I completely reset the phone...
Sent from my Galaxy Nexus
big samm said:
Same thing happened to me, the weird thing is it happened right after I completely reset the phone...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yea its strange...
In my case the Auto rotate feature seems to be the common theme for funkyness.
Sometimes its quick, less than a second, sometimes it doesn't move at all.....
Then, a hard lock.
I realize that 4.02 and .03 fix some bugs but I have the Canadian ver. and google is not gonna update OTA for my NG.
I'm not ready for the whole, flash to "google's" stock rom yet. I just learned to unlock it...lol. If it locks again i'll try that. If it don't i'll leave well enough alone.
Oh by the way, to the Admins, sorry for not posting in the Q&A section. I though i was in the Q&A, my mistake.
Please by all means move the thread.
zephiK said:
? when do you pull a battery out of a computer?
... haven't received a reboot since day one.
Click to expand...
Click to collapse
Actually, I have to replace cmos batteries all the time.
Usually they are good for 4 or 5 years but sometimes not.
Some people don't know what "Hit F1 to continue" means and I get calls all the time.
So yes, its quite common to have to pull a bad battery when dealing with 2,000+ PC's ...
Simer03 said:
I work for tmobile, at&t and Verizon! I've dealt with dumb little bugs that people have....pulling the battery is the first thing I tell them to do and 99% of the time, it fixes their bug! So why not just save yourself the time and be one step ahead of the phone!?
sent from my Nexus Prime
Click to expand...
Click to collapse
Because I use a otterbox with my Galaxy Nexus and it's not very pleasent to keep taking my phone out of it's hard shell case and putting it back in?
Pulling the battery is always a last resort. If the phone is frozen, that is fine to pull the battery or you can hold power on the phone and it'll turn off by itself (not sure if this is in the GN but it was in Galaxy S1).
@test4echo: That's not the experience of a daily person. Not everyone deals with 2,000+ people on computers.
zephiK said:
@test4echo: That's not the experience of a daily person. Not everyone deals with 2,000+ people on computers.
Click to expand...
Click to collapse
You are correct. Its not a common everyday thing for most.
I was just suggesting a legit reason for why anyone would need to pull a computer battery.
On another note, i agree with you that having an otterbox case makes it even more of a pain to have to pull the battery.
I just had another freeze up while trying to get back to the main page using the launcher.
Im getting worried now. I've had this phone for 2 weeks and it was great until today....
I think I'm gonna bring it back to virgin just to be safe before my 30 days is up.
If its just software then the new one will do it as well but at at least I'll know thats what it is and either wait for samsung updates or update manually.
Again....nowhere in my response did I say u HAVE to pull the battery every week....I simply said its best if u do, nobody is gonna force u to! But when u do get a bug...pull that battery, and if it keeps happening, send it for warranty...simple
sent from my Nexus Prime
Guys, I was all set to get a new 32gb Nexus 7....the reviews are great, and then I start reading about the issues.
After a bit more reading, I'm left wondering if its such a good idea? I read that Google released an update, then I also read that it didn't always fix things for people?
So the questions I guess are, Do you own one? Have you had a problem? Is it now fixed by the update? Maybe you've never had any problems?
Would you recommend getting one? I don't wanna spend out on something that I'll regret.
Thanks guys.
I've had mine since the first weekend of availability and it's lived up to all my expectations and then some, you're just buying the usual support vocal minority, sume have legit issue, noisy are just being nitpicky
Sent from my HTC One using Tapatalk 4
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Thanks for your reply.
Mine worked 100% out of the box, no light bleed, no multi-touch issues, no GPS issues. Updates have installed perfectly. I am running stock deodexed + root + TWRP + Elemental X 1.1 Kernel. Couldn't be happier with my purchase. :good:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
madpete said:
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Click to expand...
Click to collapse
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
I bought the 32gb. Works flawlessly, I got it a week and half ago.
Sent from my Nexus 7 using xda app-developers app
GET ONE
I would say go for it, you are always going to have issues with most anything. Just buy from a retailer with a good return policy, I own the nexus 7 2012 and the nexus 7 2013 , no issues here, awesome devices.
Thanks guys. Sfhub, you make some good points....think I will buy from a large high street store, rather than online.
Sent from my GT-N7100 using XDA Premium 4 mobile app
sfhub said:
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
Click to expand...
Click to collapse
i think mine is definitely, hardware, maybe , cuz of user error, ie, bad dirty flashing of zips, i dont' want to start all over fresh again, too many apps/settings to revert back (yes call me lazy sob)
most of the reboots happen when im clicking on an app with wifi on , but one of my last reboots, it just just rebooted out of the blue, i didn't even touch the tablet, but i seen it reboot!
Not sure, really, whether I have/had problems or not. Got mine over the weekend. During my initial playing, I did not notice any touch issues. The GPS would lock, but I didn't have time to take it anywhere for long enough to be sure if it would stay locked for a long period of time. Almost immediately (1 day) I got the JSS15Q OTA update. The GPS DOES seem to lock a bit faster, and I seem to be seeing more satellites than before -- it could be my imagination, though. Still no touch issues that I can see.
New Nexus 7 (then) past issues, (now), Cool TAB!
phab3k said:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
Click to expand...
Click to collapse
I HAD issues out of the box. Waited for the first update from Google, rebooted once after. Took forever to get the screen to respond to any kind of tap. Rebooted a couple of times and was able to get somewhat R E A S O N A B L E response out of the screen. GPS would work for all of 2 minutes and then shut down. No problems with Wi-Fi.
That was then, along came update: JSS15Q! All is happy in Nexus land. GPS is strong and works flawlessly even in the darkest center of my house! Screen is responsive my fingers are happy.
APPS? That is another matter, remember, even with a stock Nexus 7 fhd you are on the bleeding edge meaning that many apps found on Google Play may fail. Live with it until either the app is updated, ***** at the (no don't *****, contact the developer and kindly tell him/her your problem; or find another app that works for now.
Games? Heh, that is a real crapshoot. If it won't function, move on.
This is one hell of a tablet with excellent video, good sound, fast processing. Short of it not being the size of my 60" monitor (TV) I can read everything with these 78 year old eyes!
[email protected]@dog!
Google Nexus 7FHD
Kindle Fire Rooted Android 4.3
Kindle Fire HD 8.9 Rooted 2nd boot loader Android 4.2.2
Droid Bionic stock Android 4.1.2
Guys, just wanted to say thanks for all the posts. You help me make up my mind, and gave some sound advice.
I've took the plunge and brought the 32gb model (from a big high street retailer), and I have to say....what a cracking little tablet this thing is, I am really impressed with it. I have not had any issues with it, so I seem to be one of the lucky ones....either that or they have fixed the issues by the time we got them in the UK.
I do feel for all the people who had problems though, its a nightmare when these thing happen. Theres no doubt there has been or are some issues out there, one thing with a Nexus device I guess is it is patched fast if its sw...obviously hw is a different issue.
Looking forward to enjoying this device now, if I can get on it....have to wrestle it off the wife and kids first!
......thanks again guys.
Pete.
Just got my 32gb Nexus today in the UK. Only thing I have noticed is that tap and hold on screen is slow to react. Can take a couple of trys before it works. Sometimes taping an app is slow to open. Running stock and latest update. Only change made is to use Nova as the launcher.
Sent from my HTC One S using Tapatalk 4
To Wugfresh Re: Toolkit
This is a followup to my 2 confusing Twitter's I made it worse by referencing Nexus 4 and 7 so I will stick to 7 (mostly). I now realize that lurking has its penalties since I need 9 posts after this before I can post this in the relevant thread (with a nostalgic tear for the days we welcomed all comers and left our doors unlocked).
I bought an N7 FHD (2nd gen) and rooted it after the 4.3 auto update soft bricked (right term of art?) it. I used the other toolkit to restore it to JDQ39 factory unrooted. Then it installed JSS15J. Today it tried to do an update and (presumably) it failed because of rooting. That build is no longer on the developer's website and has been replaced by JSS15Q. I would never presume to call myself a developer but my first modem was a 300 baud acoustic coupler and I have a 5 1/2" floppy disks older then most of you and it's actually floppy. ROFL.
Back to reality, on the Nexus 4, I could not discern how to upgrade to the latest Y build but I did manage to restore it to factory settings and Google handled the rest, You were kind enough to add JSS15J to your toolkit for the Nexus 4 but it is not available (in your drop-down) for the Nexus 7. I figured that if you made JSS15J available for the N7 I could restore the N7 to a factory fresh un-rooted one and Google could update it to JSS15Q. In the alternative you might guide me to how I could go from JSS15J to JSS15Q. I am certainly not in your league but this is not my first rodeo and I cannot tell you how grateful I am for your efforts. Your toolkit saved my Nexus 4 from the 2 week wait during which Google might have told me rooting voids the warranty or just have left me phone-less till they returned it.
Again thank you especially, and to all the others here who light candles in the darkness for each other and the rest of us pilgrims. A tip of my fedora to ya. Never forget one definition of a pioneer is someone with an arrow in their back.
Much of the time I am as confused as a baby in a topless bar who said, "What do you mean this is not a lunchroom, what else could it be?"
My suggestion is to keep root, grab the latest carbon ROM, the elemental 1.1 kernel and you should be all set. They already have the updates From G in them and they work superb.
Sent from my Nexus 7 using Tapatalk 4
Do you own one?
Yes, from day one.
Have you had a problem?
Yes, GPS and the touchscreen grounding issue.
Is it now fixed by the update?
Yes, GPS seems fixed.
No, grounding issue may be worse. Works fins as long as I'm holding it. Placing it causes touches to become sporadic.
Maybe you've never had any problems?
I wish...
Would you recommend getting one?
Yes, it still a FANTASTIC device and many have no issues. If you do return it right away until you get one without issues.
I spoke too soon....at first I thought everything was ok....then I began to notice when I was typing that sometimes it would come out as gibberish. I thought nothing of it as we all make typos now and then, then I noticed that press and hold didn't always register (sometimes takes a few goes). I downloaded the multi-touch test from play and to my horror it's all over the place (compared it against my note 2), this is with the latest update. After reading around a bit more, I'm beginning to think these touch screen issues are hardware....and that it's more widespread than people think. Will be exchanging it for another one, hopefully fair better second time.
Sent from my GT-N7100 using XDA Premium 4 mobile app
madpete said:
Will be exchanging it for another one, hopefully fair better second time.
Click to expand...
Click to collapse
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
sfhub said:
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Hey man, thanks for the reply.
I opted for the swap out because I don't want to loose the warranty, which I believe you would if you unlocked it?
I bought from PC World / Currys so the swap was no hassle.
Using the new one now, its testing better and typing and "hold and drag" is working much better (although hold and drag still isn't 100%, it's now acceptable to me).
I tested before and after the update, the observation I made is that the update seems to dull down the touch screen a little. It became slightly less responsive after the update than before, but hasn't really affected the usability on this one....although I think I prefered it pre update.
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.
I've had Honor 7x for about a week now and I love the phone. I experience no lags or any other issues except one. Touch screen sometimes acts up and is not responsive and sometimes I have to touch the same spot like two or three times to get it to work and it's so frustrating.
The only way that I'm able to make it work well as it should again is by restarting the phone, and then it's all good until next day or so.
Have you guys noticed the same symptom?
May I Ask....
pcaseiro said:
I've had Honor 7x for about a week now and I love the phone. I experience no lags or what so ever except one issue, touch screen sometimes acts up and is not responsive and sometimes I have to touch the same spot like two or three times to get it to work and it's so frustrating.
The only way that I'm able to make it work well as it should again is by restarting the phone, and then it's all good until next day or so.
Have you guys noticed the same symptom?
Click to expand...
Click to collapse
Short Answer For Me.. No.
Are you still within your return period ? Swap it out for a new one.. and see if it's any better.
If Not... Sell It.
Didnt have any issue as such..
Get it checked..
I am having the same issue now I believe. Phone worked great for about two weeks then started having screen issues. I have to push a little harder and slower than normal or touches don't want to register. The buttons along the bottom and the pull down menu at the top of the screen seem especially bad. A reboot clears it right up for a time. I'm past the return period so I have to send it in for a warranty repair. Were you able to get the issue resolved with your phone? I'm a little worried with it being a sort of intermittent issue they won't be able to reproduce the issue and won't fix it.
Yes it is buggy !
pcaseiro said:
I've had Honor 7x for about a week now and I love the phone. I experience no lags or any other issues except one. Touch screen sometimes acts up and is not responsive and sometimes I have to touch the same spot like two or three times to get it to work and it's so frustrating.
The only way that I'm able to make it work well as it should again is by restarting the phone, and then it's all good until next day or so.
Have you guys noticed the same symptom?
Click to expand...
Click to collapse
Hi,
Yes, I'm also facing the same issue and thinking that removing the tempered glass may help.
Also, there are lags and lack of responsiveness in this device time to time and I don't feel it as a Hardware issue. Its just that if you are not used to clearing out apps from recents, unlike 90 percent of the other users and if you ever felt the phone's hardware/software competent enough to handle those by itself and at the same time, maintaining the performance, then you are wrong.
Now after a good 2 months of usage, I can say that we will have to wait for a slim pure AOSP rom for this device to please us. Its not at all a balanced device and indeed its a total flop. I feel no joy( and sometimes want to throw it on the wall also) in using it now because of these 3 issues :
1. Time to time lag/hanging - due to not clearing recents frequently - Since I do not believe it is really required for a phone with 4GB ram and Kirin, equal to SD 652 processor. My OP2/ Mi Max and all others used to be much much better than this piece of sh**.
2. Touch not snappy and feels like less responsive for a fast user. May be perfectly fine for the one's using it in a relaxed way.
3. Notification quick reply screen timeout because of not recognising it as an active function.
- From a quite unhappy first time honor user !
I got in touch with customer service and they advised me to factory reset it.
After that phone actually felt better with no issues.
However, I was still within the 15 day return window and I didn't want to take the chance, I sent it back and bought another one.
With the new phone all I can say is that I love the phone. No touch screen issues, no lag what so ever, it is extremely fast and even after I cranked it up with apps it didn't get any slower. I can say that it's faster than my broken Nexus 6p.
Love it
Glad you got a new one sadly I missed my return window. I tried a factory reset and only installed a podcast app different from the one I normally use and actually Uninstaller a few factory apps like Facebook, Instagram and couple Google apps docs and sheets. Still had the issue after some use. Always seems to happen after 20-30 minutes of phone calls. I have contacted support and will most likely be sending it in. I'm getting the b140 update as I type this and the change log says "Performance optimization changes has been included in the current software" so maybe that will fix it. What are the odds. Is it hardware is it software I don't know but I would think if it were hardware a reboot wouldn't make the issue go away for a while but that's probably flawed logic. Also I'm using the US variant (L24) 32gb/3gb.
Touch Screen Issuess
pcaseiro said:
I've had Honor 7x for about a week now and I love the phone. I experience no lags or any other issues except one. Touch screen sometimes acts up and is not responsive and sometimes I have to touch the same spot like two or three times to get it to work and it's so frustrating.
The only way that I'm able to make it work well as it should again is by restarting the phone, and then it's all good until next day or so.
Have you guys noticed the same symptom?
Click to expand...
Click to collapse
I was having a touch issue, but changed in the settings-Smart assistance-touch disable mode (un toggled it)
Well it's been a couple of days since I received the b140 update and so far my screen hasn't acted up. I'm not 100% sure it's fixed but so far so good.
jmjj27551 said:
I was having a touch issue, but changed in the settings-Smart assistance-touch disable mode (un toggled it)
Click to expand...
Click to collapse
This seems to have resolved my issue also. Thanks for the tip!
Since it seems software related, and I imagine this 'feature' is to detect whether you 'meant' to touch the screen or not, it would make sense that this is potentially the problem. In my case especially, I would describe the issue as it seems like my screen falls asleep if I take too long between interactions.
Edit: this actually didn't resolve the issue
-tg
Unfortunately after further testing the issue persists. Most noticeable in clash of clans, Facebook, Snapchat, other slightly higher resource usage apps.
tjg06c said:
Unfortunately after further testing the issue persists. Most noticeable in clash of clans, Facebook, Snapchat, other slightly higher resource usage apps.
Click to expand...
Click to collapse
Still digging in on this, I enabled Show Taps from the developer options and the malfunctioning taps actually do show up when they occur. I sent an email to support 2 days ago with no response yet. Will probably have to call I guess. womp.
-tg
got my phone more than 15 days ago, issue started becoming more prevalent this past week. notably when i'm playing rhythm games (lol). thought ir was the tempered glass screen protector but its now happening with a film/wet application protector. i can't replicate it consistently either. would be interested in updates, this is really frustrating.
sgchrom said:
got my phone more than 15 days ago, issue started becoming more prevalent this past week. notably when i'm playing rhythm games (lol). thought ir was the tempered glass screen protector but its now happening with a film/wet application protector. i can't replicate it consistently either. would be interested in updates, this is really frustrating.
Click to expand...
Click to collapse
I still haven't received an email response, however if you go to the site via mobile you are presented with a live chat option during their business hours (listed on the site https://www.hihonor.com/us/support/index.html). I used that to arrange the repair return for the phone. They don't simply replace it which is kind of frustrating, so I guess it's back to my trusty nexus 5 for a week or two. ?
-tg
i've done some looking around -- i know this thread is much older than the recent UI update, but it looks like the most recent update has messed up the touch sensitivity completely. loads of people are complaining on the hihonor forum. hoping this'll be something they can fix with a patch.
really hoping that i won't have to send it in, this is a replacement for my old phone since the charge port was completely shot. so i'd have to buy a new phone anyway...
thanks for the update, hope this all gets fixed soon!
This appears to be related to the most recent update. That is when it started becoming more of an obvious issue.
Oreo will fix this surely... I had same but now its fixed ?
Touch sensitivity
I'm having the same issue, my screen touch is not sensitive I used to have moto g4 it's been a couple of yrs since I bought it even that screen touch sensitivity is better than this. But overall features camera screen everything is good except the touch sensitivity, I need to click everything a couple of times to respond and even while texting I'm missing out some letters. BTW I won't use any screen guard or tampered glass and it's been a week since I'm using honor 7x.Apart from the screen sensitivity issue I'm damn satisfied with the product.
Thanks,
Aditya
verma.arun833 said:
Oreo will fix this surely... I had same but now its fixed
Click to expand...
Click to collapse
I can also confirm that this is a software issue and is resolved by the Oreo update (currently beta, link below), at least for my case of ghost taps registering on different parts of the screen than what I am actually touching. I've been running Oreo for a week now and this is definitely the phone I was hoping for when I bought it :good: I've been emailing details regarding this issue with a member of their beta support team and it has been relayed to development. Hopefully they can/will release a hotfix for nougat in the meantime.
Oreo is currently in beta. The forum post regarding beta enrollment :
https://forum.xda-developers.com/honor-7x/how-to/how-to-beta-test-emui-8-0-oreo-based-t3757323
I used to have similar problems, particularly when I try to scroll by sliding it would actually open the link if there is one where I first touched. Also writing was difficult on SwiftKey, it would jump over and behaved as if I hit enter.
I joined oreo beta and upgraded yesterday, all these problems seem to have disappeared. Fingers crossed, will wait and see a few more days.