T-mobile Note 4, CM12, Google Wallet tap-to-pay? - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

Can anyone confirm whether or not this combo is working with Google Tap-to-Pay?
T-mobile Note 4, CM12, Google Wallet
I scoured the Note 4 CM12 thread and didn't find anything definitive.
I'm interested in getting a Note 4 to replace my Note 3, but won't if this doesn't work.
Thanks!
Edit: I found some evidence that it *might* be working, from this thread. Halfway down the page, the discussion starts.
http://forum.xda-developers.com/not...fcial-cm-12-0-t-mobile-note-4-t2964887/page60
Can anyone else report success with it?

Update:
I got a N910T now. I'm running Temasek CM 12.1. I've also installed the latest PA Gapps, and have confirmed that I have the latest Google Play Services.
1. NFC: works. I'm able to use Android beam and transfer to other devices.
2. Google Wallet: app is installed, and successfully sets up Tap-to-Pay with my credit cards.
However, I'm now 0-4 trying to actually use the tap-to-pay. At CVS and Home Depot, it flat out didn't work because those idiots disabled NFC when Apple came out with Apple Pay. However, at this one vending machine and at Staples, when I tried to pay, I got a screen on my phone which said:
"NFC Reader detected. The last tap may not have been successful. Please check with the cashier to see if the transaction went through and if not, try again."
Can anyone provide any insight and/or help as to what is going on here and why tap-to-pay is not working for me?

FYI:
The vending machine I went to when I attempted to use Google Wallet had a pay terminal that looked exactly like this.
https://www.youtube.com/watch?v=6tBAB5ls5vM&hd=1

Here is the exact error message. It's in the attached picture right in this post.
http://forum.xda-developers.com/showpost.php?p=46199890&postcount=1

Update:
Finally, some closure on this issue.
After EXTENSIVE research (probably one of the few times that I used every Google trick in the book), I found this post, which basically described my issue to a T. Needless to say, it emboldened me that it was not any issue with my device, ROM, or configuration, especially being that Google Wallet set up tap to pay perfectly.
http://forum.xda-developers.com/nexus-4/general/google-wallet-fix-t2096956
I set back out on the road, and this time used MasterCard Contactless locator to find an actual store that offered tap-to-pay.
http://www.mastercard.us/cardholder-services/paypass-locator.html
The first place that I hit on that list was a Shoppers Food Warehouse. Unfortunately, that store either didn't have it turned on, or the cashiers were clueless. Probably both, because when I went up to pay with my smartphone, the cashiers looked at me like I was from a different planet. Needless to say, that didn't work. So I left for my second store on the list.
The store was a Panera bread place. I stopped by and got a cinnamon roll. The cashiers assured me that their tap-to-pay was working, and hit something on their end so that the touchpad was waiting for input (either tap or swipe). So I unlocked my phone, unlocked the Google Wallet app, and hovered over the touchpad, which clearly had a Paypass logo on the upper left hand corner of the touchpad. After hovering all over the touchpad (this took about 30+ seconds), the phone finally registered, but it was an error:
"Reader detected. Your last tap may not have been successful. Ask cashier if transaction is complete or tap device again."
Click to expand...
Click to collapse
This time, I flipped the phone around so that the battery side was up (NFC is on the battery) closest to the Paypass logo. After hovering CLOSELY and nearest the vicinity of the Paypass logo on the touchpad for about 5 seconds, the phone finally buzzed, and a W appeared on the screen. The cashier hit something on the register, and what do you know: IT WENT THROUGH! Here was the confirmation!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After all this ridiculous hassle in trying to find out whether or not tap-to-pay works, I can confirm that it actually does. However, during this ordeal, here are a few observations I came up with.
1. Finding a place that does tap-to-pay is much worse off than 1 year ago, which is when I last used it. All the places I went that used to accept it (CVS, Home Depot) don't accept it anymore, just because of the stupid issue with Apple Pay.
2. Not only do you have to find a place that offers it, the cashiers have to know what they are doing, otherwise it will never work.
3. For our Galaxy Note 4s, the NFC is VERY PICKY. I'm guessing it's because the NFC chip is so small, and the fact that it is shoved over to the right side of our big phones doesn't help things at all. This is the reason why I was getting the "last tap not successful" error message so frequently, because it has to be in the right orientation, and it takes more than a few seconds for it to register.
4. The face of the tap-to-pay surface, if the clear glass type, has to be CLEAN and free of obstructions. Part of the reason I was having issues at the Panera bread is because the Paypass surfaces they had are laid flat rather than at an angle, so they were very dirty.
Bottom line: Google Wallet Tap-to-Pay works fine on AOSP/CM12 and the Note 4, if you have Google Wallet set up properly and it says "Read to tap and pay".
I hope this helps anyone else out there who is having these issues.

