Related
Looking for some advice/help. I got my wife the Evo Shift a couple of weeks ago. Her phone has not been rooted and other than a few added apps the phone is completely stock. The phone reboots on her 4 and 5 times a day. She does not have any kind of task killer installed so that's not it. She plays Angry Birds a lot and uses Pandora quite a bit. I have also installed Sound Manager for her. Other than that I can't think of anything that would be helpful for trouble shooting. I have searched here and through Google and have not seen any info of others having this problem. I am not sure if I should root the thing or return it to best buy. I have the Evo and previously the Hero and am no stranger to rooting or custom ROMs. Just really did not see the need to root it since my wife has no idea about any of that. Any help or advice will be appreciated.
Thanks.
root and install nfinitefx's or mik's rom; you'll have less trouble than if it was stock.
danaff37 said:
root and install nfinitefx's or mik's rom; you'll have less trouble than if it was stock.
Click to expand...
Click to collapse
That's what I was thinking. I am a little worried its a hardware problem though. I guess I could always flash back to stock and return it if that doesn't fix it.
hell return it ya got nothing to lose but a headache
Did you try a factory reset?
Sent from my PG06100 using XDA App
JKILO said:
Did you try a factory reset?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Not yet. I did get some more info from my wife though. It only happens when she is at work. And she says she get some sort of "radio error". I'm starting to think it might have something to do with the building she is in. She had my hero for a couple months before I got her the shift and had no problems. It had CM 6.1 running though.
hauntedchild said:
Not yet. I did get some more info from my wife though. It only happens when she is at work. And she says she get some sort of "radio error". I'm starting to think it might have something to do with the building she is in. She had my hero for a couple months before I got her the shift and had no problems. It had CM 6.1 running though.
Click to expand...
Click to collapse
im running mine stock and rooted and dont have any problems with reboots. sounds like a app is probably screwing something up
i had a similar problem with one of the streaming media apps i used to use a month or so ago i cant remember the name but for some reason if i lost signal it would crash the phone and need to be rebooted
i took it off and installed tuneinradio and it worked better anyways
My shift was rebooting itself 3 to 4 times a day, I just rooted it and it seemed to stop rebooting itself for a day. Now its starting to reboot itself again, but not as often.
I am almost convinced its a hardware problem. Sounds too rare to be anything else. Maybe bad memory or something.
Sent from my PC36100 using Tapatalk
I had a freezing issue with my phone which people suggested possible due to pandora and bluetooth. Perhaps you have the same issue?
Anyway, try to find "bluetooth for automotive" settings for pandora and turn it off.
I wouldn't recommend rooting your phone if you think its broken. You might just end up breaking it further and render your warranty void.
If you can't fix it, get sprint to replace it.
i dont need a signature
This may be resolved by now, but I got my shift previously used. When I first activated it, I was getting some radio errors and I could not make calls or send sms messages, but the email worked fine. I contacted Sprint customer service via chat from the website and they did something from their end to fix it. I had to turn off my phone and she said now wait till I tell you to turn it back on. I waited 5 minutes and when I turned it back on, everything was fine. So I would take it in or contact Sprint and see what they say. As for not sure if you wanna root it for her, I would definitely recommened it, she doesn't have to take advantage of all the advanced tweak that some use but it will just make the phone a lot smoother and easier to use. IMHO.
Sent from my PG06100 using XDA App
Michael61182 said:
This may be resolved by now, but I got my shift previously used. When I first activated it, I was getting some radio errors and I could not make calls or send sms messages, but the email worked fine. I contacted Sprint customer service via chat from the website and they did something from their end to fix it. I had to turn off my phone and she said now wait till I tell you to turn it back on. I waited 5 minutes and when I turned it back on, everything was fine. So I would take it in or contact Sprint and see what they say. As for not sure if you wanna root it for her, I would definitely recommened it, she doesn't have to take advantage of all the advanced tweak that some use but it will just make the phone a lot smoother and easier to use. IMHO.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Thanks for the input. I think I'm going to go ahead and root it. After keeping an eye on the situation its seems its only happening when she is at work. I can't imagine it will fix it but I think its worth a shot.
I think I fixed mine. I tried to use navigation and it kept force closing, that was strange because I've used it before with no problems. I googled around and found some info that if you had another text to speak engine in your phone then uninstalled it without setting it back to pico as default it would cause nav to FC, which is what I had done. So I set it back and checked "Always use my settings" in the Voice section of settings, nav started working and the reboot issue went away for the past 7 days.
I don't really know crap about phones and most tech stuff for that matter (heck 99% of what is said in these forums goes over my head) but I think why this fixed it is either nav or some app was trying to use pico or something and when it couldn't the phone would get an error and reboot itself. I may be wrong (probably am) but maybe she deleted something or changed a setting some app needs and that is causing her problem. Hope this helps in someway or at least gives you another direction to start checking.
As of this morning (at least), the earpiece in my phone is no longer functioning. I can't call people and hear them without using the Speakerphone or a Headset. I've initiated contact with Windows Phone and Samsung support, but I was hoping maybe someone here has run into the issue and found a fix, as I imagine the "fix" from MS and Samsung is going to be send the phone in for repairs.
I'm currently running 7392, so I might try rolling back, but the one person I saw on another forum with this issue didn't get it fixed this way.
Also, I'm using a microSD card.
To make things even better, the first boot after a battery pull brings up the red screen.
If you saw the red screen, you probably did the 16-bit reg edit fix. What other reg edits or diagnostics stuff have you done?
Sent from my SGH-i917 using XDA Windows Phone 7 App
I had the exact thing happen to me minus the red screen issue. What i did was use the diagnosis app type in *#0289# and test all the speakers, make sure they are all on too. Then restart your phone and it should correct the issue.
other info. I am running samsung focus stock 7390 on att
also- if you do not have the diagnosis app it is the sticky thread in the top of the general section.
munkeyphyst said:
If you saw the red screen, you probably did the 16-bit reg edit fix. What other reg edits or diagnostics stuff have you done?
Sent from my SGH-i917 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Yeah, I forgot that the Advanced Configuration Tool auto-sets it.
Unfortunately, I didn't see siralex's suggestion until after I already got the phone replaced by AT&T. I appreciate the intention, guys.
Confirmed
FishFaceMcGee said:
Yeah, I forgot that the Advanced Configuration Tool auto-sets it.
Unfortunately, I didn't see siralex's suggestion until after I already got the phone replaced by AT&T. I appreciate the intention, guys.
Click to expand...
Click to collapse
I can also confirm. I know this is an old thread but for others who may have developed occasional random reboots and the red screen of death when rebooting, I was having the same issues for a while. What I also found was that I had checked the "fix 32 bit" checkbox in Advanced Configuration when I installed it. I unchecked this box and saw these symptoms disappear immediately and not return. It got to the point I could not reboot without getting the red screen and it took several battery pulls to be able to turn the phone back on.
Hi,
in the last days with my S3 on every call I had which went for more than 1 minute the other person suddenly couldn't hear me anymore. Sometimes it happened after a minute, sometimes after 3 minutes, but in the last 4 calls it happened every time!
Reception came back after some seconds and from then on it was really bad, the other person had hard problems understanding me.
I searched around and found this thread of GNex owners having the same problem:
http://androidforums.com/samsung-galaxy-nexus/472451-vzw-other-person-cant-hear-me.html
Then I found it in the Issues DB too
http://code.google.com/p/android/issues/detail?id=24019
Do you guys know more? it is really bad, since this is my business phone so nearly every call is an important one and it really bugs me out.
Anyone having same problems?
I hope someone can help me out.
Yes I have the exact problem. It's driving me nuts and I've tried different roms and kernels.
Sent from my GT-I9300
Have you tried to DISable the noise canceling feature?
No but I will try it and report back.
By the way I'm on stock LF6 4.0.4 in Germany (with o2 as my carrier. Unbranded. )
Is the noise canceletion buggy?
Sent from my GT-I9300 using xda app-developers app
I've read that some kernels cause issues like this.
Also, in UK, in Birmingham on Orange, I have been having issues like this, and it usually occurs when the Signal Switches over from Orange to T-Mobile, mid call, and once onto T-Mobile signal, the call breaks up or goes quiet.
Maybe an issue switching from 2G to 3G or back mid call also?
BobFL said:
Have you tried to DISable the noise canceling feature?
Click to expand...
Click to collapse
Will try also. The only reason I haven't got rid of this phone is it mostly happens on o2 calls, I am on giffgaff which is run by o2, The op is o2! Hmmm
Sent from my GT-I9300 using xda app-developers app
just yesterday I again had the issue....and my noice cancelling was off...so this is not causing it....
I'm bumping this in hope someone has a cure.
The new rom LFB is not yet published for Germany but for UK. Perhaps it makes a difference? Can somebody in UK with LFB who previously had the issue please check?
Same problem, no solution
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
the-0ne said:
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Which ROM are you using right now?
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Try this for a fix
goto settings
sound
Toggle on then off or off then on the screen lock sounds then try again :good:
the-0ne said:
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Hey,
just so you know. I am on CM9 and I have kind of the same issue. Sometimes audio is unidirectional, both ways actually, unable to recreate it so far. What always seems to work is my bluetooth headset. Switiching between the two of them makes me lose audio entirely. I have tried many things, even rebooting the phone Sometimes it helps, sometimes it doesn't. I'm guessing it has something to do with BT.
I am NOT facing the issue with losing audio in the middle of the call when the display goes to sleep. The display goes to sleep because of the ligth sensor, btw. - not because the system is idling The display is not needed once the phone realizes it's attached to your ear (lights off).
It's driving me nuts
BUT: CM9 is amazing so far. It's fast, it's open, everything works just fine. Except for the phone as a phone of course
change modem
Oomahey said:
Which ROM are you using right now?
Click to expand...
Click to collapse
Using Stock right now. OTA updates till Jun 26th.
badaeng said:
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Click to expand...
Click to collapse
Mine's currently DDLF3
winwiz said:
Toggle on then off or off then off the screen lock sounds then try again
Click to expand...
Click to collapse
I've just tried this, will report back. How do you think lock sounds affect the mic, though?
avetny said:
change modem
Click to expand...
Click to collapse
Does CM9 come with an integrated modem switcher? I don't like messing around with "packages" too much. The more you mod everything, the less stuff has got to do with each other and it is more likely to run into trouble, because as a developer you can't really consider every side effect
So if this is actually about the modem (which I doubt, because the connection is just fine, it's just the audio output and input that is kind of broken) - what modem would I use with CM9? Can I just flash a random one over the current one?
Appreciate the advice.
Andreas
I notice that as soon as I take the phone away from my ear and the screen lights up I can again be heard... Wonder if there's a problem with the light off sensor affecting the mics too... It ALWAYS goes away when I remove the phone from my ear and the light sensor allows the backlight to come on again...
Might be a crazy thought but the evidence does seem to support this. I haven't turned off the light sensor in settings yet, if I even can, but was going to try next call...
I updated to BLG8 and I will see tomorrow if it happens again. Today I already had one call which lasted 11 minutes without interruptions. I will report as soon as I got more calls to test.
I had the same prob...
I just reflashed the official firmware frm the service centre.
Sent from my GT-I9300 using xda app-developers app
Same problem here. Tried several roms, kernels and modems. Only one working for me is Checkrom v3 with xxlbf... but here also after a while some calls it reappears... I reflash modem and I am set for the next couple calls... then again
Ps: i am from Romania on Vodafone
Sent from my GT-I9300 using xda premium
I'm the OP and I now didnt had the problem for 2 months with the last stock ICS build.
It seems to be resolved.
I'm now on JB since today (XXDLIH) and will report if it comes back.
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
GHII said:
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
Click to expand...
Click to collapse
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
tiguy99 said:
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
Click to expand...
Click to collapse
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
I'm having the same issue with knock on not working. i've wiped a few times and have flashed diferent roms but it wont turn the phone back on. i'm also having this strange issue where i cant pull the notification bar down.
EDIT: I figured it out. did you install TWRP Recovery? i did and mine was messed up. i flashed back to stock and re-rooted and everything works again. I'm not sure if TWRP is the reason since im on a t-mobile G2 but reflashing to stock definitely worked. also i think you have to do a reset after flashing rom because the changes wont take effect unless you do
GHII said:
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
Click to expand...
Click to collapse
Wow that's a relief, I'm having the same pull down issue too.. Even scrolling here is a dead spot on the screen if I'm scrolling a page or list as I get in that area it "slows". I thought my digitizer was going bad. I found my knock on works but I have to do it extremely slow... Tap... Pause 1-2...tap.
Edit yes to twrp.
Sent from my VS980 4G using xda app-developers app
well i re-rooted and it doesnt work anymore. i deleted stuff so i need to see if its something that is being removed that causes it to not work
I just flashed the stock rom back..shows unrooted again, and it is still doing the same thing. Im still under my 30 days, Im going to return it, hope for the Nexus 5 on verizon by the weekend and if not I guess buy a new G2.
mine still says rooted so i'm kinda screwed right now
Same issue
Same thing with my T Mo G2. Using Nova launcher. Knock on worked flawlessly since new, about 2 months,use Nova gesture for knock off. Suddenly knock on stopped working. Too bad, because I like the feature, got used to using it. Did a restore and wipe using TWRP, kept root access, but still no knock on. Next I'll try going back to stock ROM, but I'd rather go an easier route. Has anyone successfully restored knock on?
Hi i have a dead spot somewhere app in the screen and when i pull down the notification bar it doesnt goind down.Also i tryed to draw with quick memo and i can see that it is a dead spot somewhere near the top of the screen
Does anyone has the probleme and have you fixed it
The only solution is returning the phone
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
rastigo said:
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
Click to expand...
Click to collapse
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
ankurcshah said:
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
Click to expand...
Click to collapse
I read the following posts on some other forum...so essentially its a hardware issue....try stock jb rom kdz, then factory reset and reboot. If this helps solve the problem you are lucky. If not, try getting your phone replaced with 802 model. That is practically most stable with a lot of devlopment and tons of ROMS stable and working.
I will still keep looking for a solution and let you know consulting a few senior xda devs I know... sorry man, it hurts to see a fellow indian in distress.....:crying:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
That's odd, I have not seen much on this... if running stock
Quote:
Originally Posted by Burkettacb View Post
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Or againg, a ROM you may be using.
More detail would be helpful
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
Good luck with that if the phone is a D800. I took my G2 to the local AT&T store just a couple of hours ago with the same "no knock on" bug. But the sales person (who had bad breath) told me that because there was another way to get the phone to function (the back button), they won't even look at it. The fact that the knock off/on feature was a MAJOR selling point when the phone was released is apparently irrelevant.
He has a ls980 so it might not be the same for him. He can ask for a replacement
Sent from my LG-D802 using XDA Premium 4 mobile app
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Andrew_han said:
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Click to expand...
Click to collapse
Did you try the "Hidden Menu" "Touch firmware update" option? I had this issue and it got fixed with it.
try 3845#*modelnumber# eg: 3845#*800# change model number 800 with your phones model number, then tap on "Settings" and scroll down to "Update Touch Firmware"
I have a few more suggestions to make it work, let me know how it goes.
Mine are not lighting up and not working. I have done various resets and things would be back to normal, but that has stopped now. Have made enquiries and people are saying it's the Google app and you have to disable it then enable, but that doesn't work either. Has anyone else had this issue? Factory resets were advised in other threads but did not work. I'm getting so many bugs on this phone that it's starting to piss me off
Have you tried initializing in smart switch. Or using odin to flash the latest firmware?
qwewqa said:
Have you tried initializing in smart switch. Or using odin to flash the latest firmware?
Click to expand...
Click to collapse
I''ll give that a try as that seems to be the only option left apart from returning it.
Gave it a try x 2 and it initially appears to work. Then installed some apps and it reverted back. Tried again, and tried setting up as a new phone, same thing. This phone has to be the most disappointing smartphone I have ever had. Permanent bugs, poor sound. Should have waited for the HTC 10.
In Accessibility Settings check if "One touch mode" is enabled. Disable it.
themissionimpossible said:
In Accessibility Settings check if "One touch mode" is enabled. Disable it.
Click to expand...
Click to collapse
Don't have one touch mode anywhere . This phone is really beginning to piss me off. Surely a replacement can't have as many bugs as the one I have. Samsung Internet hardly ever works, the settings I save never save and now this. i'm thinking Samsung rushed this out.
Maybe it's called "Single touch mode" or something similar, I'm translating from Italian...
themissionimpossible said:
Maybe it's called "Single touch mode" or something similar, I'm translating from Italian...
Click to expand...
Click to collapse
Thanks for your help but I cannot find anything relevant on the phone or by Google.
mightywhites29111971 said:
Thanks for your help but I cannot find anything relevant on the phone or by Google.
Click to expand...
Click to collapse
Have you tried the app called galaxy button lights? It might fix the problem.
Heres a link: https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights
Also check to see if you have powersaving enabled. When enabled the recent and back keys do not illuminate.
amar95353 said:
Have you tried the app called galaxy button lights? It might fix the problem.
Heres a link: https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights
Also check to see if you have powersaving enabled. When enabled the recent and back keys do not illuminate.
Click to expand...
Click to collapse
Thanks, have just tried it, doesn't work or do anything I'm afraid
mightywhites29111971 said:
Thanks, have just tried it, doesn't work or do anything I'm afraid
Click to expand...
Click to collapse
I think your only option is to get a replacement then. Hope you get a working one becuase this really is a great phone.
So people say but I have had nothing but problems with it. The sound quality is poor, it never saves my settings and I had to pay £200 to replace the screen whilst out jogging. I didn't drop it, it was in my arm strap for the entire 2 mile jog back from the gym. I'd love to swap it for a HTC 10 as I had the M7 and M8 and they were great phones and I didn't have any issues with them.
mightywhites29111971 said:
So people say but I have had nothing but problems with it. The sound quality is poor, it never saves my settings and I had to pay £200 to replace the screen whilst out jogging. I didn't drop it, it was in my arm strap for the entire 2 mile jog back from the gym. I'd love to swap it for a HTC 10 as I had the M7 and M8 and they were great phones and I didn't have any issues with them.
Click to expand...
Click to collapse
You must have just got a faulty one. I have had mine since it was released here in the uk and have not had a single problem with it other than the occasional reboot but thats acceptable and is just in the nature of Android. I would try a replacement but if you prefer you could sell it and put what ever you get towards a htc 10.
mightywhites29111971 said:
Mine are not lighting up and not working. I have done various resets and things would be back to normal, but that has stopped now. Have made enquiries and people are saying it's the Google app and you have to disable it then enable, but that doesn't work either. Has anyone else had this issue? Factory resets were advised in other threads but did not work. I'm getting so many bugs on this phone that it's starting to piss me off
Click to expand...
Click to collapse
Is powersave mode on?
I've taken it to Samsung on Oxford St, London. After waiting 90 mins a member of staff tried the buttons and then said they will have to send it away for repair and it will take 7-8 days. Then instead of posting it back to me I have to go back to Oxford St and presumably have to wait the same time to get it back. Shambolic customer service.