Today I got my phone in. I was on the first set up page and it wouldn't respond to any of my touches. The buttons would glow like I was touching them but it wouldn't type or input. I soft reset it. It worked when I used assist touch. I hard reset it, wiped cache and factory reset. It fixed and I installed all my apps and when I plugged it into the charger it stopped working again. I can open the camera by double pressing the home button to unlock my phone but i can't open anything. It will glow like I'm pressing it but it won't open. I can pull down my notifications bar but none of my toggles or setting icon will work, again, they will glow just not open. I came back to my room and randomly it was working again, after 5 mins it stopped again.
Thank you for your attention.
ATT 64 GB
Galaxy S6 (not edge)
I don't know if this is the cause/solution to your problem, but I know S Voice can cause lag issues. By default, double pressing the home button (when device is unlocked) opens the S Voice. Frankly, it's redundant and pointless, as it's a mediocre attempt at Google Now. Open it, then go into the settings, and disable it. It causes lag because it's waiting to see if you're going to press it again or not.
But if that doesn't fix it, and it's doing that stuff before you've even set it up, I'd tend to think you've got a faulty unit. The capacitive buttons are part of the screen/digitizer, so maybe you've got a bum one.
Related
It says only ipl 2.25.0001 and spl 2.25.0001
I try a hard reset, but when it asks me to confirm by pressing SEND, I press SEND and nothing happens.. press any key and nothing happens, just sits there saying press SEND to confirm...
I tried flashing Cingular/AT&T's rom on to it, it was successful on the screen, but after rebooting, just went back into the 3 color screen...
Does anyone have any suggestions?
Additional info
I just wanted to add, I have searched threads here on xda-dev and other sites, and have found similar issues - normally the other issues have been resolved in one way or another involving a hard reset, which my phone will not complete. When it asks me to press send, the phone freezes at that point and does not accept any key entries (except reset). I would really appreciate any input. I also have a theory-that I may attempt this evening-If you hold the camera button down and reset, it brings up the boot loader screen (if my information is correct)... could my problem be caused by a faulty camera button? Maybe internally the button is remaining closed, which could prevent it from doing anything on a reset outside of the boot screen? Any engineers around that may know this? I am going to attempt (hopefully with low heat) to remove the button this evening... possibly even repair or replace it if the phone works with the button removed...(these thoughts are based on my phone being dropped in the sand at the beach...maybe a grain of sand worked it's way into the camera's button housing and is holding the contact closed)
problem's almost fixed
well thanks for no advice... i desoldered and removed the camera button (button 3). powered it on and the phone works. I reprogrammed the camera to button 5. (i also loaded a new WM6 rom and some other stuff) The last time I opened up the phone, I broke the itsy bitsy super micro tiny lock on the keyboard ribbon cable socket... so now my slide out keyboard doesn't work. I installed a full screen keyboard and set it to the messaging button (button 1) - the messaging button still brings up messaging with just a touch, but a long hold brings up a full screen touch keyboard that works fantastically!!! I am going to dismantle the very tiny micro switch and repair it, then resolder it back on the mainboard to make my camera work like it should again...and find a way to get the keyboard ribbon cable to lock into the socket...then my phone will be as good as new!
umm... thanks???
well congratulations on getting it working again.
tiny switch
I have taken the tiny little switch apart without breaking anything... one tiny grain of sand stuck under the button pressing on the switch plate... now i have to find a way to put the little switch back together... then attempt to solder it back onto the board without over heating nearby components. I have been playing around with Byka's cube... took a bit of tweaking to get it to work well.... not sure if I want to keep it or not... I have been trying to find htc cube, but no luck outside of a rom... which I may consider...but I just spent the past week reinstalling all of the software I use... Would like to just design my own windows for my phone if I had the time... Been working on an ion motor for an electric car...
I would like to thank everyone here at xda-dev. for all the information. Could not have learned so much, so quickly, if it weren't for this site.
oh... and I am using an 8125 (G4) with Faria Crossbow
Have the same problem...
Hi!
I have the same problem (but I don't have much tech know how).
It all started when phone got wet (inc. in battery compartment).
My phone would not soft reset beyond the Bootloader, unless I leave the battery out for a few hours. Then once it loads up, after a short amount of usage 2 things happen: 1) every time I would turn it on (or get a call) it starts in Camera (you didn't report it but you must have had the same experience). 2) the buttons don't work properly.
It finally dawned on me the camera button might be stuck, I set the button to "none", and no more more automatic camera. I still need to free the button altogether as still causing button freezeup and also allow soft resets.
I don't know much about soldering.
Any ideas?
Thanks
Hey, I was just playing with my phone this morning and noticed a strange problem... The top part of my screen, just under the notification bar, does not respond when touched, if an app is running. For example, I cannot hit the location/search/layers button in gmaps, or the search button in market (this is only in portrait mode btw), but on the main screen, it responds just fine. This problem did not exist yesterday either, and I have already tried rebooting, and that did not fix it...
Might want to provide a bit more info if you want help.
I.e. What rom are you using, what kernel, any speedtweaks, etc.
Oops, sorry, it just seemed to fix itself randomly, but I am running CM7 1.2/MR2 radio, no other tweaks, just in case anyone else has the same issue in the future...
NoHesHere said:
Hey, I was just playing with my phone this morning and noticed a strange problem... The top part of my screen, just under the notification bar, does not respond when touched, if an app is running. For example, I cannot hit the location/search/layers button in gmaps, or the search button in market (this is only in portrait mode btw), but on the main screen, it responds just fine. This problem did not exist yesterday either, and I have already tried rebooting, and that did not fix it...
Click to expand...
Click to collapse
Im hoping it was just a fluke for you, but keep an eye on the issue, if it happens more it would sound like you could have a bad digitizer (its what controls the touch screen)
So it happened again today, not sure what set it off, but this time it wasn't just the top part of the screen. Phantom presses would happen, the notification bar would go halfway down and then pop right back up, the 4 buttons on the bottom wouldn't respond... I did a battery pull, and it seems to have fixed it for now, should I be contacting verizon to replace this one? It is a replacement of my original one (which bricked)...
I have just noticed that when selecting apps and doing most actions that require a quick touch, there is about a half second delay. The keyboard works fine except when I press the space bar sometimes. The capacitive buttons on phone react instantly. I can press the app drawers then press any of the capacitive buttons before phone opens drawer. This tells me it's not the screen or my protector.
I didn't notice this until I tried to play flappybird and couldn't even get through the first pipe. I installed the sense 5 update a few days ago. I'm fully stock, no root , nothing.
Anyone else have the same problem? I've tried doing a hard reset/battery pull sim and still same results.
I am unable to wake the phone during a call. As soon as I answer a call, or press the call button my screen turns off. I can not wake it with proximity sensor, double tap or power button. There is literally no way to turn on the screen once a call has started. It was random when it started. I had been using Vanir for a while and then one day it started on my phone, and never left. I have even flashed my OG nandroid stock and the issue was present there after flashing to that.
I have swapped ROMs, AOSP x4, BarRin, Stock, you name it, but to no avail. I have cleared everything off my internal, wiped the internal memory, sideloaded a ROM back from scratch and booted up plain jane... same issue.
I am attaching a link to a logcat incase anybody has any ideas. I'm simply lost with this, and it is a major issue considering every time I make a call I have to be ready to take the case off so that I have faster access to pop the back off and battery pull. This is not a way to live.
PLEASE if someone has any ideas on how/where to go about fixing this, I will be grateful.
Not sure if it matters, but after a call ends, I need to wait about 5 or secs before the power button will be recognized. After it's first press it seems to first power off the screen, as though it is awake the whole time, but black and inoperable. After the screen thinks it's off, the second press turns it back on. I have also tried other dialers too, but it totally seems like an integrated OS/Firmware issue at this point.
Are you by chance running Greenify? I was having some issues when sleeping system apps. What Xposed modules are you currently running?
No battery apps installed whatsoever. No battery saving modes enabled.
Mods- App Settings
DarkTube
GravityBox [KK]
Pandora Patcher
Youtube AdAway
Sorry a bit tired. I just noticed you stated it still happens after you nandroid back to your previous backup. Do you have a screen protector or anything on it?
Try going to Settings/Call and disable the proximity sensor and see if you have the same results
It's not the sensor though b/c it has 0 results with the double tap to wake and also the power hardware button itself. Holding the button, pressing it quickly, tap it multiple times in a row. Additionally, I do not have a screen protector.
OK, here's the situation. sometime last night my phone decided it was going to play a late April fool's joke on me. I had set it down, and the screen timed out as usual. Only when I hit the power button again, it came right back to the home screen instead of the lock screen. Granted I only have it set to swipe, but that's beside the point (I think). I thought it's been a while since I rebooted, maybe that'll help. When it came back up, straight to the home screen again, only this time was way interesting! Not only did the lock screen get skipped, I had no haptic feedback like usual, the home button wasn't working for short press or long press, and with it plugged in and notifications waiting turning the screen off by the power button didn't do anything as far as the notification light.
Now here's the kicker: DOUBLE pressing the home button and bringing up the s-voice actually worked, and after that everything else worked too! Only thing is the problem comes back after every reboot so far. Oh and I've lost the ability to write to the external SD card. I've even tried reauthorizing it, no joy.
Anybody got any ideas about what I could try? If not, at least I hope I made some of you start or end the day with a chuckle and a solid Wtf? ?
My next step is gonna be clearing the dalvik/art from twrp.. Worst case scenario I factory reset and restore my week old backup..
I'm running stock rooted 5.0 with ph1 as my latest update. And if somebody is interested enough to want a logcat from boot to couple minutes in, I'll reboot now, capture the log and post it in a few.
Confused but amused,
I am
The Dude
The log.. I had Logcat Extreme running at info priority, and stopped it after around 8 minutes and just under 22,000 lines. Is that a lot? It seems like a lot. There are a couple power button hits, a menu and a back button press, and also at the end is where I double pressed home and got things back to normal..
Yes, I use xposed, minminguard, unbeloved hosts, and lucky patcher. You'll see them in the log, as well as my Wi-Fi ssid.. I dunno what else might be in there.. Hopefully nothing juicy though. Lol
If there's a way to filter stuff out, or just log the important things let me know and I'll give it another go.