Develop Bugs

GPS issues finally fixed with Froyo?

So, all those who have upgraded the firmware to Froyo, please answer this.....
Is your GPS/Google Map finally working in perfect condition?
If the GPS still have problem then i think we can probably say with high degree of certainty that it is a hardware based problem....
I mean with all the firmwares that they have leaked so far, wouldnt fixing the GPS issue be priority number one for them? If it was software/firware fixable, then i would think that they would have solve it by now....

widjaja74_us said:
So, all those who have upgraded the firmware to Froyo, please answer this.....
Is your GPS/Google Map finally working in perfect condition?
If the GPS still have problem then i think we can probably say with high degree of certainty that it is a hardware based problem....
I mean with all the firmwares that they have leaked so far, wouldnt fixing the GPS issue be priority number one for them? If it was software/firware fixable, then i would think that they would have solve it by now....
Click to expand...
Click to collapse
If they haven't fixed it yet for us on Eclair what would make you think FroYo fixes the problem?

heygrl said:
If they haven't fixed it yet for us on Eclair what would make you think FroYo fixes the problem?
Click to expand...
Click to collapse
The next official release will be Froyo, so it makes sense they do not work at eclair firmware anymore. So if they fix GPS it will be with the next official firmware and this should be Froyo.

Bajo76 said:
The next official release will be Froyo, so it makes sense they do not work at eclair firmware anymore. So if they fix GPS it will be with the next official firmware and this should be Froyo.
Click to expand...
Click to collapse
They need to patch the GPS before September. If they had a patch we would be hearing about an OTA and it would be included in later leaked firmware revisions.

the gps is fixed (at least for me) in JM2 already!

jodue said:
the gps is fixed (at least for me) in JM2 already!
Click to expand...
Click to collapse
Not for me. JM2.

Its much worse on froyo.
But its perfect on JM2 if you use -
http://forum.xda-developers.com/showthread.php?t=732030
and
http://www.intomobile.com/2010/07/21/t-mobile-samsung-vibrant-galaxy-s-gps-issues-fix-tutorial/

Are you going back to the SGS if/when they fix it? Thought you sold yours.... But im old and might have you confused with someone else
Sent from my GT-I9000 using XDA App

The GPS is still useless in Froyo. At least for me...

ml78 said:
Are you going back to the SGS if/when they fix it? Thought you sold yours.... But im old and might have you confused with someone else
Click to expand...
Click to collapse
Yeah my exact thoughts. Dude didn't you say 2 weeks ago that you sold your SGS? Did you even have one?

Yes sirs..... i sold mine couple of weeks ago ...
i couldnt find any good or better android phone ever since... all have their flaws in one way or another... so if they fixed the GPS issue, i might go back to this phone because it still offers the best features compared to others....
i'll probably wait to see until september wether they have fixed this GPS issue or not.....
Iphone 4 seems to have the phone signal problems taken care off in their later batches of production phones... so i might consider that phone too if that is really the case.....But still, i hate the thought of having to cut up my sim cards just to be able to fit in the phone... it will give me problems when i want to use the sim on other phones.... i think the use of different size sim card is totally dumb move on steve jobs.....its a differentiation feature that offers no benefits at all but headache....But coming from someone who said "you are holding it the wrong way" about a phone, it is no surprise for me......
So smart yet so stupid....

Wierd post..
Sent from my GT-I9000 using XDA App

GPS on my Galaxy S works perfectly on all firmware, so if gps does not work on yours it must be a hardware problem. Take it back.
Sent from my GT-I9000 using XDA App

