Related
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.....
Anyone know if this is a general WP7 problem, or if it's just the Trophy doing it? It's getting on my nerves, and I'm wondering who to blame
tiwas said:
Anyone know if this is a general WP7 problem, or if it's just the Trophy doing it? It's getting on my nerves, and I'm wondering who to blame
Click to expand...
Click to collapse
Lol I'm sorry for you.
My device never rebooted itself.
And freezed only once. The only unreliable behaviour I noticed was Marketplace - widely documented problem - and Weather Channel quit working once...
So I have no idea what causes that.
But it may be an app, badly written.
You're probably looking at a hardware problem. This happened to a number of HD2s too. I'd take it back to the store you bought it from, explain the problem, and use your warranty to get a new one.
Well, the reason I'm asking is that there are a lot of people in the Trophy forum reporting this behavior - in addition to me. If it doesn't happen to other devices, it's probably a design flaw, but I'm not taking my phone in until I can back it up
tiwas said:
Well, the reason I'm asking is that there are a lot of people in the Trophy forum reporting this behavior - in addition to me. If it doesn't happen to other devices, it's probably a design flaw, but I'm not taking my phone in until I can back it up
Click to expand...
Click to collapse
What do you need to backup. All your purchases can be re-downloaded for free. Contacts, emails, pictures, videos, etc. can be resynced. That's the beauty of the 'cloud'.
tiwas said:
Anyone know if this is a general WP7 problem, or if it's just the Trophy doing it? It's getting on my nerves, and I'm wondering who to blame
Click to expand...
Click to collapse
My LG optimus 7 rebooted randomly like yours. Now back in repairs, I'll suggest you send it back while it's still under warranty
Mine has rebooted itself a few times and I have a Samsung Focus. Personally I think its a memory management issue. Generally happens after running a lot of apps and the phone hasnt had a reboot in a while.
randude said:
Mine has rebooted itself a few times and I have a Samsung Focus. Personally I think its a memory management issue. Generally happens after running a lot of apps and the phone hasnt had a reboot in a while.
Click to expand...
Click to collapse
WP7 clears any memory aps use after the phone exits a program. And without multitasking, memory is not an issue. It's a hardware issue... usually with the internal processor.
I don't think it's a software flaw either, as a lot of people don't have this problem. Also, there are no programs running in the background, so that clears that issue. I suspect the phone developers have been in a hurry and have just pushed out handsets that are really just beta versions.
My LG Optimus 7 reboots from time to time, too.
My TMOUS HD7 has done this like 3 times in about a month and a half if that makes a difference to anyone. T-Mobile replaced my HD2 when it was doing this and the newer HD2 never did it.
Do you guys have bluetooth enabled? Just hit me yesterday that my problems started when I turned bluetooth on...
My bluetooth is off and I have this problem.
Ok, might be coincidence, but my phone seems to have stopped rebooting after I turned BT off. Not a single one in the last four days
Hi everybody,
I bought a Note 2 in october 2012. I installed the ROM HD Revolution. Until now there was no problem.
Few days ago, my screen has swiched off and there was lot of reds pixels everywere on the screen.
The phone of course was rooted and the garantly not applicable.
So in the samsung shop, i explain that the phone was rooted... The techniciens has puted a new screen thinking that the problem was coming from a screen hardware. This new screen has well worked during 20 mn, after that, same trouble, the screen was killed....
My phone was sent to another tehcniciens ( more specialists and i think, working directly with samsung) in france, who can works on the motherboard. But just before to sent it, the technical personnal has succefuly replace the rom Revolution by another official ROM by Odin. (In order to keep my garantly.....wonderful techniciens)
Today the phone was return to me, with just a new screen. The third screen after mine who was killed in first.
No motherboard trouble, no graphic chipset trouble was fixed, only the HD Revolution ROM who is apparently , and i 'am sure now, has killed the screen
I'am not able to explain why and how, I am not found on the web or another forum the same trouble.
Somebody know what's happened?
thanks
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
silentecho13 said:
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I'am sure, very sure that the problem on the screen is due to the ROM Revolution, otherwise explain me why the third screen has no trouble after changing only the ROM with the lastest samsung ROM?
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
SacGuru said:
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
prbassplayer said:
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
Click to expand...
Click to collapse
It was the REVOLUTION HD Rom.
You think that the Samsung technicians when they changed the screen after the other first technicians has not been honnest?
It's incredible, i don't believe in this idea... I cannot see the interest... But if you are talking about the kernel maybe it yes...
It's a crazy story...
HD Revolution....? wait.. isnt it for a international version of Note 2?
No wonder why your phone is acting up. Flashing almost non compatible ROM on your device doesnt give you rights to discredit Dev.
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
cwhitney24 said:
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Click to expand...
Click to collapse
I use the recovery mode after have put the zip's ROM on my SD card.
And i never use the o/c
I 'am sure that the trouble has been caused by the Kernel or the ROM... I don't remember what was the kernel... i thinking...
prbassplayer said:
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
Click to expand...
Click to collapse
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
aquasirius said:
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
Click to expand...
Click to collapse
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
mike1986. said:
No mate, LTE version is not supported.
Click to expand...
Click to collapse
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
Relax man, I did not think you were lying, neither did I accuse you of it, I merely asked you to, and personally believe,that the developers on this forum (who are people like you and me) are anyday more trustworthy than repair men who are from samsung or freelancers (read people bent on profiting from me screwing up my cellphone). Thus I asked you to visit the developers thread and look for comments about the issues you were facing, that is what I would've done.
Apparently you flashed a ROM which was not meant for your particular model. Whether that is true or not, I am sorry for all the trouble you had to go through with the engineers and all. I hope your note 2 functions great from now on.
Je vous présente mes meilleurs vœux pour l'année 2013
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
prbassplayer said:
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
Click to expand...
Click to collapse
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
aquasirius said:
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
Click to expand...
Click to collapse
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
prbassplayer said:
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
Click to expand...
Click to collapse
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Dumbo53 said:
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Maybe you right, and the phone has been exposed every time in good condition, and never droped or jared. I will see with the time if it was a another hardware problem.
I think actually the association ROM/kernel has revealed an intrinseq hardware problem on my phone and maybe later even with a samsung rom the problem should be appear again....
aquasirius said:
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
Click to expand...
Click to collapse
Wait.....Your Note 2 is an N7100? Then why did you come to an i317 forum to complain about a ROM somehow breaking your screen?
If you really think you have a legitimate concern that a ROM may have damaged your phone in some way, contact the developer. Maybe it has happened before. Maybe the developer can make changes to prevent it from happening to others. What you probably shouldn't do is to make claims that a ROM damaged your phone on a forum for a different model of phone.
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.
Hey guys, so....
I don't know if I'm screwed or what. I have an original notes of a not a replacement 1. I got it about a week before The 1st recall. I returned to Verizon about 4 times in the past month and a half to try to get a replacement device [ with the new battery or whatever they did to the replacements ]. However every visit I was told they didn't have my color, gray, in stock. Now it's two months out and there's a total recall on it and I have an original device. I like the phone and wanted to keep it. What the heck do I do now? I've read through some of the threads about keeping the replacement note 7 or not, but I haven't seen anybody with an original one. Is your anybody else with an original note 7 that's going to keep it? And do you guys think that development will continue after all that's happened?
TLR - I still have an original note 7, not replaced (they never had my color), Do you guys think it's safe to keep it and do you think development will continue or die off early ?
Thanks for any advice. Man I really like this stylus ....
outamoney said:
Hey guys, so....
I don't know if I'm screwed or what. I have an original notes of a not a replacement 1. I got it about a week before The 1st recall. I returned to Verizon about 4 times in the past month and a half to try to get a replacement device [ with the new battery or whatever they did to the replacements ]. However every visit I was told they didn't have my color, gray, in stock. Now it's two months out and there's a total recall on it and I have an original device. I like the phone and wanted to keep it. What the heck do I do now? I've read through some of the threads about keeping the replacement note 7 or not, but I haven't seen anybody with an original one. Is your anybody else with an original note 7 that's going to keep it? And do you guys think that development will continue after all that's happened?
TLR - I still have an original note 7, not replaced (they never had my color), Do you guys think it's safe to keep it and do you think development will continue or die off early ?
Thanks for any advice. Man I really like this stylus ....
Click to expand...
Click to collapse
I'm in the exact same situation as you. I still have the original model Note 7 and have tried multiple times to exchange it for the "safe" model. At this point given the evidence, I believe that both models are equally safe (relatively). New models and old models catching on fire combined equaled around 90 cases out of about 2,000,000. I'm not sure if the failure rate on the updated models went down, but I feel that failure rate in general is about on par with other devices.
I have read about Apple phones in the past catching on fire. The difference is Samsung tried to be super responsible in this situation by taking ownership and the media and such has definitely exacerbated the situation. Apple never took ownership of any of the battery failures that happened with their devices, and mostly blamed it on the user using 3rd party accessories and such.
I may be wrong, but I believe the issue was blown out of proportion. I'm not saying the phone is safe, but I'm also not saying that this phone is way more unsafe than any of the others.
So, given the statistics and history of the two different models, if you disable fast charging on the device I believe the two different models are on equal ground as far as failure rates go. Which are higher than they should be but still fairly low.
jal3223 said:
. New models and old models catching on fire combined equaled around 90 cases out of about 2,000,000.
I may be wrong, but I believe the issue was blown out of proportion .
Click to expand...
Click to collapse
I even thought it was less than that and I'd take those odds, I don't think theyre too bad . However, I did think that my battery was kind of sub-par; this note 7 sucks down quite a bit of juice. I was hoping at the replacements had a better battery or longer-lasting one or something ????.
outamoney said:
I even thought it was less than that and I'd take those odds, I don't think theyre too bad . However, I did think that my battery was kind of sub-par; this note 7 sucks down quite a bit of juice. I was hoping at the replacements had a better battery or longer-lasting one or something ????.
Click to expand...
Click to collapse
to bad it doesnt even matter now lol.. u guys got v1 so the only way you can get a v2 is to try n find one from a third party
elliwigy said:
to bad it doesnt even matter now lol.. u guys got v1 so the only way you can get a v2 is to try n find one from a third party
Click to expand...
Click to collapse
Is v1 any more prone to failure than v2 though? They sourced the battery from a different manufacturer for v2 to try to head off the problem and there were still fire reports. I'm thinking that the failure rate is probably the same as any other phone, only with Samsung trying to be super careful by calling a recall, actually put themselves under a microscope in the media. They even said that they could not replicate the issue in their labs. V2 was just hoping that the battery was the problem. Which it seems that it wasn't.
jal3223 said:
Is v1 any more prone to failure than v2 though? They sourced the battery from a different manufacturer for v2 to try to head off the problem and there were still fire reports. I'm thinking that the failure rate is probably the same as any other phone, only with Samsung trying to be super careful by calling a recall, actually put themselves under a microscope in the media. They even said that they could not replicate the issue in their labs. V2 was just hoping that the battery was the problem. Which it seems that it wasn't.
Click to expand...
Click to collapse
they had a lot more reports with v1.. I think it was 90+ then v2 I think is under 10... not sure if time is the culprit or not however