Related

Screen dies when closed - help requested

I have an HTC Dream/G1 that's having a rather odd issue. When the screen is flipped open, it appears to behave exactly as it should. When the screen is closed however, the display becomes a mess of vertical lines (or sometimes just fades to black) and does not respond.
One need only "sleep" the phone and "wake" it after flipping the screen up to bring it back to normal operation. This only lasts until the phone is again closed. I've included a couple of screen captures to help illustrate the issue. I've searched and searched and found absolutely nothing about this problem anywhere.
I'm currently running Firmware 1.6, CyanogenMod-4.2.7.1 with Cyanogen recovery. Everything was working fine and the phone suffered no trauma prior to this issue presenting itself. It literally happened while the phone was sitting idle on a coffee table. I've tried reflashing the phone (including reverting to Dreaimg.nbh and starting "from scratch") to no avail.
It does not appear to be an issue with the ribbon cable (no amount of flexing the cable or moving the screen has any effect). The display behaves properly throughout its movement up until the exact point at which it switches to "closed" functionality (approximately 80% closed). It appears to be something related to the hardware after it switches to "closed mode". My shot-in-the-dark guess is some form of chip-failure related to the phone's orientation detection as the vertical lines do not change regardless of orientation or touch-input. Again, that is just a guess.
If no one here has any recommendations, I will likely perform exploratory surgery and barring any obvious hardware failures, will likely be forced to replace the phone. If I do manage to resolve the issue (with or without outside help) I will surely assemble a how-to so others may resolve the issue in the future.
Thank you everyone for your help and suggestions, and for existing in the first place. You are the reason technology is fun.
EDIT - As pjcforpres kindly pointed out, I neglected to include the fact that the display failure is present regardless of boot state. It behaves this way upon initial "G1 screen" boot and even in the recovery console. This is appears to be further support for the idea that it is indeed a hardware failure.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does it do this while in recovery/boot loader as well? Is there anyway when closed to get it to work correctly?(I think your answer will be 'no' but just double checking)...
Oh wow, I can't believe I forgot to include that important bit of information. Yes, the phone behaves this way regardless of boot-state. Even with the initial "G1" screen displayed or in recovery mode, closing the screen brings about the display failure. No amount or configuration of screen or button operation seems to bring about the appropriate closed screen behavior. I will edit my original post with this information if I can. Thanks for looking and responding!
I didn't read your post
But my dads g1 did this.
It's a hardware ribbon, not software.
Go get a return or exchange for a new g1 because yours is defective.
That makes me think hardware then... not sure what though? Like you were saying, if there is an open/close switch of sorts that would be my bet. It could be the flex cable as well, and when it close that much it gets pinched, and happens to coincide with the orientation flip. But then it wouldn't take sleep and unsleep to go back right when opened, I would think... so we are back to it probably being the orientation sensor switch being funky like a monkey.
Well, I just tore it completely apart and put it back together to no avail. I made the assumption that the LCD flex cable was not the cause because of the behavior (only happening at a precise position, having to sleep then wake the phone to recover, etc...). It appears, however, that this assumption was incorrect. On Icebergxx's suggestion I decided to give it another look. I wedged a tool in against the cable and with various forceful flexing I can recreate the issue even with the screen fully extended. Luckily it appears the LCD flex cable is available on ebay for $24. Thank you so much for your responses. I'll dig around for a flex cable replacement guide, if a sufficient one does not yet exist, I will take the opportunity to share. Thanks again!
You're so handy its admirable haha good luck buddy glad to have helped.
Happy to hear it is just the flex cable! I was worried with the way it was acting it was something worse, just the whole not coming back to life when opened without sleeping then un-sleeping.

Galaxy S4 Active GPS Fix That Worked For Me

