Related
Just got my new TF700. Major, major touchscreen issues. But these are weird... At first it looked very much like hardware fault but the more I try and use it the more I think its software.
First off, the left hand side not as good as the right hand side. Its first turn on was not usable and its been getting little better as the hours go by. 2 days in now. Done the normal re format, drain battery and also got it warmed right up with a good turn off also. ( Elec Blanket worked great for this controlled warmup ) Nothing has made a direct impact as some others have claimed on the whole Transformer range.
Ive had to take a video of what's happening. I've turned the developer options on to indicate when the digitizer detects the touch and also the indicator when the system responses to this touch. There is clearly a delay in when the system reacts to my touch. But sadly not as clean cut as this as sometimes the digilazer doesn't even sense my touch. Notice the left hand side not as good but still does work sometimes.
http://youtu.be/aslnYafGLf0
To me there is clearly a software issue with this delay. The system response times vary's heaps especially with 10 point touches. But at other moments its not detecting my finger at all... Ive read a lot of TF101 firmware upgades have created touches not to get detected also. Still software going on here ?
My issues with Asus and repair .... I brought this from USA and brought it to New Zealand over night. Big risk yes but it does have the Asus international warranty. 2 days after the invoice date NZ has to say it can be a repair only. I understand NZ doesnt have this yet but this is a huge kick for me as the turn around time is 5 to 8 weeks to repair my 2 day old product. They will import a new screen in but not DOA on receipt date. That hurts Asus but what if its your firmware ? Could it be fixed by the firmware first ? Its nice having a RMA number already as the NZ guys are great but I dont want to be their first TF700 to pull apart as it will never be the same.
I dont feel I can root it to test it some more as they might run away from warranty. Im stuck.... My first Asus product not been a motherboard and not happy with the evidence in front of me guys, please help me out.
Holy crap, that is ridiculous! Dunno what it might be, but I would try PM-ing that vid link to one of the Asus guys on XDA.
Kezzainc said:
Just got my new TF700. Major, major touchscreen issues. But these are weird... At first it looked very much like hardware fault but the more I try and use it the more I think its software.
First off, the left hand side not as good as the right hand side. Its first turn on was not usable and its been getting little better as the hours go by. 2 days in now. Done the normal re format, drain battery and also got it warmed right up with a good turn off also. ( Elec Blanket worked great for this controlled warmup ) Nothing has made a direct impact as some others have claimed on the whole Transformer range.
Ive had to take a video of what's happening. I've turned the developer options on to indicate when the digitizer detects the touch and also the indicator when the system responses to this touch. There is clearly a delay in when the system reacts to my touch. But sadly not as clean cut as this as sometimes the digilazer doesn't even sense my touch. Notice the left hand side not as good but still does work sometimes.
http://youtu.be/aslnYafGLf0
To me there is clearly a software issue with this delay. The system response times vary's heaps especially with 10 point touches. But at other moments its not detecting my finger at all... Ive read a lot of TF101 firmware upgades have created touches not to get detected also. Still software going on here ?
My issues with Asus and repair .... I brought this from USA and brought it to New Zealand over night. Big risk yes but it does have the Asus international warranty. 2 days after the invoice date NZ has to say it can be a repair only. I understand NZ doesnt have this yet but this is a huge kick for me as the turn around time is 5 to 8 weeks to repair my 2 day old product. They will import a new screen in but not DOA on receipt date. That hurts Asus but what if its your firmware ? Could it be fixed by the firmware first ? Its nice having a RMA number already as the NZ guys are great but I dont want to be their first TF700 to pull apart as it will never be the same.
I dont feel I can root it to test it some more as they might run away from warranty. Im stuck.... My first Asus product not been a motherboard and not happy with the evidence in front of me guys, please help me out.
Click to expand...
Click to collapse
The touch indicator has always been laggy. In actual usage, touches register pretty well.
Sent from my FHD porn machine.
jdeoxys said:
The touch indicator has always been laggy. In actual usage, touches register pretty well.
Sent from my FHD porn machine.
Click to expand...
Click to collapse
At times its not laggy at all on this tablet. Cheers,
Kezzainc said:
At times its not laggy at all on this tablet. Cheers,
Click to expand...
Click to collapse
What? I thought it was always laggy. (By touch indicator I mean the line drawing thing you enable in dev settings)
This sounds as nothing a good custom ROM shouldn't be able to fix. (Unlocked bootloader has been released today! )
My HTC One X 4.1.1 never has any lag at all. Asus TF300 has a little but not inconsistent like this. The very edge of the screen is the hardest to even work and pushing to maximise finger area helps. But its the not even seeing touches and a long swipes does not work as it cant stay locked on.... Pinch to zoom very crazy because of this.
But its looking like I am the only one which is saying hardware ?
**** Update : Wow this is a huge epic fail from Asus. My patience is fully coming to an end. Asus have not done a single thing for me on this fault that makes it unusable.
I have a software issue. Its very clear it is now. Lastnight I did another hardreset to try and get this .26 update. For the first time ever it worked, 100% worked on its first boot up. I had a really really happy half hour with it and man it felt good knowing I didnt buy the most expecince tablet dud on the market. But, I did a standby power once and Boom, back to its crap unusable old ways.
So 100% working after reset then one power down resets it to its old ways. When it did work for that 30mins its was 100% working.
Gary and Tien from Asus. These guys have both repied to me. They are not the big Asus people at all, they are just USA Asus. They havnt even done anything for me at all. A huge let down as they make themselves sound like they can help. My unit is a USA unit. They have not asked me to do any tests, offer me a test firmware or even a better video. Or ask what hardware versions I have, simple nothing and taking the piss of what they are offering to this advance community here. Not even an email saying the new update is coming out that may help.
The really bad part about this is its quite clear that the .26 update talks about upgrading the touch FW. Tien emailed me this morning saying they cant even give me a copy of this public released FW for me to fix my problems.
EPIC EPIC FAIL FROM ASUS.
What should I do everyone as im starting to think about getting on a hill a shouting this out to more than just this forum.
( first 'bad' forum post in my life like this )
Kezzainc said:
**** Update : Wow this is a huge epic fail from Asus. My patience is fully coming to an end. Asus have not done a single thing for me on this fault that makes it unusable.
I have a software issue. Its very clear it is now. Lastnight I did another hardreset to try and get this .26 update. For the first time ever it worked, 100% worked on its first boot up. I had a really really happy half hour with it and man it felt good knowing I didnt buy the most expecince tablet dud on the market. But, I did a standby power once and Boom, back to its crap unusable old ways.
So 100% working after reset then one power down resets it to its old ways. When it did work for that 30mins its was 100% working.
Gary and Tien from Asus. These guys have both repied to me. They are not the big Asus people at all, they are just USA Asus. They havnt even done anything for me at all. A huge let down as they make themselves sound like they can help. My unit is a USA unit. They have not asked me to do any tests, offer me a test firmware or even a better video. Or ask what hardware versions I have, simple nothing and taking the piss of what they are offering to this advance community here. Not even an email saying the new update is coming out that may help.
The really bad part about this is its quite clear that the .26 update talks about upgrading the touch FW. Tien emailed me this morning saying they cant even give me a copy of this public released FW for me to fix my problems.
EPIC EPIC FAIL FROM ASUS.
What should I do everyone as im starting to think about getting on a hill a shouting this out to more than just this forum.
( first 'bad' forum post in my life like this )
Click to expand...
Click to collapse
I've downloaded several touch screen test apps and I'm not seeing the issues you're experiencing. I have noticed that some apps perform better than others, but that's about it. I'm thinking that you just got a bad unit.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Dude, just return it for a new one if you still can.
Hey guys, dont want to bring this post up again but think I need to to close it off.
I have a fully working unit now. The .26 software update has fixed it completely.
I am pleased I stuck to my feeling of what it was. Fully credit to XDA again with getting this update as that really was weird it not on Asus's website for the guys who really did need it. I waited for the XDA Asus guys but sadly ended with no reply on my email asking for a copy of the update.
Kezzainc said:
Hey guys, dont want to bring this post up again but think I need to to close it off.
I have a fully working unit now. The .26 software update has fixed it completely.
I am pleased I stuck to my feeling of what it was. Fully credit to XDA again with getting this update as that really was weird it not on Asus's website for the guys who really did need it. I waited for the XDA Asus guys but sadly ended with no reply on my email asking for a copy of the update.
Click to expand...
Click to collapse
Hey, it's always nice to hear that a case actually went over to the "Resolved" bin for a change (and all that on a stock ROM update instead of the custom ROM I had put my stake on, hehe). I'd rather have threads like these revived for messages like these than the dozens of useless threads that are cropping up on XDA re-chewing regurgitated (and partly decomposed) matters.
I'm glad it worked out so well for you, and wish you all the best and a happy forum forum presence and participation in the coming future.
Sent from my ASUS Transformer Pad TF700T
The help that XDA provides is what led me to it in the first place. XDA is teh bestest. I'm thinking about a manual infinity update myself.
There should be a motto for XDA like "XDA: Where the awesome happens!"
Hi All,
I live in Australia and received my TF700 from the US yesterday. I charged it up and then attempted to do the initial configuration where it asks you to choose a language. However the touch screen does not appear to be working – it is not responding anywhere I touch so cannot continue past this screen. Have tried cold booting (power and volume down key) multiple times but no change. I am guessing it is DOA – or is there a chance it is firmware related? I am reluctant to send back to the US as it is going to cost a fair bit...
I am going to borrow a mates keyboard dock and see if I can continue past this screen with that and then hopefully install latest firmware. It is the only thing I can think of...
Does anyone have any suggestions?
Thanks
I've recently noticed another touchscreen "issue". Apparently, the digitizer is either incompatible with the screen resolution or just a software bug. When you scroll really really slowly, you can tell it's jumping by a few pixels at a time. When you fling though, it is completely smooth. This does not affect actual usage whatsoever but I do think its an interesting thing to point out.
le rustle face
Keion said:
I've recently noticed another touchscreen "issue". Apparently, the digitizer is either incompatible with the screen resolution or just a software bug. When you scroll really really slowly, you can tell it's jumping by a few pixels at a time. When you fling though, it is completely smooth. This does not affect actual usage whatsoever but I do think its an interesting thing to point out.
le rustle face
Click to expand...
Click to collapse
I can't reproduce that effect. Can you explain a bit more?
Mines seems to be too sensitive. I put my finger as close as I can put it to the screen and it activates whatever icon is under my finger. Doesn't annoy me only when I get near the bottom right of the screen and the panel pops up.
Sent from my LG-P999 using xda premium
Eroc162 said:
Mines seems to be too sensitive. I put my finger as close as I can put it to the screen and it activates whatever icon is under my finger. Doesn't annoy me only when I get near the bottom right of the screen and the panel pops up.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Good capacitive screen. You are electric, lol.
Hi Guys - thanks for the advice I appreciate it - however I decided to bite the bullet as I was dreading sending this thing back to the US etc... Anyway - so my touch screen was not working at all - so I borrowed a keyboard dock from a friend (lucky I had this option), and could then proceed to configure the device (using the keyboard of course). I then manually downloaded and installed the .26 firmware and hey presto it's a miracle - the touch screen now works perfectly! So it was a risk but I am glad I had a crack anyway. So hopefully no-one has the same issue as me but if so then this might be worth a try.
Thanks again for any feedback.
okantomi said:
I can't reproduce that effect. Can you explain a bit more?
Click to expand...
Click to collapse
1. Open up chrome.
2. Swipe down without lifting finger off.
3. Scrutinize the motions extremely closely while moving your finger as slow as you can.
You should notice multipixel (2 or 3) jumps.
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.
I've read a few threads on the screen Flickering and there doesn't seem to be any resolution .
I'm on my 3rd tablet now (thanks best buy accident damage warranty!) And this one is flickering worse lately than ever. I updated to the latest firmware, yesterday only to boot up to horrible bouts of flickering during the setup screens.
The odd thing is, there seem to be no consistency to it. Some days it's so had I can't even use the thing, other days it doesn't happen at all. I use the tablet every day for notes or PDF viewing. I've used it with no magnetic cover (totally naked) and with the cover.. doesn't seem to change the occurrences.
I've turned overlays on/off force gpu render on/off.. nothing seems to fix it. Sometimes changing the overlay will reduce the flickering other times it doesn't affect it at all.
I hate to say it, but if I can't resolve it, I'm going to be forced to move to the surface 3.
I'm an electrical engineer and I've done as much trouble shooting as I can think to do.. but I've come up empty handed.
Anyone else have these problems? Has anyone found a definitive fix?
I sent mine back 3 times. The first was a reset. Thanks for wasting my time. The second was a motherboard and that didn’t do it. The third time they did a motherboard, digitizer, and usb port. It's finally stable and back to normal. After 5 trips back, the BB warranty triggers a new unit. Check if it triggers a refund.
I get it occasionally, so far I'm able to resolve it by booting into custom recovery (TWRP) and clearing dalvic to allow all apps to rebuild. Sometimes this resolves it for a few days, sometimes a couple of weeks. Its a repeatable "fix" that makes me question if the issue is related to memory or trim or something like that. Kind of reminds me of how with the first generation nexus 7s one would see slow downs after a while and filing storage with fake data then deleting it would improve performance for a while.
I'm definitely not a tender user of the device. I go back and forth between multiple ROM's and kernels on a daily basis testing what is testable, and unfortunately also what is not. Anyway, even though mine was bought as refurbished on eBay, I have never had any issues like the ones you describe. More specifically, I have never had any issues what-so-ever, that was not created due to my own ignorance. To me the device seems indestructible.
Besides, I would hate to be in the place of my device, or I would definitely have turned schizophrenic. Should I feel bad about pushing it through all this?
Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?
ShadowLea said:
Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?
Click to expand...
Click to collapse
P900 wifi. Us version bought at best buy.
Today the tablet has been rock solid, I have literally done nothing between when it was flickering like mad and now.
I wonder if it might be related to some kid of data transfer. either over wifi, or when data is written or read from storage or SD card. I've take then SD card out to eliminate that as the problem.
Mine was P900 from BB
Issue lies with the screen.
This happened with me I sent it back to Samsung, 3 times. They seem to have finally got it right. They replaced the battery and then the display screen. Now it appears to be working I will let you know after a month if it is still good. They also told me that they will not replace the device even though I bought it and the issue was right from the start. Not even 6 months old. When working the device is excellent.
Ah, so now we know for sure the battery is replaceable. That's good news. Maybe someday our batteries will no longer hold a charge and we can replace it. Now for a good video on tear down and what tools to use to do that and where to get a replacement battery. I know it's early for most of us but someday......we will have to replace that battery. I'm one of those that keep my toys (computers/laptops/tablets/phones,) for many years.
Mine is running like new since last service. Getting the BB Geek Squad warranty has paid for itself already. I get 2 years on anything over $500.
Mine is a p900. I purchased from samsung website. Mine has been doing it fresh out of box. So bummed.
Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.
{Diemex} said:
Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.
Click to expand...
Click to collapse
My P900 has just begun flickering exactly as you describe. So I should just be patient and hope it goes away by itself?
I'm flickering again. Turning the screen brighter is what triggers it for me. Returning to stock just to get it back and have it flicker again to hit the magic 5 returns may be what I have to do.
https://youtu.be/CvxbVft69Kg
I just followed this guide. Its been a week now, not had any flickering since I did it.
Manya3084 said:
I just followed this guide. Its been a week now, not had any flickering since I did it.
Click to expand...
Click to collapse
Lifting the motherboard only temporary close the gaps of cracked battery connector. The permanent fix need to do: re solder the battery connector.
Look closely under magnified glass or microscope , you'll see the cracked solders. You can test by pushing the connector slightly, a bad one will move easily or lift off from its solder joints.
This video was removed from the poster after I pointed out his guessing solution. Flickering screen has nothing to do with LCD connector on the motherboard.
Lifting mother board actually you're applying pressure on the battery connector from rear cover.
I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk
bluebirch said:
I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk
Click to expand...
Click to collapse
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.
Beut said:
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.
Click to expand...
Click to collapse
Thanks, missed that other thread. Next time, I'll send them an en explicit request to replace the battery comnector, and refer to those two threads.
Stefan
Tapatalked on some kind of Samsung tablet
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!
Hi. I'm not your typical noob person, I simply haven't had an issue I couldn't find a solution for that required me to come to XDA in a very very long time.
Long story short, I got the Galaxy S8+ 5G tablet brand new from T-Mobile in less than a week.. immediately noticed issues with swiping/glide on both Samsung and Gboard keyboards(Gboard is my STRONG preference for a long time now)
This is brand new out of the box, before a screen protector was added or any apps installed. Still did all the standard trouble shooting - installed update, no dice. Force closed each keyboard, wiped cache and data on each keyboard, tried turning sensitivity off and on and.. no dice. Restarted into boot mode and wiped cache.. most of these things not really something that should apply to a brand new out of the box tablet except update and factory reset - both of which I did, neither of which, nor anything else has helped.
I even added a tempered glass screen protector thinking it's TOO sensitive, and even after that, and again trying to toggle sensitivity setting in the settings.. still just will not swipe.
I type this currently on my Samsung Galaxy S20 FE5G absolutely flawlessly. I can type without looking at the phone at all and type near perfect accuracy with just the occasional need to choose a different word in the suggestion bar.. that is using Gboard "glide". The tablet using Gboard bloating mode is almost an identical match to the size of this keyboard and would make it a nearly *perfect* way of typing just as quickly and accurately on the new tablet.. I understand that some of the accuracy comes from use of the keyboard and locally stored into but.. the tablet types gibberish half the time. If I push FAR harder than I should have to while gliding, a few words may work.
Called T-Mobile Saturday, had a warranty replacement sent(God I didn't want a refurbished device) because the only natural conclusion I could come up with is the digitizer has an issue, maybe during shipping.. etc. I don't know..
Got it last night, booted it up, this time I made them include a "invisible shield glass fusion+" screen protector which went on flawlessly and should have no effect on typing at all.. and it's got the same EXACT issue. Maybe a HAIR better, but still completely unusable in my opinion.
I want this for work, the tablet and this phone and a 4k Chromecast, with features like dex, second screen, etc.. there's just about no scenario I can think of where this WON'T be beneficial in any support scenario..
T-Mobile already wants to give me the tablet for free, I've had so many issues with them for so long they switched me to a "business select" package only certain managers can apply, and I get unlimited everything for each device at $25 per device.. forever. No matter how many.
No discounts for auto pay or mass numbers or.. just a flat number that beats the company I was going to switch to when I unlocked my phone 12 days ago.
But I've been a customer customer for 8 years and a T-MOBILE customer since before the first iPhone smartphone was released.. even a few years before that when the best phone you could get had a slide out keyboard and basic touch functions..
So they are supposed to be calling me within the hour, I expected to see numerous threads or posts about this issue, because clearly it isn't ME..
I find some other links I've tried fixes from like:
Strange Gboard bug temporarily breaks glide typing, here's how to fix it [Update]
Over the past 24 hours or so, users have started noting a strange issue with Google’s Gboard keyboard on Android,...
9to5google.com
And see this post of Galaxy phones describing exactly the same issue
https://www.reddit.com/r/GalaxyS22/comments/u8y4cz
and describing it happening with a specific update..
I've got 2 devices, the first is brand new and factory reset as of last night, has a glass screen protector, and the refurbished one in front of me with the same issue.. I've restored data so I can continue using it, but tried all the SAME fixes and nothing.. and T-Mobile is calling in 45 minutes or so.
Obviously I'd like to keep the brand new device rather than the refurbished one- but IS THERE A FIX, or anything I can do with them on the phone.. I got a Bluetooth keyboard and mouse and aftermarket case.. I can type using the keyboard obviously, but I typically can type WAY faster with Gboard the way I am on my phone right now..
I tried doing searches on XDA but it seems like their search functionality has changed for the worse in the years I haven't been here.. that or I can't find the advanced search and forum search I KNOW I used to use daily.. not in the app, the mobile page, or desktop version.
And because it isn't worth it's own post I'll ask one more question -originally I had them send me a Galaxy tab 7 FE 5G becauseb the S20 I'm using still works so well and it was only $100 if I added the line.. and it's just an oversized worse version of my phone.(but don't recall it having this issue now that I think about it) Which is why I'm here now with this tablet..
The problem created by that is I can't tell the pen for that tablet and the new one apart, and here https://m.gsmarena.com/compare.php3?idPhone1=11342&idPhone2=10922# it is showing the new one has less latency, Bluetooth, etc..
Part of the reason they are calling this morning is they were like "oh, just keep the Galaxy tab 7 for free, on us"
Me: "I don't want that oversized garbage, that's why I'm ordering the 8+!"
T-Mobile guy: "Oh, well then return the 7 and you can have the 8+ on us!"
Then I've been trying to get a shipping label for 11 days now, only to find out that he never put in the system that I wanted to return the device and he already voided out the equipment plan for it.. meaning I'm stuck with a tablet I don't even want- and can't tell which s-pen is supposed to be the better pen!
I mean, the chance I'll lose one is so high I won't return the pen and keep it as a backup.. but.. I'd still like to know how to tell the difference, when I attach either one it connects with no issue and I can't find anywhere that shows the pen type connected!
I'm so sorry this is so long, but like I said.. I normally do not need to come here and get my issues resolved myself, it's what I do for work.. and I haven't needed to root/rom a device in so long that I just kinda.. stopped.
(But I'm not going to lie, I got super excited when I came here and there seems to be the option to root/ROM and that it seems like a well supported device in that way! I've kind of dreaded KNOX because previously I never could.. but I'll look into that later once I fix my CURRENT issues..!)
Best I can do as far as pic of S-Pens https://photos.app.goo.gl/pfqKMiiG49L21gx7A