I am having a very weird, and oddly repeating hardware problem with my HTC TP.
My original one started having this problem about 3 months after I bought it. The problem had two aspects - the screen appears as if the LCD material in it has moved or changed format (see image below) - and the touch function of it became problematic, often identifying the press in the wrong location.
I gave it to the vendor during warranty, and after some issues with the lab was offered a new device (it was indeed brand new, battery date indicated that). The new device - after less than a month - started having the exact same problem! (I'm giving it for repair tomorrow)
Is anyone familiar with this problem? Is this just a streak of bad luck? or am I doing anything bad to my devices? As far as I know - I'm not doing anything bad to them - the 2nd one was so short with me it haven't even dropped once. And before that I had a imate KJAM for 2.5 years without such problems.
Ideas?
It looks like too much pressure was applied to the LCD screen.
it is odd though - especially as it occured in such a short time on my new device, and I have not done anything especially bad to it
it definitely has the "feel" of a pressed LCD, but this is during rest. btw - in both times it was just the center area, and both cases a very similar size problem.
the only type of pressure I can think of is when it is in my pocket, but comeon, I am quite positive HTC did not design a device that can not withstand being in a pocket.....
it's a random defect that some screens get
and also a sign of worse things to come I believe
had a friend who bought a new one and it already had
it when it got it he of cause sendt it back
so I just coincidently got two of them ?!
That's quite jinxy
anyway - got today back my first phone, repaired (screen replaced).
Let's hope this doesn't re-appear.
Ofer.
sorry a little off the mark
e
i dont know if anybody has had this or a similar problem but i finally got my phone where i want it. i am running 6.5 on my fuze the only issue i am having is the phone dosent give me any vocal notification when someone is calling me while i am on the phone. i have already made sure that call waiting is set to notify me in the phone services but still dosent beep. if someone calls me it does come through cause if i am looking i can see it just dont hear it. it even alerts me after the fact telling me i have a missed call. just not during
Hi.
I've decided to post this thread here as i don't wherelse to go.
Well known UK grocery and retailer Tesco has launched its very first Android tablet called the Hudl. Specs-wise its pretty descent and above average. I have it for 8 days now and i like it. But i noticed there is one fatal flaw: the touchscreen.
I found the touchscreen to be unresponsive at times on any app or whatever i'm doing) when 1. the tablet has been left on standby for very long hours (say overnight for 8 hours or more) and when the battery life goes below 20% where its at its worse.
Any idea on what could this be or what could be causing it? Would a touchscreen booster app help with at least the sensitivity of the screen?
Please advice. Thank you.
Hi,
There are know faults with the Touchscreen on a batch of hudls.
My 1st one - would happen very intermittantly and half the screen would stop responding - a quick press of the powerbutton and again to switch screen on would fix it - would happen randomly in 3d games and also when using browser/facebook etc
Contact Tesco tech support and they should be able to arrange for replacemnet device and hopefully that will sort it
As i said they are aware of it and have some naff advice on their website
http://ttselectrical.custhelp.com/app/answers/detail/a_id/3539
It's a great device considering the price and take comfort in the fact that there are also screen issues on old and new Nexus 7's
also check this forum out - http://www.modaco.com/forum/747-tesco-hudl/
Stuben32
Hi everyone,
I bought a Oneplus One in past July with enthusiasm.
After few days of use, began the "ghost swipes" issue (as every owner of the One) and multitouch issues (my phone is basically recognizing 1 finger at the same time) preventing any pinch to zoom or notification expand gesture.
But that's not the worst, after few weeks of use, began the most annoying issue I ever had on a device : my touchscreen is going crazy detecting contacts on the touchscreen by itself.
This issue began slowly but is getting worse over time. I noticed that the issue appears only after keeping my phone on my pocket for a while... I need to wait up to 10 mins after taking it out for the problem to disappear.
At first, a simple reboot was temporary the issue but not anymore. It's simple, I only can use my phone 10% of the day... During the remaining 90% it calls numbers, takes photos, deletes messages by itself...
Watch this video, it speaks for itself :
I do not know if anyone else has the same issue or not and I can't determine if it is a software problem, a hardware one or a combination of both...
I opened a support ticket on Oneplus website (but it seems I won't have answer before a few weeks... ) and I don't even know if they will accept doing a swap (OPO support is one of the worst I know).
What's sure is I am really disapointed by this device, whatever its price tag... And I won't recommend it to anyone and I won't give out my invites.
Guys, don't buy this phone and wait for the next Nexus device with which you'll have a high quality device at a decent price...
I let them a little while to find a fix to this situation and if nothing comes, I'll buy another one and use all means at my disposal to be refunded (the French law is quite helpful in the field).
.ant1
There are many users facing this issue. Check around the forums you'll see numerous threads about this issue, you might also find some tips to reduce the issue.
AFAIK this is as of yet not permanent fix for this issue, but since i dont have this issue i havent been following it so i might be wrong. Good luck though.
Google "bacon 55"
Sent from my OnePlus One using Tapatalk VIP
The only solution is to RMA the device. Took me 6 weeks of haggling with One Plus but finally the RMA is in process.
PSA: *This will be crossposted in xda HTC One X and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
Hello everyone! after many headaches, 3 times P907A replace my device, do everything I found on the forums, I've finally been able to solve the problem of blue screen of death.
5 days have passed without any reboot, it is too early to draw definitive conclusions, but at least is a significant advance, previously had reboots 5 or more times a day.
Well, what I did was this:
1- Rooted my device using Towel Root
2-System Tuner Pro installed on my device
3- On the main page of System Tuner in the upper left corner, go to Options, Advanced Settings, then Boot Configuration.
Then in the Edit CPU options, there you will see the processor 1,2 & 3 offline, you just have to put them online.
And that's it. I think there is a bug in the OS, I'm supposed to be work according to the requirements, but it is likely that this will not automatically and only one processor working the number 0, is receiving full workload, for this reason the system is rebooted. They are now working 4 processor simultaneously.
The battery consumption? who gives a damn, when working well your dispositive.
Sorry for my bad English, but I am using San Google translator.
I hope work for you as well as me is working.
Sorry if it is not the appropriate place to write this post, I'm just trying to help.
:laugh: Greetings from Mexico
Still no BSODS?
Issued BSoD
Hi Drew489! !
Unfortunately the problems returned. Not with the same intensity, I mean, once every week or 15 days. So I decided to send my tablet to Samsung warranty.
It was not reliable for me. Samsung replacement motherboard and ready ... the problems are over.
If your gonna do as I do, I advise you to take a photo when this blue screen and send to Samsung.
to that facilitating and Samsung will replace the entire motherboard to just a few components. Sorry but true. Greetings and if you need a picture with blue screen, just tell me and I'll send it
Thank you. I'm on my second one as well. Really annoying but I guess if that's my biggest problem, life is pretty good.