For 6 months, my Nexus 5 have been the best thing that happened to my life. But after the 4.4.3 update around Jun13, this display issue appears. Display keeps shifting upward in a continuous manner. For example, the keyboard is now in the middle, and the top part is below, it keeps flickering and moving. So I thought it may be a software bug since it coincided with the update (and no, I did not drop it). I tried all (factory reset, turn auto settings off, Developer options settings) to no avail. I contacted Google support and after a few emails, they told me to contact Japan support team. I don't know anyone from Japan. (Actually I do, but when he called them, the Google person couldn't speak English and my friend can't speak sufficient Japanese). (Note: A friend of another friend bought this phone from Google Store Japan)
So I thought, wth, let's open the back, maybe there're loose connections, like the battery or something. But now the adhesive is tampered with, a small dent in the case (due to the very strong adhesive) and the back does not pop completely back. One corner is a bit loose, so there's no fooling them that I have opened it.
I updated to 4.4.4 and new issue, the display is gone, just backlight. I managed to fix this eventually. Now I'm back to 4.4.2, and the display is still shifting. During bootup, Google logo is stable, but the next animation is shifting. Bootloader is stable, but sometimes it moves up a grid after I press a button. So I assume that the display moves when the system processes something.
So my conclusion now is that this is probably hardware/GPU issue. Or is it? My warranty is as good as void already since I can't communicate with Japanese, and since I opened the back, it really is void already. I have 2 immediate plans of attack: 1) flash a custom rom, if software issue; 2) buy a triwing screwdriver to check the back, if loose hardware.
Any thoughts?
You have answered your questions already m8.. If I were you, I would find someone who can speak Japanese and tell them to contact Google support and act as a interpreter.. I'm sure you will find someone in your workplace.
Since you've opened up the back and damaged the device to a point where it doesn't pop back, the warranty is gone most probably. But I would still contact Google first and then go-ahead with tampering the hardware.
- Sent from an IceCold Hammerhead!
tsuwariwarirap said:
For 6 months, my Nexus 5 have been the best thing that happened to my life. But after the 4.4.3 update around Jun13, this display issue appears. Display keeps shifting upward in a continuous manner. For example, the keyboard is now in the middle, and the top part is below, it keeps flickering and moving. So I thought it may be a software bug since it coincided with the update (and no, I did not drop it). I tried all (factory reset, turn auto settings off, Developer options settings) to no avail. I contacted Google support and after a few emails, they told me to contact Japan support team. I don't know anyone from Japan. (Actually I do, but when he called them, the Google person couldn't speak English and my friend can't speak sufficient Japanese). (Note: A friend of another friend bought this phone from Google Store Japan)
So I thought, wth, let's open the back, maybe there're loose connections, like the battery or something. But now the adhesive is tampered with, a small dent in the case (due to the very strong adhesive) and the back does not pop completely back. One corner is a bit loose, so there's no fooling them that I have opened it.
I updated to 4.4.4 and new issue, the display is gone, just backlight. I managed to fix this eventually. Now I'm back to 4.4.2, and the display is still shifting. During bootup, Google logo is stable, but the next animation is shifting. Bootloader is stable, but sometimes it moves up a grid after I press a button. So I assume that the display moves when the system processes something.
So my conclusion now is that this is probably hardware/GPU issue. Or is it? My warranty is as good as void already since I can't communicate with Japanese, and since I opened the back, it really is void already. I have 2 immediate plans of attack: 1) flash a custom rom, if software issue; 2) buy a triwing screwdriver to check the back, if loose hardware.
Any thoughts?
Click to expand...
Click to collapse
It is incredible, i have exactly the same problem and i did the same as tsuwariwarirap did. So if it is the same issue could be a kind of software problem? Or maybe all the nexus5 hardware will have issues with 4.4.3 or 4.4.4 ?
shevaperu said:
It is incredible, i have exactly the same problem and i did the same as tsuwariwarirap did. So if it is the same issue could be a kind of software problem? Or maybe all the nexus5 hardware will have issues with 4.4.3 or 4.4.4 ?
Click to expand...
Click to collapse
It's a hardware issue. A software update can't cause the flex cable or the display to go bad like that. If you have flashed back to fully stock and still have these issues, your only option is to replace the damaged parts.
Hi, do you mean this kind of issue
How did you solve this?!
Related
Greetings all. I'm not convinced my problem is specifically related to the One S, and I certainly haven't got anywhere near rooting yet, but you Guys are expert at nosing round in the bowels of this phone & the OS, and I'm getting totally flummoxed as to where I've gone wrong.
I've owned this phone since June and it was originally locked to O2, was unlocked and used on Giffgaff, an O2 offshoot - probably irrelevant. One of the apps I particularly wanted to use was Google Sky Map, duly installed and run successfully for a day or so. Other apps installed, as one does, but when I came back to Sky Map, the app was frozen, as were seemingly all compass function apps.
Various uninstalls & reinstalls later, a system reset and a factory reset and this function still was inactive. Returned to HTC for fixing. No better - all worked OK for a short while then stopped. Returned again and this time internals were swapped ,but now the microphone wouldn't work. Third return and an unlocked sim-free handset was returned.
As soon as I loaded my profile from Google, initially it worked, but later most of the sensors again seemed to fail. I've tried the full factory reboot then logged in with a totally new Gmail account, but no change. Phone Tester app shows only readings from proximity and light sensors - no gyroscope,compass, mag. field or accelerometer. Accelerometer did show one set of readings this morning, but nothing since. Lookout AV has always been installed. Incidentally, almost exactly the same profile worked perfectly well on my previous phone, a Wildfire S.
Should I shoot myself or the phone? I admit I'm not any sort of phone expert, but I don't think I'm that dense as to so consistently screw this thing up.
Any ideas people please, in (moderately) simple terminology?
Ok maybe you could shoot google, maybe its a fault by them.
If I helped in anyway please hit thanks
Thank you for the oh-so-helpful response.
Just in case one of the myriad readers of this thread should have just a quiver of interest ................. I believe I've found the answer.
It's always been difficult to pinpoint the problem, and certainly HTC haven't twigged what's happening, as before I sent the phone back to them I TOOK THE FLIP CASE OFF!
That's why it would work for a short while after return, until I replaced the case. I can only guess there's something like Carbon Black in the plastic back shell, and that's what's been interfering with the sensors.
It may also be relevant to the big Home Button problem, with the screen flipping between Home & Helicopter views. Has anyone investigated whether there could be sufficient signal degradation to trigger this problem caused by the use of a case?
Sweetness and light to all.
I spoke to an HTC rep, and he said they would not give an unbranded handset back. If that's the case, I want my phone unbranded. I'll take it to them and hopefully get an unbranded one.
Well good for your HTC rep. They can't go giving out unbranded sets like that. What is the World coming to?
Notwithstanding - the previous clutter of O2 apps was pleasantly noticeable by its absence as was the O2 splash screen.
What a lucky little customer I am and it's only taken 4 months to sort out.
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
Hi Guys,
Just got my phone replaced because the screen was sometimes unresponsive when layed flat on a surface.
Now I got a problem with the rear facing camera. When I open the camera app the auto focus doesn't always work. As result I get very blurry photo's
I made a short video to show you guys the problem:
Can you guys tell me if this could be a hardware or software problem. I performed a hard reset and reboot but the problem still occurs from time to time.
Ps. I didnt drop my phone and I removed the plastic of the camera lens and led flash, so that cant be the problem.
Since the problem cant be solved with a hard reset, I guess it's a hardware problem. So I contacted my carrier and I will get a new phone. Hopefully this time a phone without problems/bugs.
I will keep you guys updated.
I have that problem too, shaking the phone unlock the focus. It seems to be hardware problem, using the manual focus in pro mode change nothing, only way to fix it for me is wait like 30 to 60s or shake the phone.
I try to get a replacement but obviously, it works perfectly the two times they check :silly:
I had the same problem in the store like you. When I wanted to show the problem to a shop assistant, the camera worked perfectly :silly:
But (thankfully) they believed me and one of these days I will get a replacement because they didnt had any in stock to give me right away.
Maybe you can show them the video on YouTube and tell them that there are more people with the same problem?
I think I will keep it like this for now, and I will ask for a replacement just before the warranty end, so I will have a new phone ^^ I'm used to it now, if it bug, I just shake it and all is fine.
Yeah that would be great. Only I'm afraid that here in the Netherlands the phone will be send to get repaired instead of getting replaced. Only in the first two months i can get it replaced, at least that is what the T-mobile shop assistant said to me.
One of my friend has the same issue. She figured out that she "just" needs to hit the phone on its front top left corner (not hard) and it suddenly works.
yeah thnx, that works most of the time. Still I would bring it back to get it repaired or get a replacement. Yesterday for example, I wanted to take a picture of a fast bike passing through but I ended up with a blurry picture. That shouldnt had happened and I dont want it to happen again.
Still thanks for the tip.
i have the same problem.. the camera take too long to focus or does not focus at all, i need to shake the phone.. i called tmobile and they will give me a replacement.
root the phone then add this to build.prop to fix it
ro.ril.sensor.sleep.control=0
aloric said:
root the phone then add this to build.prop to fix it
ro.ril.sensor.sleep.control=0
Click to expand...
Click to collapse
Where do I add that line in the build prop?
I have almost the same problem. Only facing this issue on third party camera apps like Snapchat or Facebook messenger, besides that it works fine. No problems on stock (yet).
Similar Issue
I went hiking one day back at the end of May, and inadvertently left my S6 in the car, which of course, got very hot during the day. After getting back to my car almost 9 hours later, my phone was almost too hot to even touch. I promptly removed the slim case that was on it, and held it up to the A/C (not ice cold, was trying to avoid condensation).
Ever since then, when going into 3rd party apps (most notably Snapchat, and sometimes even the stock camera app) the auto-focus motor seems to get stuck.
The easiest fix for me so far seems to be shaking my phone up and down rapidly 1-2 times. Upon doing this, I can hear a faint *click* and the focus works as normal.
This is very obnoxious as I've missed many shots due to having to do this (and sometimes it doesn't always work). Hard reset has done nothing, so I'm assuming maybe something in the camera got damaged due to excessive heat.
***Edit: After talking to my insurance provider (Squaretrade), they told me that this was still under manufacturer warranty, and to go through my carrier. After taking the phone to Verizon, it was discovered that the water-damage indicator had the slightest bit of red/pink on it, deeming it "water damaged". I later checked this myself at home and there definitely was some red on the strip.
Contacted Squaretrade again, informing them of the new situation, and they advised they would send a refund for the phone (since it was from eBay).
Hopefully the new phone will not have this issue!
Hi guys ..
I was suffering from the same problem .
The problem is the focus of the camera in galaxy s6 just like the Video, .
The solution is:
delete this line : ro.ril.sensor.sleep.control = 0
from ( build.prop )
you can find it in : system/build.prop
Using this program with root access : (Root Browser)
*i can not insert the link because i am a new user here .
after you click on build.prop chose (RB Text Editor)
note : (i am arabic man so my english is not good )
Anyone managed to fix this issue with the method above?
Yup..This is still common.. How does one fix without root?
Solution not working for me I did non fount the line ro.ril.sensor.sleep.control = 0 in my build.prop.. i tried to add the line but nothing changed problem still remains
I had the same camera issue. I took my phone to Samsung and they replaced the camera module.
Now it works perfectly.
Saludos ?
I can't go to Samsung, i have knox counter altered..no warranty for me
yourlifeupdated said:
I can't go to Samsung, i have knox counter altered..no warranty for me
Click to expand...
Click to collapse
So what? I have that to, went to an official Samsung Store and they (tried) to fix it
Having the problem myself btw, but if i aim the sensor to the ground en go back up its fixed, not so big problem. Only when selling the phone i want it fixed so its worth more...
Hi Everyone. I've read a lot of posts here and elsewhere on this issue, but have been unable to solve it, and Sony phone support suggested I post a question. So here goes...
I have a Z3 (D6653) on Android 6.0.1. A month out of contract with my telcom (Telstra), I started having trouble pulling down the notification drawer. Originally it was just slow, then only possible from the home screen and within a day altogether impossible.
I reset the device to factory, but this didn't help.
I used the native diagnostic tool to test the touchscreen and it showed a narrow, very uniform unresponsive band at the top of the screen. About 2-3mm. The uniformity of the band, which suggested to me (right or wrong) that it may be a software issue, not a hardware issue.
So I tried to flash a custom ROM, but although I was able to unlock the bootloader, I was unable to access recovery mode. (I've flashed custom ROMs before, but it's not something I've ever found trouble-free.) After about 8 hours trying all the usual methods, and all the unusual ones, I gave up and started looking at recovery apps.
But recovery apps all require root, so I decided to pursue that course. But without recovery, I couldn't root the device the normal way, so I decided to try Kingroot. After a few false starts, it eventually said it had successfully rooted the device, and Root Checker said it had too. But I was still unable to install a custom recovery with an app. Which left me with nowhere to go.
And now Root Checker is saying the device is NOT properly rooted, Kingroot basically spins, and I haven't been able to unroot with SU or anything else I've tried (not many attempts).
And now at least one app (Pokemon Go) won't work because it thinks the device is rooted.
So I'm now using a floating app to pull down the notification drawer, and I've got all the apps that most often give me notifications sitting directly on my home screen, rather than in folders. I know none of this is the end of the world, but it interrupts my workflow and, thus, my overall productivity. Also plays havoc with my OCD!
Sony support said it's no longer covered by warranty because I rooted it, and although they can probably fix it, it'll take up to a month, and will cost somewhere between $50-$250. I could buy a replacement phone for not much more!
Any ideas on where to go from here? Should I just get a local mobile repair shop to replace the touchscreen? Or is my suspicion right and it's more likely to be the OS? And if the OS, how do I get to recovery?
Thanks heaps, in advance.
Cheers
Glenn
divinewrite said:
I used the native diagnostic tool to test the touchscreen and it showed a narrow, very uniform unresponsive band at the top of the screen. About 2-3mm. The uniformity of the band, which suggested to me (right or wrong) that it may be a software issue, not a hardware issue.
Click to expand...
Click to collapse
I just about guarantee you that it's a hardware problem, this has happened to me twice on 2 different display panels, through some research this problem happens only on sony phones.
Normally cracking the screen will trigger this problem (Even the smallest of cracks will) but in some cases it will do it on it's own. I think (correct me if I am wrong) sony purposely made this happen possibly to make money on the unfortunate ones who have cracked the screen and caused the digitiser to become slightly unresponsive or not work at all (Thus needed repair and most will go to sony to do so).
I ended up blowing up the phone (Not kidding, I put it in a old microwave and the battery exploded) because it was a pain to run AOSP/CM roms on there and it was gonna cost me quite a bit to fix again so I said fk it and happily destroyed it with a couple of mates (I don't suggest doing this I was just sharing my experience/feelings with this problem {and more}).
I'd suggest selling it (If possible) and getting a new phone, even a phone with the same specs will be better due to sony being... well... sony.
I'm quite happy with my new Moto G4 Plus that runs considerably better than my old Z3 (And the battery lasts longer too ).
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