Why with froyo, if is a software issue must be broadcom driver problem libgps.so ,
android interface with driver gps.h is clear(http://pdk.android.com/online-pdk/guide/gps.html).
So you "only" have to replace the driver and possibily related config files.
If GPS is capable of 24 satellites (bcm4751 seems a good GPS chip) simultaneus tracking why only can lock 8 (this is not explainable).
Excuse my poor English.

justmevagyok said:
GPS on my Galaxy S works perfectly on all firmware, so if gps does not work on yours it must be a hardware problem. Take it back.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
And ignorant comment of the day goes to.....drum roll please....
Sent from my GT-I9000 using XDA App

jodue said:
the gps is fixed (at least for me) in JM2 already!
Click to expand...
Click to collapse
please stop saying bull****....
the fix time is not the GPS problem
try copilot or navigon and use the GPS in your car, then you will how bad the GPS is

justmevagyok said:
GPS on my Galaxy S works perfectly on all firmware, so if gps does not work on yours it must be a hardware problem. Take it back.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
yeah sure .... using the GPS with GPS test in your house and having a fix in 10 sec is the main use of a GPS ... at least for all people saying it work
Just for information, the main use of a GPS is for car navigation, and there the GPS is kind of useless .....

widjaja74_us said:
if they fixed the GPS issue, i might go back to this phone because it still offers the best features compared to others....
Iphone 4 seems to have the phone signal problems taken care off in their later batches of production phones...
Click to expand...
Click to collapse
It's more likely that the flaw is in software than hardware, and samsung has said multiple times that they are looking into it, so i bet there will be a fix for it.
The problem with the iPhone is that you can't fix a design flaw, without new design, understand? See, when you connect 2 different antennas with your finger, you kill them both.
Anyhow, if you even consider iOS over Android, then i guess Android itself just isn't for you. The thing in Android is customization and if you don't like that, then you're better off with Apple products. I tend to recommend iPhone for girls and hipster friends, because they don't understand anything about personality or care about the latest and greatest hardware.
[offtopic rant]
In fact, Apple products scare me a little bit; so much fanaticism. I happen to work in a web development agency and we have to use mac's. Everyone except me in my office praises Apple and i absolutely hate it, mainly because my WIN 7 machine at home is just, well, multiple times faster and better for everything (crapbook in work is the latest and greatest). To me it seems that they are in some sort of vista (before SP1) hating time continuum; they can't escape, even though snowleopard is a joke update to the previous cute cat. They seem to hate all Microsoft, because of IE6 and vista(before sp1); even though they have **** like iTunes, QuickTime and well OSX(my honest opinion, have to use snowleopard every day).
[end rant]
Good luck!

pepitodequetequejas said:
Why with froyo, if is a software issue must be broadcom driver problem libgps.so ,
android interface with driver gps.h is clear(http://pdk.android.com/online-pdk/guide/gps.html).
So you "only" have to replace the driver and possibily related config files.
If GPS is capable of 24 satellites (bcm4751 seems a good GPS chip) simultaneus tracking why only can lock 8 (this is not explainable).
Excuse my poor English.
Click to expand...
Click to collapse
Is it for sure that our Galaxy is using this chip?
I also think that it is an driver problem. while starting gps test at the first moment it locks satelites with signal under 20 snr, but it loose them again and do not lock satelites under 20 snr anymore.

madfarmer said:
Wierd post..
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
May sound wierd for ignorant people who have not been following the story.....
Very sad.....

New GN froze had to pull battery...No big deal?

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

Defective Touchscreen?

Hey
I had some issues with the Touchscreen of my GNex, i thought it was nothing special, because i had something similiar on my xoom too but it only occurred 1 time on it.
Then i've tested the GNex for some Days and i'm now very sure it's a hardware defect, but i want to know what you think of it.
I'll try to describe it a bit:
Sometimes (i sadly don't know when or why) it launches a line of touch-inputs rapidly on the right side of the screen. It's really annoying because it starts a bunch of apps or commands...it even shuts down my alarm in the morning sometimes.
The big problem is, i'm on Vacation for 2 weeks soon...means i can't give it back to warranty now...maybe there is a way to disable the sensetivity of the touchscreen because these inputs are very light. With a testapp i was able to see that it's half as "heavy" as when i tap the screen with a finger.
I've attached a vid of it, maybe someone could say if this happens on their GNex too...i doubt no. (The vid is not that good, please apologize)
Link: http://goo.gl/QnTy7 (Sorry Attachment doesn't work somehow)

No one out there with a idea what's wrong with my gnex? :-(

I would go to verizon and see if there is anyway they could give you a replacement considering your circumstances. Or maybe they would give you a loaner phone while yours is being serviced.

Does it look a bit like this behavior?
https://www.youtube.com/watch?v=Z5_tUcosrtQ&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda premium

I would get a replacement phone from T-Mobile but that would be a real old phone and I have a nexus s here so maybe use this.
But would be nice to know if it's a hardware defect or if it's fixable....
I'll try to exchange it after my vacation.
Yes it's the same behaviour as in that video. I uploaded one too in the first post and mine is only a bit more right on the screen...
I'm really disappointed because my nexus s has some defects too and I'm curious if all Google devices has some defects....
Thanks for the answers

0 defects on my Nexus S
0 defects on my Galaxy Nexus

damn thats gotta suck :s
maybe flash any custom rom? hope you have your bootloader unlock or any pc close

I'm using CM9 since I got the GNex, will try reflashing it tomorrow with full wipe. Will report then.
Hope it's only the ROM, the screen works perfectly aside from this.

I didn't know you were running I custom rom, I would definitely try and do a full wipe and load the rom again or a different one.

The problem on my gnex went away after the ota update from 4.0.1 to 4.0.2.
Sent from my Galaxy Nexus using xda premium

Petrovski80 said:
The problem on my gnex went away after the ota update from 4.0.1 to 4.0.2.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I'm using CM9, latest nightlys. Did a full wipe and reflashed from scratch, same problem... maybe try stock or other rom when i'm back home..

[Q] Looking for SGH-T989 hardware knowledge

I have a very strange wifi/bluetooth problem that seemed to come out of nowhere and I think it may be hardware but I'm not too sure. When I format the system and install a new ROM everything works as it should for a little while but then within a few hours the software toggle switch grays out and wifi and or bluetooth don't respond. Bluetooth always seems to go out first but wifi follows soon after. I thought originally I had a corrupted driver or something but no matter how many different ROMS I try, going from gingerbread all the way to jelleybean and the phone always acts the same after a seemingly random amount of time. I don't know too much about how bluetooth/wifi drivers work so this may still be the issue.
Sometimes by toggling the various switches off/on a bunch wifi will go back on, and even more rarely bluetooth will work without a system format but it never stays working. If anyone knows what the problem may be I would appreciate some help or if you can point me to a component level diagram that would be helpful too. I have been looking around for a few weeks now with no luck. I never dropped the phone and it looks like I just pulled it out of the box. I did take it apart and look for loose connections and cold solder joints (I have quite a bit of experience at component level repair) but found nothing.
I did try to go back to stock GB with Odin and that was about the same, it worked for about a day and then the problems crept back up.

I thought for sure someone would have an answer.
Sent from my SGH-T989 using Tapatalk 2

I have a very similar issue but it only affects my Bluetooth. Sometimes it works, sometimes it doesn't. I haven't been able to pin point it. I've done the exact same steps as you. I just chalked it up to it being a hardware issue since I got my S2 from a lady that ran over the phone with her car. I just replaced the glass. She knew it could be fixed but she wanted me to have a better phone. What a sweet old lady. ANYWHO, I would love to see some more input on this.
Sent from my SGH-T989 using XDA Premium HD app

jmpsatx said:
I have a very similar issue but it only affects my Bluetooth. Sometimes it works, sometimes it doesn't. I haven't been able to pin point it. I've done the exact same steps as you. I just chalked it up to it being a hardware issue since I got my S2 from a lady that ran over the phone with her car. I just replaced the glass. She knew it could be fixed but she wanted me to have a better phone. What a sweet old lady. ANYWHO, I would love to see some more input on this.
Sent from my SGH-T989 using XDA Premium HD app
Click to expand...
Click to collapse
I switched to twrp and the problem isn't gone but it is better. I'm not sure if it's a coincidence or not but this seems like a positive step.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Touch "gets stuck" on letters while typing

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.