Related
Please post the manufacture date of your phone if you have NOT have the problems
Please post the fix if you have had the problems but did something that remedied it!
I got mine on 5/27. It rebooted spontaneously a couple of times in the first two days. However it has been working flawlessly for several days now. Not sure what happened. Knocking on the wood.
Sent from my LG-P999 using XDA Premium App
I have had my device for 3 weeks and yesterday I had to pull the battery for the first time due to the phone not coming back on. Today I lost signal out of the blue, and couldn't search for networks. Had to reboot the device.
I want to root the device and install one of the custom gingerbread roms but if I need to warranty this thing I want it stock.
Sent from my LG-P999 using XDA Premium App
I'm using gingerbread roms so its hard for me to comment here. But I have not had many issues even with these roms. Mu build date is may 9 iirc
I did however exchange my battery. I have done a couple of battery pulls but mostly due to rom issues and that has been very rare. I don't consider a battery pull to be a problem unless its once a day or more. I have had the device about a week.
G2x with faux AOSP
chubb16 said:
I want to root the device and install one of the custom gingerbread roms but if I need to warranty this thing I want it stock.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
You can revert it back to stock
G2x with faux AOSP
Dated 4/11, stock and unrooted. No reboots, lockups or anything of the sort.
I just used this phone outdoors in direct sunlight. I mean straight on as direct as it can be bright sunshine, and the display was easily visible even just set on auto. I can live with a little light bleed along the edges on a screen that works this well otherwise.
This phone is fast too...
ETA: This is my original and only G2x, no exchanges. I guess I got relatively lucky.
Only two "random" reboots in a little over a month (both occurred shortly after plugging into my laptops USB to charge).
Got mine on 4/20. No reboots ever.
Spyvie said:
Dated 4/11, stock and unrooted. No reboots, lockups or anything of the sort.
I just used this phone outdoors in direct sunlight. I mean straight on as direct as it can be bright sunshine, and the display was easily visible even just set on auto. I can live with a little light bleed along the edges on a screen that works this well otherwise.
This phone is fast too...
ETA: This is my original and only G2x, no exchanges. I guess I got relatively lucky.
Click to expand...
Click to collapse
Bingo. Makes me forget the sensation even exists.
G2x with faux AOSP
<SIGH> My better judgement be damned, I just picked up a 4th G2x - dated May 13th... Hoping I have better luck with it...
No reboots our issues, build date 4/25/11..
Best phone around imo... Except sgs2 maybe.lol
All of the above daily! Most unreliable device I've ever had.
never had this problem at all build date 3/31
I seldom have this problem (3 times so far from the date I purchase).
Stock rooted ROM.
mingkee said:
I seldom have this problem (3 times so far from the date I purchase).
Stock rooted ROM.
Click to expand...
Click to collapse
Actually that's not bad - I've had PCs reboot on their own more often than that, brand new even!
2 days old - 3 reboots
I've had this phone for 3 days, and I've seen it reboot 3 times.... Very concerned about this.
No problems, 4/14/2011
I think mine has rebooted by itself twice in almost a month. It also froze once and I had to do a battery pull.
Aside from that, no problems at all. I'm really happy and count myself lucky that I've never had to replace my unit *knock on wood*
Manufacture date: 4/26/11
Stock ROM, Unrooted
...
It's about time a poll was made about this. I just hope that once and for all this matter gets concentrated in a single thread. I hope this thread gets a sticky until the the G2x issues are resolved or have come to a sufficient conclusion (I'm not so optimistic about T-mo after the Vibrant).
Getting a 4th replacement sometime tomorrow according to T-mo & UPS, just to note. I'll spare the details and update my post when I have more time. =X
On Stock ROM (Rooted) it rebooted every time I used the stock web browser.
On AOSP ROM 1.2.0 (slows.... 40 sec pause/freeze) on the stock browser
I'm still on AOSP for now. Just crashed on me again, but it happens when I web surf on the browser.
Its annoying but hoping this crap gets better. I swear buyer's remorse every time I think about how unstable this phone is.
I already sent my phone to Samsung to repair it under warranty, but I just wanted to see if any one else experienced this problem with Blaze 4G.
Basically, the problem first appeared rarely but progressed within several days to the point that the phone's touchscreen is unresponsive most of the time. It is not present constantly, and that confuses me. It also does not depend on what ROM I am using at the moment, so I guess it must be a hardware problem. The touchscreen can work for 30 minutes to several hours and then become unresponsive for half-day or so. Removing battery or rebooting the phone does not have any effect on this occurence - it still is unresponsive at random.
E107946 said:
I already sent my phone to Samsung to repair it under warranty, but I just wanted to see if any one else experienced this problem with Blaze 4G.
Basically, the problem first appeared rarely but progressed within several days to the point that the phone's touchscreen is unresponsive most of the time. It is not present constantly, and that confuses me. It also does not depend on what ROM I am using at the moment, so I guess it must be a hardware problem. The touchscreen can work for 30 minutes to several hours and then become unresponsive for half-day or so. Removing battery or rebooting the phone does not have any effect on this occurence - it still is unresponsive at random.
Click to expand...
Click to collapse
Haven't heard any issues similar to yours. You probally had a lose connection or worse, but as far as I know the only bug across the boards was the issue not hearing when making/receiving a phone call. From what I seen and others mentioned is the audio bug only occurred on custom ROMs not stock.
---------- Post added at 08:51 PM ---------- Previous post was at 08:45 PM ----------
Where do you live? Maybe its from moisture. I've heard others (not blaze users) report that there phone became unresponsive due to overactive moisture sensors. They go crazy over in the middle east and places with high temps or humidity.
jbats said:
Where do you live? Maybe its from moisture. I've heard others (not blaze users) report that there phone became unresponsive due to overactive moisture sensors. They go crazy over in the middle east and places with high temps or humidity.
Click to expand...
Click to collapse
I live in Bay Area (South Bay). The humidity is quite low, actually. The phone has never been placed in a moist or humid environment. This problem appeared out of the blue. It was not a ROM issue for sure, as it appeared in stock GB, stock ICS and AOKP JB. Heck, the screen was unresponsive even in TWRP
E107946 said:
I live in Bay Area (South Bay). The humidity is quite low, actually. The phone has never been placed in a moist or humid environment. This problem appeared out of the blue. It was not a ROM issue for sure, as it appeared in stock GB, stock ICS and AOKP JB. Heck, the screen was unresponsive even in TWRP
Click to expand...
Click to collapse
Sounds as if it was hardware related pro ally a bad sensor
Well, they updated the status as fixed and shipped. They put the cause as "touchpad failure" and the solution - S/W update. I am kind of sceptical of this repair, but tomorrow I shall see for myself.
Sent from my Prism using xda app-developers app
E107946 said:
Well, they updated the status as fixed and shipped. They put the cause as "touchpad failure" and the solution - S/W update. I am kind of sceptical of this repair, but tomorrow I shall see for myself.
Sent from my Prism using xda app-developers app
Click to expand...
Click to collapse
sounds like they just did a wipe and flashed stock...
Racing19969 said:
sounds like they just did a wipe and flashed stock...
Click to expand...
Click to collapse
Yes, that is what they did apparently. I got phone today with a stock ICS (it had GB when I sent it to them), and it still has the same problem It seems that people who are responsible for repair have no clue about what they are supposed to do.
I will send it again and in the meanwhile, I will get a T-mo Galaxy SII from Walmart. If Blaze gets fixed - great, if not, I will end up with a slightly more performing phone for $300.
Almost a month later, I received my phone second time from Samsung repair department. Well, this time they actually listened to me and replaced the touchscreen. Now, the phone works fine.
In this past month I have tried:
1) T-Mobile Prism (Huawei)
2) T-Mobile Exhibit 4G (Samsung)
3) Family Mobile Galaxy S II (same as T-Mobile but without a SIM card included)
4) T-Mobile Optimus L9 (LG)
I had high hopes for S II and even considered keeping it, but it turned out to be a very mediocre phone (even though it was still better than the AT&T version). Too large and, as a result, uncomfortable; in addition, the GPS was extremely slow to respond and almost any unofficial version of 4.1.2 resulted in an extremely bad sound quality. Noticeably larger screen still had the same resolution as the Blaze 4G.
The most acceptable phone was perhaps LG Optimus L9 - it was thin and lightweight, had high resolution (960x540), good reception and responsive GPS. The only disadvantage was not having NFC. I used it stock and unrooted for the entire 2 weeks, so I do not know how it would function with 4.1.2. If somebody wants a well-functioning smartphone for only $200, I would highly recommend it.
If my Blaze 4G breaks down again, it will probably not have warranty (until March 2013),so my next device would most likely be Nexus 4.
Hi, i did not find any related to my problem, that's why i am opening this thread.
I did a brick on my tf700 at last September and the cheapest solution it was to buy a new board on ebay.
i did the replacement that it was easier than i supposed and it started to work like new, like the first time the system ever boot.
After some days i did again unlock and install cromix and during several weeks it was perfect until yesterday when I detected that it was not good WiFi.
It is like half of intensity compared with htc one. Just works up to 8m from router.
I open it again to verify contacts, board. Everything is normal.
Do anyone know about antenna problem on tf700 (on my last prime it was a lot)? or hardware problem that in a moment reduced the intensity, if it was no WiFi at all i understood as a hardware problem, but half is strange.
Another thing is sound. When i started tf700 no sound, just on phones. After some hours (from night to morning) tablet working, sound appear.... i don't understand.
I tried different firmwares, now i am on cmb 4.3, and it is the same.
Any help?
antonio3073 said:
Hi, i did not find any related to my problem, that's why i am opening this thread.
I did a brick on my tf700 at last September and the cheapest solution it was to buy a new board on ebay.
i did the replacement that it was easier than i supposed and it started to work like new, like the first time the system ever boot.
After some days i did again unlock and install cromix and during several weeks it was perfect until yesterday when I detected that it was not good WiFi.
It is like half of intensity compared with htc one. Just works up to 8m from router.
I open it again to verify contacts, board. Everything is normal.
Do anyone know about antenna problem on tf700 (on my last prime it was a lot)? or hardware problem that in a moment reduced the intensity, if it was no WiFi at all i understood as a hardware problem, but half is strange.
Another thing is sound. When i started tf700 no sound, just on phones. After some hours (from night to morning) tablet working, sound appear.... i don't understand.
I tried different firmwares, now i am on cmb 4.3, and it is the same.
Any help?
Click to expand...
Click to collapse
If you use a different rom and you still have the same problems, then you may have a defect motherboard..
You can try to install a stock rom to verify the issues that you have. If you still have the problems, then you can confirm that you have a bad board.. Good luck..:fingers-crossed:
LetMeKnow said:
If you use a different rom and you still have the same problems, then you may have a defect motherboard..
You can try to install a stock rom to verify the issues that you have. If you still have the problems, then you can confirm that you have a bad board.. Good luck..:fingers-crossed:
Click to expand...
Click to collapse
I already ordered another board from other guy.
My doubt is if the problem is at the ROM level, or kernel level.
Is not possible to take a log to see what Android reports at startup for sound and WiFi?
antonio3073 said:
I already ordered another board from other guy.
My doubt is if the problem is at the ROM level, or kernel level.
Is not possible to take a log to see what Android reports at startup for sound and WiFi?
Click to expand...
Click to collapse
Did you do a clean installation of your rom? If you flashed different kernels, you may have messed up the wifi modules.
Or it is another bug that has been discussed lately in the CROMi-X forum. If you turn wifi off and then on again: Does that change anything?
Some people had bad download speed when waking from sleep, whereas it was fine on a fresh boot or after toggling WiFi on/off.
If that is your problem, try turning off WiFi Optimization in the WiFi settings.
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.
I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.
hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again
What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.
ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.
Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.
hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x
I have the same frustrating issue
Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)
I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.
This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.
I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...
HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!
The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version
My Note 10.1 is extremely slow recently. I mean it can work normally for half an hour and then hang for a minute or not allow me to turn the screen on for 30 or more seconds. Is this because of age? Is the flash inside degraded to a point it slows everything down or maybe clear new ROM will fix this? I am asking because I am not exactly sure I will be able to load a new ROM on it (the recovery is a bit broken, but it will probably be possible through Odin). If it is happening to other old, heavily used Note 10.1's I will just leave it as it is, instead of risking of breaking it completely. So, how are your good old Note 10.1's behaving lately?
One replace battery if you think thats at fault .
Two wipe and install stock rom via Odin .
Nand / flash should not degrade in such a short time .
It took me a while, since I use the tablet very rarely and have gotten used to it's slow downs but I have solved the problem - it was caused by the kernel it had. Changing the kernel to a new, stable one solved the issue. The tablet is still a bit slow, but no longer hangs for 30 seconds like it used too. Thanks everyone for help.
Magnesus said:
My Note 10.1 is extremely slow recently. I mean it can work normally for half an hour and then hang for a minute or not allow me to turn the screen on for 30 or more seconds. Is this because of age? Is the flash inside degraded to a point it slows everything down or maybe clear new ROM will fix this? I am asking because I am not exactly sure I will be able to load a new ROM on it (the recovery is a bit broken, but it will probably be possible through Odin). If it is happening to other old, heavily used Note 10.1's I will just leave it as it is, instead of risking of breaking it completely. So, how are your good old Note 10.1's behaving lately?
Click to expand...
Click to collapse
I experienced the same problem until recently with my GT-n-8010, when it still was under the official 4.4.2 firmware. I also thought about an age problem, but it was definitely not. I've been trying for the last four days the CM13 BETA developped by senior member Lirokoa - everything is explained in this thread : http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375 - and it's just as if I had gotten a brand new device, so it really was a software problem, not a hardware one. I advise you to try it too, you should not regret it