So My GPS randomly stopped working completely one day and so I started doing research on ways to improve it. I literally tried everything from application quick fixes, leaving my phone sitting outside for hours on end, ROM fixes... ext and nothing helped at all. I finally came across this article and, since I had nothing to lose at this point, I gave it a shot. When I finished, i got GPS fix within 2 seconds! This option is not for everyone, I really suggest making sure that the software/application fixes don't help first because taking apart your phone certainly has its risks but if you are like me and nothing has been working, there is hope!
http://www.instructables.com/id/Galaxy-S4-GPS-repair/
Check this article out and give me a shout out if it worked for you too.
Credit to bobyong808 from instructables.com for writing this article.
harrisd23
Keep in mind that the disassembly process is slightly different since we are talking about actives, but I just looked up another article showing how to remove the back of the active and jumped to step 3.
Thanks man, you nailed it! (I just signed up here to show my appreciation for your post, because otherwise I would probably not have come across the solution at all)
I had been somewhat unhappy with my s4a's gps performance since I bought the phone. It usually worked, but often needed 2-3 minutes for the first fix and often lost signal for a few minutes intermittently. Today I opened it up and noticed that the GPS antenna (or what I believe to be the GPS antenna) had apparently never been properly connected to the board. The springs had left no marks on the other side of the contacts (completely blank and spotless), unlike in all the other places where there are connections from the board to the midframe. Then I put a small, folded piece of tinfoil in as suggested in the link you posted and woohoo, only a few seconds now until I get my first fix outside and it can sometimes even get a fix inside my flat (a few meters away from the window at least, with 3 more floors above me), whereas before i had to hold my phone out of the window for that.
Now I am also curious whether or not that will reduce the heavy battery drain of gps logging while hiking in the mountains.
Also thanks for the hint about not following the disassembly instructions directly, since it seems one can easily break the midframe if unaware of the plastic clip above the battery holder. I used these instructions:
h t t p s : / /uuu.ifixit.com/Guide/Disassembling+Samsung+Galaxy+S4+Active/37470
With them and the appropriate tools, even I (theoretical physicist with thumbs on all fingers) found it easy to carry the task out.
(Sorry for the urls, I am not yet allowed to post links here, so replace uuu by www)
Also note that I believe that the two antenna contacts shown on the pictures of your instructables howto are the wrong ones. That should be the 4G antenna, wheras the GPS antenna is on the opposite side as shown here at 3:30:
h t t p s : / /uuu.youtube.com/watch?v=zm4f2XjQLAM
(at least that is where I put my tinfoil, maybe I am wrong and the effect I experience soley stems from me tightening the screws harder than they were before?)
Alright, now excuse me please, I have to catch that Pokemon which apparently spawned in my bathroom
My pleasure, glad I could help!
longpu said:
Thanks man, you nailed it! (I just signed up here to show my appreciation for your post, because otherwise I would probably not have come across the solution at all)
I had been somewhat unhappy with my s4a's gps performance since I bought the phone. It usually worked, but often needed 2-3 minutes for the first fix and often lost signal for a few minutes intermittently. Today I opened it up and noticed that the GPS antenna (or what I believe to be the GPS antenna) had apparently never been properly connected to the board. The springs had left no marks on the other side of the contacts (completely blank and spotless), unlike in all the other places where there are connections from the board to the midframe. Then I put a small, folded piece of tinfoil in as suggested in the link you posted and woohoo, only a few seconds now until I get my first fix outside and it can sometimes even get a fix inside my flat (a few meters away from the window at least, with 3 more floors above me), whereas before i had to hold my phone out of the window for that.
Now I am also curious whether or not that will reduce the heavy battery drain of gps logging while hiking in the mountains.
Also thanks for the hint about not following the disassembly instructions directly, since it seems one can easily break the midframe if unaware of the plastic clip above the battery holder. I used these instructions:
h t t p s : / /uuu.ifixit.com/Guide/Disassembling+Samsung+Galaxy+S4+Active/37470
With them and the appropriate tools, even I (theoretical physicist with thumbs on all fingers) found it easy to carry the task out.
(Sorry for the urls, I am not yet allowed to post links here, so replace uuu by www)
Also note that I believe that the two antenna contacts shown on the pictures of your instructables howto are the wrong ones. That should be the 4G antenna, wheras the GPS antenna is on the opposite side as shown here at 3:30:
h t t p s : / /uuu.youtube.com/watch?v=zm4f2XjQLAM
(at least that is where I put my tinfoil, maybe I am wrong and the effect I experience soley stems from me tightening the screws harder than they were before?)
Alright, now excuse me please, I have to catch that Pokemon which apparently spawned in my bathroom
Click to expand...
Click to collapse
longpu said:
I believe that the two antenna contacts shown on the pictures of your instructables howto are the wrong ones. That should be the 4G antenna, wheras the GPS antenna is on the opposite side as shown here at 3:30:
Click to expand...
Click to collapse
Much obliged for that!
I was able to download a service manual that appears to be an inside document bundle of Samsung. The GPS antenna is named 'ANT200', and it is in fact, on the other side of the PCB (left size, when looking at the PCB from the battery side of the phone, with the rear plastic assembly removed.)
Previously I tried the GPS fix by adding aluminum foils on the two other antenna connectors, which did not fix my GPS. adding the alumium on this single connector made a difference. (I actually also took it back out, to make sure this really helps.) However, still takes a while to get a fix. at least with my phone held outside my apartment.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

