Related
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,
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
Hy guys I have seen on a noob guide that I can see my phone cpu "stats".
This tells me is my phone a powerfull machine or a bad brick.
So I have installed the faux kernel and with root explorer I came to this t3_variant
/sys/kernel/debug/t3_variant
If your cpu_process_id=
"0"- Sorry, but your in for a world of hurt. I'd recommend only trying out his mainline edition, nothing else.
"1"- Well, you''ll do just fine, but it still sorta shaky. Don't think about overclocking though, unless you're on a beta or VF version
"2"- Knock yourself Out! ;p
"3"- Lock that phone in Fort Knox and, if you see faux lurking around your house, then just run . Jokes aside, your phone can do ANYTHING.
Click to expand...
Click to collapse
This is a quote from a Noob Guide - here.
Mine cpu_process_id=0. Does this mean I bought 4500kn (597.32€ - Yes that's the price of HOX in Croatia) brick?
I have problems with battery he shuts down sometimes more like often, is he really that bad and I am angry right now cause I think I bought bad and expensive phone?!
If you need more info I will be glad to post just someone help me please.
LOL, those cpu variants are to be ignored. They are for hard core overclockers.
It has nothing to do with battery life and you do not own a phone shaped brick. I paid the same amount for my HOX.
Well can you tell me why does he act strange all the time. He just shuts down but he doesn't do that when he is on charger. I think I have some serious power issue. I'will give you all logs you ask and all screenshots just help please.
You might want to try another kernel and do a clean reflash of rom.
Give me the kernel reboot log from /proc/last_kmsg.
No need I think I solved the problem. I have now just moved the governor to interactive witch was default "ondemand". He didn't went off for like 6 hours witch is a record and battery is still 50% can't believe. I know I am noob sry for that
You might wanna try sense roms as well. You wouldnt be facing any random reboots issue.
faiz02 said:
You might wanna try sense roms as well. You wouldnt be facing any random reboots issue.
Click to expand...
Click to collapse
All those random reboots were on stock jb xD
Oh OK,
Case closed.
I am about to buy a new Samsung Galaxy Nexus on/before 25th Jan. (GSM, of course)
I am from India where the phone is not officially released. Hence, I am going to buy it from a well-known local store for $400 USD (22k INR) WITHOUT warranty (as I said, it's not officially released)
I have been lurking the Nexus sub-forums for a few days now.
I would like to know the following this:
What all things should I check as soon I buy the phone from the counter?
What do I do when the phone gets bricked or faces problems like bootlooping? What exactly would cause bricking?
I heard there are a lot of issues with 4.2.1 l(ike SOD). Should I upgrade to 4.2.1 or keep at 4.1.x? I heard t
TheMysteriousOne said:
I am about to buy a new Samsung Galaxy Nexus on/before 25th Jan. (GSM, of course)
I am from India where the phone is not officially released. Hence, I am going to buy it from a well-known local store for $400 USD (22k INR) WITHOUT warranty (as I said, it's not officially released)
I have been lurking the Nexus sub-forums for a few days now.
I would like to know the following this:
What all things should I check as soon I buy the phone from the counter?
What do I do when the phone gets bricked or faces problems like bootlooping? What exactly would cause bricking?
I heard there are a lot of issues with 4.2.1 l(ike SOD). Should I upgrade to 4.2.1 or keep at 4.1.x? I heard t
Click to expand...
Click to collapse
Well, from my point of view:
1) First of all check your screen, if you search the forum there're a couple of topics that explain how to find possible problem of it, then check with an application called eMMC Brickbug checker to see if your phone has a memory chip affected by a problem (resolved by XDA developers, if so, check the forum for the solution).
2) It's almost impossible to brick this phone, but if you fall in a bootloop you can connect your phone to your pc and use toolkit to restore backup, or just shut down the phone pulling the battery and then turn on pressing vol+ vol- and power button, then go to recovery and restore
3) It depends from your phone, in my case i've had SOD only with early trinity kernel, but i think that now every kernel is safe enough to be daily driver. So for me the 4.2.1 worth the try!
[email protected] said:
1) First of all check your screen, if you search the forum there're a couple of topics that explain how to find possible problem of it, then check with an application called eMMC Brickbug checker to see if your phone has a memory chip affected by a problem (resolved by XDA developers, if so, check the forum for the solution).!
Click to expand...
Click to collapse
I could find this:
http://forum.xda-developers.com/showthread.php?t=2093147
https://play.google.com/store/apps/details?id=com.bengigi.screen.diagnostic&hl=en
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester
Is there anything else that you suggest?
[email protected] said:
2) It's almost impossible to brick this phone, but if you fall in a bootloop you can connect your phone to your pc and use toolkit to restore backup, or just shut down the phone pulling the battery and then turn on pressing vol+ vol- and power button, then go to recovery and restore!
Click to expand...
Click to collapse
Alright, I'll search for some tutorials/guides to get information about flashing and restoring.
[email protected] said:
3) It depends from your phone, in my case i've had SOD only with early trinity kernel, but i think that now every kernel is safe enough to be daily driver. So for me the 4.2.1 worth the try!
Click to expand...
Click to collapse
I plan to use PA ROM. Haven't decided about the kernel yet.
1) I think it's enough, however if your screen has some problem you'll notice it as soon as you put your hand on your phone and turn it on... ;D
2) Yes, before doing anything that could harm your device it's better that you understand completely what you're doing.
3) Personally i use cataclysm(ROM) because it's not heavily customized but takes the android experience a leap ahead mantaining the google's look & feel, style and philosophy, and for kernel i use franco (but for the kernel you've to make some test beacuse each device react differently with each kernel)!
Now don't worry no more and enjoy your gnex (when it will arrive)
[email protected] said:
1) I think it's enough, however if your screen has some problem you'll notice it as soon as you put your hand on your phone and turn it on... ;D
2) Yes, before doing anything that could harm your device it's better that you understand completely what you're doing.
3) Personally i use cataclysm(ROM) because it's not heavily customized but takes the android experience a leap ahead mantaining the google's look & feel, style and philosophy, and for kernel i use franco (but for the kernel you've to make some test beacuse each device react differently with each kernel)!
Now don't worry no more and enjoy your gnex (when it will arrive)
Click to expand...
Click to collapse
I am thinking of shifting to CM10.1 because of CyanDelta where I don't have to download the entire nightly.
Any idea if there is similar function in PA or Cataclysm?
What is the procedure I need to follow to update my ROM?
How do I decide which is the best kernel for me? On what factors?
TheMysteriousOne said:
I would like to know the following this:
What all things should I check as soon I buy the phone from the counter?
What do I do when the phone gets bricked or faces problems like bootlooping? What exactly would cause bricking?
I heard there are a lot of issues with 4.2.1 l(ike SOD). Should I upgrade to 4.2.1 or keep at 4.1.x? I heard t
Click to expand...
Click to collapse
1) Quality check and warranty seal.
2) Flashing an incorrect rom, kernel or recovery can cause your phone to brick. You can unbrick all kind of soft bricks with the download mode and Odin, but be careful though. Some people got hard brick, and that's, as far as I know, irrecoverable (Maybe with a jig...)
3) Well, I am with Purity v4.0 and AK Kernel Purity v11 and no SoD. So far so good! If you upgrade to 4.2.1, you can flash another kernel and stay with stock rom if you like it. You just have to look which kernel is the best for your phone.
Good luck in your buy, it's an AWESOME mobile. I didn't know Android could handle soooo well (I comre from a Galaxy Ace )
TheMysteriousOne said:
I am thinking of shifting to CM10.1 because of CyanDelta where I don't have to download the entire nightly.
Any idea if there is similar function in PA or Cataclysm?
What is the procedure I need to follow to update my ROM?
How do I decide which is the best kernel for me? On what factors?
Click to expand...
Click to collapse
PA doesn't have that system but cataclysm yes, the dev produce a stable rom once a month (not always) and then just push cumulatives update (~20MB).
For the kernel it depends on you, if you prefer battery life or performance, smoothness of ui and so on, you have to try and take the one that fit best your parameters!
EDIT: i'm talking of PA before 4.2 came out since after that release i've jumped the ship to cataclysm! Maybe now has a system like this...
1. do i have enough booze at home, because you've gonna spent a lot of time with him
2. read enough before playing bad games
3. rasbean ftw
Can someone tell me what I should look out for to make sure I don't get a phone with performance issues?
Ref:http://forum.xda-developers.com/showthread.php?t=1971852
In the post you've referenced there's a section with the current workaround... that's it... install the application Got Brickbug by chainfire (linked in that thread) to ensure you've a bugged chip or not...
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.