Related
I hate to post a thread like this, but after searching and basically pulling my hair out, I've decided it was time.
Anyway, as title suggests I have an I9000m with the 2.2 UGJL2 *Typo in title, sorry!!*
Heres the problem with the phone...
Its a bell phone, unrooted or modified. Its running 2.2 JL2. When used with an bell SIM it will dial out and receive, receive texts, send them. However it won't receive picture messages, well it receives but just says downloading (and the plan does have it)
It also won't connect to the mobile network. If I manually set APN it does, but then its ability to call out is brutal for some reason. Also I threw my virgin mobile sim in it, set apn and it would go onto the internet no problem, but calling and text suffered big time.
It also seems to lag huge all the time, it'll freeze, you hit the center button and it just takes screen shots.
Its a refurb phone if that helps. Its actually my gfs phone, I picked her up a HTC incredible S... she says if we can fix the old one she kinda wants the samsung back.
Any help would be appreciated.
Mike
Have you tried a factory reset to see if that fixes the problems? That would be the best starting point.
Sent from a telephony device
radeon_x said:
Have you tried a factory reset to see if that fixes the problems? That would be the best starting point.
Click to expand...
Click to collapse
Been done twice. Also have had two new sim cards installed aswell. I figured before I tried rooting it would be best to consult you guys. Is it possible that there's a hardware issue?
Thanks
Mike
Based on your description it doesn't sound like a hardware issue, but no way to know for sure.
I think your next best bet would be to try reflashing JL2 (or KC1 even) using Odin; as long as you can get to download mode via the 3 button combo. If you're still having problems after that then probably it is hardware.
Sent from a telephony device
radeon_x said:
Based on your description it doesn't sound like a hardware issue, but no way to know for sure.
I think your next best bet would be to try reflashing JL2 (or KC1 even) using Odin; as long as you can get to download mode via the 3 button combo. If you're still having problems after that then probably it is hardware.
Click to expand...
Click to collapse
Got er fixed. After I put the phone down and enjoyed a beer for a bit, I went back and basically wiped the phone clean, I think I did it 3 times in a row, using both the 3 button download mode one, and two different ones than can be accessed via the dialer. After doing that I retryed the APN settings again and ALAS it finally worked correctly. Its now connecting to the HSDPA and is also downloading MMS messages like it should. Its also yet to lag again. I'm assuming it was an app that was causing that aswell.
Regardless, the misses is happy, I might keep the Incredible S (currently have the HTC legend, lovely phone, but it does feel under powered compared to the I9000 and the Incredible S)
Sometimes I think a guy has gotta step back and relax for a minute lol!!
Thanks again
Coming over from the Shift forums for a question.
I've tried getting answers over in the Shift forums but no one can seem to help. (also i've done heavy googling)
OK my issue is the lights on the home, menu, back and search buttons are not working. They went out a couple of weeks ago and when I went to sprint they told me it was due to water damage (which is bs). The weird thing is, if I toggle the brightness on my phone then the lights come back on and stay on until I sleep/lock my phone. Also if I open the camera the lights come on. I know the evo and the Shift are similar devices so thought maybe someone over here might have some thoughts on the issue. I appreciate any help.. Don't ream me for being a Shifter
Thanks in advance
Sent from my PG06100 using XDA App
Have tried a new rom?
You could always try going to a sprint store to have it repaired/replaced.
Sent from my Macbook Wheel using Rotatalk
lynyrd65 said:
Have tried a new rom?
You could always try going to a sprint store to have it repaired/replaced.
Sent from my Macbook Wheel using Rotatalk
Click to expand...
Click to collapse
Yeah, I've tried switching several different ROMs, I've ran a RUU back to stock and Still no dice. When I talked to Sprint they told me it was water damage (it's never been in water) and I need a replacement. The only problem with that is all Shift are being shipped with Gingerbread and I'm not willing to lose root.
That really stinks, you might have to live with it for a while.
It sounds like a hardware issue. Have you tried contacting htc?
Sent from my Macbook Wheel using Rotatalk
The only reason I was thinking it's not a hardware issue is because I can manually turn on the light when I toggle the screen brightness.
I may try and talk to HTC and see what they say. It's not a huge deal, I was just hoping someone had seen a similar problem.
I had the same issue earlier today and read that re-calibrating the screen fixes it. It seemed like a random fix but it actually worked for me. Try Settings > Display > G-Sensor calibration
rudolph22 said:
I had the same issue earlier today and read that re-calibrating the screen fixes it. It seemed like a random fix but it actually worked for me. Try Settings > Display > G-Sensor calibration
Click to expand...
Click to collapse
Thanks for the suggestion but still no luck. I may be stuck with no lights until a new root method is found
Sent from my PG06100 using XDA App
I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
UPDATE: 15 Mar 2012:
I added a 100pf capacitor to the interrupt line on the cypress touchkey chip today. Everything works fine now. dmesg shows that I'm no longer getting any false interrupts. I downloaded a 6meg file over 3G and had zero false interrupts. Without the cap there would have been at least a couple of hundred (I use dmesg to check for false interrupts since I have printk statements in my code). I'll keep testing but I think this is it. I'll try to get some pics of the tack on showing where I added the cap. It's some tiny sh-t to work on. I had to do the soldering under a microscope. It was not easy. The cap I put on is a 100pf 50v X7R I bought from Digikey. Digikey part number 445-6856-1-ND. I got a 100 of them for <$6 with shipping.
I'll go back to the driver and remove the software fixes to see if the hardware fix takes care of the problem completely.
The parts are $0.028 each if you buy a hundred. They're less than a penny if you buy thousands. Seems a shame that Samsung couldn't pony up an extra penny to keep this problem from happening in the first place.
For those of you who don't want to crack your phone open, there's still the software (read: duct tape) fix.
Here's a link to the thread showing the hardware mod http://forum.xda-developers.com/showthread.php?p=23725671#post23725671
Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.
sageDieu said:
Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.
Click to expand...
Click to collapse
Yeah, that's why I'd like to try to fix the problem. Not to dismiss the skills of the other people who have tried, but I'm pretty good at finding bugs in hardware.
Well more power to ya, if you fix it then you will make a LOT of people very happy. You should absolutely get in contact with some developers of kernels (jt1134, sixstringsg, Tk-Glitch, sswek2, etc) if you have any ideas or get anything fixed. I'm sure they will be glad to help you out with the issue and use any of your changes in their kernels.
i have a SGS I9000. my problem is phantom presses of menu and back button. tried flashing to stock firmware etr (original was xeu). installed ics. all with no result. FINALLY found that it occurs only when using packet data (edge) we dont have 3g yet. i ve tried disabling packet data and using wi-fi and there is no preblem.
the diagnosis finally comes to this - problem related with packet data and may be (most probably be) related to software bug in the touch button firmware.
It only seems to happen to me at my house, which is in a low signal area. I'm betting it is buried somewhere in the tower switching code, as my phone switches towers constantly at home.
Sent from my SCH-I500
Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.
electric bill said:
Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.
Click to expand...
Click to collapse
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.
Downgrade
I have found that the only thing that works is to downgrade. I am however through uscellular so my phone is the mesmerize. I tried talking to a representative about my problem but all they would say is to upgrade. After multiple tries and different methods I downgraded to DI14 from EH09 and I have not had one problem since. Besides one with random menu flashes but it turned out to be the application Zedge. Hope this helps. If not at least I can say I tried.
ssewk2x said:
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.
Click to expand...
Click to collapse
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk
electric bill said:
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.
ssewk2x said:
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.
Click to expand...
Click to collapse
I've been testing the code for about a day. I added the int test to the interrupt handler just now and I'll test for awhile. I'll prob also put it on my daughters phone since she uses hers about 10x what I do.
Excellent. You're welcome to drop by the glitch kernel thread, btw. I've got some folks testing there with good results so far.
Superclean Rom has screenshot removed. Also Geewiz 2.4.2 has a mod to remove the screenshot, just flash this in recovery:
http://db.tt/xERensX3
It happens when you have a low signal. It's was so annoying but no longer have that issue.
Keep me Fascinated.
It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App
SnrSuave said:
It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.
electric bill said:
I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week
electric bill said:
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.
Click to expand...
Click to collapse
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.
th3b3 said:
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week
Click to expand...
Click to collapse
yeah, I'm on my third phone. there's been some speculation that phones built early (ie when they just started making them) don't have the problem. the data code on mine is 08/05/2011.
dff_jx said:
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.
Click to expand...
Click to collapse
technically if we change the driver code, which is in the kernel then it's been modded...
If you want to run fully stock ROM and see this problem go away then I think you can add a 120pf cap from the interrupt pin on the cypress chip to ground. I haven't tried it yet but I'm going to as soon as I get done testing the s/w fixes.
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.