N910T won't fix on satellites, even though it can see them.

Hey guys, I'm pulling my hairs out on this problem I am getting with my note 4.
Long story short - I cannot get a GPS fix (to even a single sat) with my N910T.
The longer version:
This thing had a cracked screen - but worked great before that (no GPS problems) and I used it a good year before breaking it. So I bought a N910A (ATT) note 4 to use the screen to fix my trusty note.
I gutted both phones, and put my N910T motherboard in the N910A's frame, with the screen still attached to the frame. I kept the N910A's USB daughterboard (with the charging port) because in the research I did, it seemed basically identical to the one from my broken screen frame, and I knew it would be tricky to get that out and into the new one without busting the new glass or destroying the flex cables.
So after some trouble with the S pen not working initially (the cable didn't press in fully, had to stick paper behind the flex cable and it went in properly) I was able to get the phone up and running again, and all features seemed to work great again.
However - I noticed after a couple days that the GPS was super spotty, so bad it was mostly unusable. I noticed that AGPS was on and it was using wifi and mobile data to help get a fix, so I turned it to GPS only mode. In GPS only mode the phone gets not signal whatsoever, no matter where I am.
I tried the simple fixes many recommend online, one which is to try tightening the screws a bit, and in fact, as this process continued I opened and closed up the phone several times, making sure to carefully but tightly screw all the screws back into place. That didn't help. I also tried making sure the compass calibration was good - and it made no difference. And I even factory reset to make sure there were no issues with installed apps or anything like that.
I got to thinking, perhaps its a issue with the small bendable pins that press from the motherboard into the mid-frame not making good contact, so I tore the phone down a couple more times, slightly bent out - very carefully - all the pins that press into the mid-frame to make them all have a solid contact, and even tried to get any corrosion or debris from the pads on the mid-frame. I even made sure there was contact for those little ones alone the sides of the phone which seem to have something to do with the buttons rather than what I'm dealing with.
Still no luck, so I tried doing a NV rebuild, which I read might solve getting 0 sat fixes, and discovered my phone wouldn't let me into that menu of the service options, so I had to install root and then do it through shortcut master instead. Once I finally was able to get to the menu and run the NV rebuild.... nothing changed.
So I am fresh outta ideas, and I'm thinking that A) that ATT USB daughterboard actually plays a part in GPS somehow and I need to take my TMO one out of the old phone and put it in the new frame and screen.... or B) Something is damaged on my motherboard.... or C) Somebody out there has a better solution
Any ideas, experiences of what worked are all appreciated!
BUMP --------
Still having this issue. Tried opening it up, and realllllly making sure those antenna springs are making contact, and I made sure the contacts on the mid frame are clean.
I tried TopNTP and that made no difference. Here is an image of whats going on when I run GPS Test:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bump?
Losing hope for my old phone here
Anybody happen to know if the daughter board that has the USB charging port plays any role in gps?

Question fingerprint scanner not working after screen replacement

hi guys
so this is my question\story, back in may '21 got my zf8 8/128gb unlocked eu model.
forward 10 months the phone fell on its rear upper corner, cracked the rear glass and the main camera stopped working.
the price of a new camera module is basically the price of another good second hand smartphone. so, i found by chance zf8 16/256gb with broken (but working) front screen for dirt cheap (everything is in order imei serial numbers etc). first thing, swapping cameras between boards is ok, swapping boards makes the fingerprint scanner useless even though in test mode .12345+= the sensor is ok and i dont get any errors or messages from the system. i tried factory resetting, boot unlocking, factory resetting from recovery mode, setting fingerprint in safe mode, with no luck. what is going on? i found nothing useful on the net. it seems like there is some stupid solution that i am missing. what should i try next?
Maybe try setting the fingerprint in a custom rom, like LineageOS? It could work as it is probably something asus put in their ROM to prevent users from swapping things left and right. So if that lock is set in the ROM it could work, if it is firmware locked, whicch I think is the most likely, it most likely won't work. Still worth the try though
Adaoh said:
Maybe try setting the fingerprint in a custom rom, like LineageOS? It could work as it is probably something asus put in their ROM to prevent users from swapping things left and right. So if that lock is set in the ROM it could work, if it is firmware locked, whicch I think is the most likely, it most likely won't work. Still worth the try though
Click to expand...
Click to collapse
i was gonna try this but got cold feet, afraid i will get stuck with no working scanner with the original mother board. i will try rooting as a last resort although i was almost there. if only there was a way to get an engineer code or put the device in a service mode like the onepluses of the world...
Adaoh said:
Maybe try setting the fingerprint in a custom rom, like LineageOS? It could work as it is probably something asus put in their ROM to prevent users from swapping things left and right. So if that lock is set in the ROM it could work, if it is firmware locked, whicch I think is the most likely, it most likely won't work. Still worth the try though
Click to expand...
Click to collapse
i just tried it and.... its not working... swapped the boards and it worked fine on the original screen. lesson learnt
Another loss for right to repair... That sucks, maybe you could try to detach only the fingerprint scanner from the display to keep on the original motherboard
Adaoh said:
Another loss for right to repair... That sucks, maybe you could try to detach only the fingerprint scanner from the display to keep on the original motherboard
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
first, i tried, its nearly impossible to separate the screen from the chassis without pro tools and without breaking it. i dont mind breaking the already broken screen, but it will be risky with the good screen.
second, there is no scanner for sale by asus or any other shop on the internets and by looking at picture above from ebay you can see that the scanner is part of the screen electronic circuit...
i called the service center in my country to ask if its possible for them to swap the screens between my phones, and the answer i got was no. they said that i have to give them about 45 days to check the damage and only then will they give me a quote for the repaire . i dont want to sound like a karen, but i need to speak with a manager. it wouldn’t be fair to talk s**t on asus because the service center is not an asus owned and run operation, its an “authorized“ service center. so i need to hit asus zentalk forum or somethig… lets get this show on the road see whats really going on…
AJ205 said:
i called the service center in my country to ask if its possible for them to swap the screens between my phones, and the answer i got was no. they said that i have to give them about 45 days to check the damage and only then will they give me a quote for the repaire . i dont want to sound like a karen, but i need to speak with a manager. it wouldn’t be fair to talk s**t on asus because the service center is not an asus owned and run operation, its an “authorized“ service center. so i need to hit asus zentalk forum or somethig… lets get this show on the road see whats really going on…
Click to expand...
Click to collapse
Can you update what was the private massage? It's really interesting to see what's going on behind the curtains, if you are not comfortable sharing it here my telegram is @MOSSADAVICH

Touch Screen issue after May Update!

Hey guys,
I am back to the real OG forums of Android after spending a few good years with iOS devices. Ngl, missed this place a lot!
So I have been using a Pixel 4a (5G) for 2-3 weeks now, and everything was perfect until the May security update 2 days ago. Although, previously, there were a couple of touch screen issues observed by many anyway, a friend too who uses the same phone, same variant g025-e and we used to observe extremely **** typing experience while charging our phones, until this update, literally destroyed the whole experience for me specifically, and not my friend.
This update was about 16.9 mb and on the night of 1st of May, I put my phone to update and slept, within hours it was released. The next morning my frustration begins. There is a part of my screen, specifically between the app dock and home screen separator that doesn't work anymore. There is absolutely no damage to the phone, neither have I dropped it or anything. The whole "asd" row on my qwerty keyboard barely works. Tapping the letters on that row a million times might register a touch magically, but you get my point, its just extremely frustrating.
Furious, I immediately took it to Pixel Community (Pixel Community Post here) and I haven't received a reply there yet. I took it to Reddit (Reddit post here), and there isn't any help either.
I have run a couple of tests on my phone testing my screen, and to my surprise multi-touch isn't working either (I can't zoom into photos, can't use maps or anything for that matter) and my phone only detects one finger. Attaching screenshots below where you can see touch break (there is no point of posting multi-touch test here, it can only show its detecting 1 finger, and that also breaks in the area shown below):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As last resort, I have also tried removing my screen protector, playing with the screen-protector mode in the display settings but in vain.
Now I am thinking something definitely went wrong while my phone installed the update, and thinking of a full fresh flash of the Software after unlocking the bootloader. Please suggest what to do. Hoping for positive replies. I am not doubting the hardware because my phone just stopped working right after the update, even though the new update suited my friend's phone just fine.
Hello ,
I have same problème as your but in worst, I have to use USB louse to use my phone....
vince 038 said:
Hello ,
I have same problème as your but in worst, I have to use USB louse to use my phone....
Click to expand...
Click to collapse
Oh damn I'm sorry its that much for you mate. Did it happen after the update or just randomly?
the day I updated the phone, the touch screen started to not answer again on the top and then the problem is repeated gradually on the rest of the screen. I just made a factory rest, the touch screen no longer works, I will change the screen .
Vincent

Categories

Resources