I assume it is since it happens for my X10 as well as my girlfriends.
1) While texting it seems to freeze and have a constant vibration, then if your fingers kept texting it would eventually type all those keys or the last key multiple times.
2) Run out of memory. I use ATK and I notice after a day it starts off at something around 136mb of free memory then later in the day it will say "7 apps killed, 119mb remaining" and it has gone down to the 80's before. Where is this memory being used?
3) I seem to pocket dial/text a lot even though I lock the screen every time...
4) When on the phone it hangs up a lot from my cheek lol Is there a way to fix this other than bringing up the dialpad and hearing the keys being hit
Also might as well put this here. Is 'rooting' your phone the same as jailbreaking an iPhone?
C3LL0PHANE said:
2) Run out of memory. I use ATK and I notice after a day it starts off at something around 136mb of free memory then later in the day it will say "7 apps killed, 119mb remaining" and it has gone down to the 80's before. Where is this memory being used?
Click to expand...
Click to collapse
Basic stuff for an android phone. High memory usage is nothing to worry about, it's actually almost the opposite, more the merrier.
Hmm I think I've experienced most of those things. They're odd occurances. But be glad they're software issues, because software can be changed/fixed!
As for rooting vs jailbreaking an iphone... the thing is, since iPhone is locked down so much, jailbreaking an iPhone can make a big difference than a stock iPhone. Rooted android allows access to hidden system files, so can allow for more tweaking, but an unrooted Android phone already does so much, as opposed to an unjailbroken iPhone. Rooted android can by far do way more than a jailbroken iPhone. And even in some ways, an unrooted Android phone can do more than a jailbroken iPhone as well.
PS: can you share the numbers of some of you girlfriends? maybe I can help them out with their technical issues
C3LL0PHANE said:
I assume it is since it happens for my X10 as well as my girlfriends.
1) While texting it seems to freeze and have a constant vibration, then if your fingers kept texting it would eventually type all those keys or the last key multiple times.
2) Run out of memory. I use ATK and I notice after a day it starts off at something around 136mb of free memory then later in the day it will say "7 apps killed, 119mb remaining" and it has gone down to the 80's before. Where is this memory being used?
3) I seem to pocket dial/text a lot even though I lock the screen every time...
4) When on the phone it hangs up a lot from my cheek lol Is there a way to fix this other than bringing up the dialpad and hearing the keys being hit
Also might as well put this here. Is 'rooting' your phone the same as jailbreaking an iPhone?
Click to expand...
Click to collapse
1) I've noticed this. The pattern I notice is that this only happens when you're receiving text and typing. Since in the options for the keyboard you can enable vibration when u type I believe this is the problem. I haven't tested it but the way the phone seems to respond, it seems to be so. It seems to be able to only output one vibration feedback at a time. So in effect it delays those linked to your typing until the vibration for receiving text has ended. I could be wrong though.
2) It is most probably being used by background running processes. Typically you only really close a process by pushing the back button until it closes. If you continually open new tasks after pushing the center button you're essentially putting the current program in the background.
3)What you can do is enable a simple swipe pattern lock to help this, but even so you run the risk of locking your phone if you "guess" the pattern lock too many times. So I would recommend you buying a case for it if you don't have one. I have not had any problem like this and I use a case.
4)It sounds like your proximity sensor isn't working or isn't being properly activated by your cheek. What you can do is go to a mirror and call someone, while speaking to them shift the phone a little bit at a time until you see the screen black. This indicates the proximity sensor has detected your face being close to the phone. While you are at it you can also slide the phone a bit to get peak volume with your phone. From what I can see the in-call speaker is very directional.
EDIT: Yea you can consider rooting to be the android equivalent to jail breaking. Considering you're asking that I am guessing you have not rooted your phone yet. If you don't have the latest firmware it might be a good idea since it fixes some little oddities on the x10 as well as offering battery and speed improvements.
There's an easier way to test the proximity sensor:
While in lockscreen, press: Menu Back Back Menu Back Menu Menu Back
This opens the service menu. Go to Service Tests-Proximity Switch.
Now just move a finger over the sensor to test. It also gives you a sound so you can also try holding it to your cheek!
Hope that helps!
@beno1 cooooolll thanks man.
Sent from my X10a using XDA App
So I went into the testing part and checked the proximity switch and it says it is off. That's not what I want now is it? I couldn't figure out how to get it on.
As for pressing the Home button instead of Back.. wouldn't Advanced Task Killer close those applications anyways?
Put your finger over the proximity sensor and it will go from off to on.. then take it off and it will be off..
Tri3Dent said:
Put your finger over the proximity sensor and it will go from off to on.. then take it off and it will be off..
Click to expand...
Click to collapse
I tried that and it beeps, but goes back to off
C3LL0PHANE said:
I tried that and it beeps, but goes back to off
Click to expand...
Click to collapse
That's what it should do! It will only go to on when it is covered then as soon as you uncover it then it swiches back to off.
This is as it should be in the service test. It is working.
Related
Anyone have experience with this? If i type words, press up/down, or pretty much do anything on the keyboard, from time to time the backlight will just turn off.
I've tried messing with pretty much all the backlight settings with no effect.. Anyone know of a fix for this?
SH4YD33 said:
Anyone have experience with this? If i type words, press up/down, or pretty much do anything on the keyboard, from time to time the backlight will just turn off.
I've tried messing with pretty much all the backlight settings with no effect.. Anyone know of a fix for this?
Click to expand...
Click to collapse
Can't think of anything other than a loose internal connector. If you are more or less continuously typing with no long gaps then the light should not go off - even if it does then as soon as you type a letter it should come back on.
I would not try opening up or anything, before doing a hard reset - just to rule out a software issue. If you have lots installed then make a full backup first saves much time re-installing everything.
Mike
I've had the same problem.
different roms do it.
I'm sure it's a bug in the design of the keyboard circuit, or a software bug.
happens mainly when I type fast.
I have the same problem, Did you notice when you slide the phone open the screen rotates but the light takes a few seconds to turn on? http://forum.xda-developers.com/showthread.php?t=314974
always happens when i start typing but then comes right back on... kinda annoying but does not really slow things down.
i've noticed this happening on certain roms, either when i've just flipped the keyboard out or start typing an email etc too fast.
agentp said:
i've noticed this happening on certain roms, either when i've just flipped the keyboard out or start typing an email etc too fast.
Click to expand...
Click to collapse
Its happened on every WM6 rom that i've used.. didnt even have the original cingular rom on the phone long enough to see if it happened in WM5.. Not sure but it can be annoying when im trying to send quick texts.. etc
Guess there is no fix..
just got it
I've just got my 8525 monday, the 2nd, and i've noticed that as well as the hang after waking it up from sleep mode. I believe the keybrd issue is caused by the rom, since i only realized it does that after it sleep mode or i've been searching webpages for a while.
does anyone know of any good rom upgrades for a noobie?
this is annoying usually i can stop it if i turn the backlight time out off (which i normally have set on 30 second timeout)
yea i have the same issue if i am typing fast and it only happened once i started using wm6, it flickers off then back on seemingly randomly
Hello, greeting from Poland,
I have found out that same problem few days ago (Hermes=VarioII, WM5) alghougt I'm using Hermes few months. I think that I have found something interesting to be checked:
When you use hardware keyboard in Hermes, an input method is still set to the last used value.
I have notified that when I have input method set to 'Remote Keyboard' (a part of TranCreative software) there are no blacklight blackouts. Recently I was on holidays and set input method to standard 'Keyboard' and this is when this all begin.
Can any one confirm that?
If this is true - we know at least that this is software bug...
Kind regards,
MA
I have the same problem but it only happens at really high speed but it is really annoying and slows you down.
Yup, I have noticed this issue as well.
SAME HERE!
Kills my productivity, and need to type fast fast fast. Type fast, light goes off for a few secs. Sux.
same here...dont really care it comes right back on.
My screen backlight goes off and won't come back on
I'm not sure if I'm experiencing the same problem... My screen backlight turns off and won't come back on no matter what I do. I tried clicking, scrolling up and down, opening and closing the phone, turning it off and on. Nothing. Black screen. I tried to go into the Backlight Settings panel but couldn't find it. I have to reset it or shut it down for the screen to work. Then the panel is there again.
Last time it happened when I unplugged the usb port. FWIW, I have the 8525 and the latest ROM (2.15 I think.)
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
LPChris said:
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
Click to expand...
Click to collapse
I've seen similar issue with the screen staying awake, thought it's just the phone. Also not sure if it's related sometimes I'll click on a button for example, but it will almost not recognize the spot i'm clicking on and click something else on the screen.
These are the same problems I've been seeing on my phone. I imagine it is due to the multitouch hack, but I haven't gotten the motivation to downgrade my phone back to 1.31.
Do you have anything installed like power manager or locale? One of those progams may be turning on wifi.
Dharkaron said:
Do you have anything installed like power manager or locale? One of those progams may be turning on wifi.
Click to expand...
Click to collapse
Nope, I had installed Power Manager once a while back and didn't like how it worked so I uninstalled it. Don't have Locale installed either. I ran the task manager to see what was running and there was nothing that I could tell that would turn the wifi on.
The touch issues are rather widespread amongst 1.41 users. However, don't know what's up with ur wifi. I have a strange issue with my wifi as well though. Whenever I boot up my phone and wifi was enabled when it turned it off. I get 2 not responding errors. Everytime. Its like clockwork. With 3g? Never. It took me about 20 wipes and 10 or so hours to finally figure it out. Hopefully all these problems will be fixed with rc33
I have also noticed that Applications don't check for new updates anymore. even when I go to "My Downloads", It used to show "free" next to any application that has an update or has been uninstalled. Now it shows "Installed" next to all the applications but when I go to the application by category, It shows up as "Free" meaning that there is a new version.
the case in simple points:
1. when I open the Application..... It doesn't detect the update.
2. when I go to "My Downloads" in the market, It doesn't show "Free" next to any application that has an update.
But if I go to the application by category, It shows "Free".
LPChris said:
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
Click to expand...
Click to collapse
i havnt had a problem with it staying on, i noticed that my phone was dimming to quickly. I know theres probably an adjustment somwhere (i think at least) but i havnt had any problems what so ever with it.
Very strange. I haven't had either problem (wifi or touchscreen). I have noticed that my battery drains more quickly than it used to, but I have been blaming this on the DroidSans autorotate feature always flipping the screen everytime I move the phone (I mess with the phone an awful lot).
Droidsan
I can not get auto rotate on JF RC-33. Does anyone have this problem???
another issue with with this version was that all my ringtones were changed for my contacts and stuff
pretty wierd.
i don't have any problems mentioned ATM.
JF RC30 to RC33
stonefurry said:
I can not get auto rotate on JF RC-33. Does anyone have this problem???
Click to expand...
Click to collapse
DroidSans Tweaks checks the version. At the moment it's not going to recognize RC33 as a valid version. Wait for it to be updated.
danguyf said:
DroidSans Tweaks checks the version. At the moment it's not going to recognize RC33 as a valid version. Wait for it to be updated.
Click to expand...
Click to collapse
What he said... But don't forget to enable auto rotate in your browser though. You don't need droidsans for that.
I have noticed that my x2a goes out of standby when I am putting it into its case (on my belt). This causes the display to turn on again -- wasting battery time and possibly starting programs.
Has anyone else noticed this? I find that if I hold the phone for an additional 3 seconds befor I place it into the case, going out of standby does not appear to happen ... but that could be just operator error ... and I have tried to avoid hitting any of the buttons when inserting the phone, but the whole thing could be operator error ... or, like I think, that the phone is sensing a position change and jumping out of standby ...
Is there a fix for this?
I thought I'm the only one experiencing that problem.. The thing is, my phone is just on the table and in standby mode and then for some reason it just opens... Very weird..
Sometimes it happens to me too. i don't know why it happens.
Razzino said:
Sometimes it happens to me too. i don't know why it happens.
Click to expand...
Click to collapse
Just a far shot:
Are you guys by any chance using the OneBridge syncronisation software?
I had this problem but it disappeared when my company switched to Activesynch/WMA for Exchange syncronisation.
i noticed my phone was doing this to, so i set it down and watch it for a while and noticed the screen will turn on when it is updating my weather or email, so this may happen when ever it automatically connects (due to some email, weather, ect.) you can try turning off data connection, and see if that changes anything. good luck
yummy-fun said:
i noticed my phone was doing this to, so i set it down and watch it for a while and noticed the screen will turn on when it is updating my weather or email, so this may happen when ever it automatically connects (due to some email, weather, ect.) you can try turning off data connection, and see if that changes anything. good luck
Click to expand...
Click to collapse
mine was off all along... so I guess it doesn't update anything when this happens...
sorry that didn't work, i'm just thinking out loud now, but my phone has recently stopped turning the screen on by itself. uhm things i've downloaded recently was the SDfix.cab and the htcSDK.cab but both of those wouldn't effect it. uhmmm. is there possibly something running in the background? the only other thing i can think of is lock your phone so you won't push button while its in your pocket, and wait for an update (which an update is unlikely to come out). sorry i couldn't help
yummy-fun said:
sorry that didn't work, i'm just thinking out loud now, but my phone has recently stopped turning the screen on by itself. uhm things i've downloaded recently was the SDfix.cab and the htcSDK.cab but both of those wouldn't effect it. uhmmm. is there possibly something running in the background? the only other thing i can think of is lock your phone so you won't push button while its in your pocket, and wait for an update (which an update is unlikely to come out). sorry i couldn't help
Click to expand...
Click to collapse
It's okay dude, I did what you said.. I locked my phone whenever I have to put it in standby mode, and great... It doesn't turn on by itself.. so I'm guessing that I pushed some buttons while the phone is in my pocket...
cheers mate!
It's the magnet!
I know the question was asked a while ago, but noone has posted this as a possible reason.
There is a magnetic sensor for opening the keyboard in the top left corner of the device. When you move your phone near a magnet (most phone cases' covers are held by magnets) it will detect opening the keyboard and go out of standby.
matt69 said:
I know the question was asked a while ago, but noone has posted this as a possible reason.
There is a magnetic sensor for opening the keyboard in the top left corner of the device. When you move your phone near a magnet (most phone cases' covers are held by magnets) it will detect opening the keyboard and go out of standby.
Click to expand...
Click to collapse
I just tried that, and it does some out of standby when I pull it out of the case ... I was wondering why that happened -- sometimes, and not others -- and that answers the issue of pulling it out of the case ...
Thanks for that explaination ...
But there are other times when it goes out by itself ... but I have it is the case most of the time now, and not on the charger ... so it is not really an issue for me anymore, but it is another mistery solved ...
Yup, my X2 does the same annoying thing.
I agree, best way is to lock the screen.
I noticed that the screen part of the phone is kinda wiggly...
1) Sometimes it takes more than a minute to fix gps.
2) Sometimes while pressing home button and hold it opens recent apps and freeze a while.
3) Sometimes Facebook app goes crazy and can't control it.
4) Sometimes it's calling and need to unlock to answer the call.
winteum said:
1) Sometimes it takes more than a minute to fix gps.
2) Sometimes while pressing home button and hold it opens recent apps and freeze a while.
3) Sometimes Facebook app goes crazy and can't control it.
4) Sometimes it's calling and need to unlock to answer the call.
Click to expand...
Click to collapse
hi, abt your questions,
1) works flawlessly on mine
2)this is the normal scenario on android, long pressing the home button gets u to all ur recent apps. what do you mean by freezing?
3)please explain the facebook thing....
4) when u place a call, there is nothing special. when receiving a call, u will have to either swipe right or left( screen is same as lockscreen) but with options to answer or to reject.
sincerely i have not experienced any ''bugs'' u mentioned above. my guess is that u are not used to android and u r interpreting some of its features as 'bugs'.
1) Not only can't fix gps signal easy also cell and 3g signal is lost a lot.
2) I mean when a long press to return home, instead it open recent apps a turn off the home button so I can't do anything except to touch one of recent apps.
4) It happened twice with me when I was receiving a call the lockscreen aks me the pin code.
deeren said:
hi, abt your questions,
1) works flawlessly on mine
2)this is the normal scenario on android, long pressing the home button gets u to all ur recent apps. what do you mean by freezing?
3)please explain the facebook thing....
4) when u place a call, there is nothing special. when receiving a call, u will have to either swipe right or left( screen is same as lockscreen) but with options to answer or to reject.
sincerely i have not experienced any ''bugs'' u mentioned above. my guess is that u are not used to android and u r interpreting some of its features as 'bugs'.
Click to expand...
Click to collapse
Be prepared to find more bugs.
onthecouchagain said:
Be prepared to find more bugs.
Click to expand...
Click to collapse
You know, i'm very disapointed with gingerbread. It's unfinished with a lot of bugs.
Did you see the issues list at code.google?
I'm wondering if Apple also works like that launching ios versions with a lot of bugs.
Releasing software riddled with bugs is more or less commonplace nowadays, and that's not going to change. So get used to it. And everybody does it, even the QC whores at Apple. If you think these bugs are bad, you should try playing a modern-day shooter video game on a console.
winteum said:
1) Not only can't fix gps signal easy also cell and 3g signal is lost a lot.
2) I mean when a long press to return home, instead it open recent apps a turn off the home button so I can't do anything except to touch one of recent apps.
4) It happened twice with me when I was receiving a call the lockscreen aks me the pin code.
Click to expand...
Click to collapse
My gps is working better here than any other phone I've used. It got a fix on my location in the back passenger seat of a moving car yesterday. Was awesome!
I've encountered the inbound call issue twice now. Heres the sequence for me:
1. User calls..
2. I go to slide to unlock..
3. Nothing happens...
4. Try again...
5. Nothing happens...
6. Lock screen
7. Unlock (pattern unlocker for me)
8. Eureka it Works! (Finally call answered).
...Very odd.
I know it's my imagination but, I swear, it's as if this phone has it in for me. Every time I want to show my friends something on my phone, it lags, or glitches, or freezes, or even once it just rebooted by itself. And you can forget about showing people a photograph in the gallery -- most of the time, you're just standing there holding your phone for upwards of a minute before photo albums will load. And then, if you're really having fun, it'll open the wrong photographs.
Just one of many embarrassing scenarios that can happen with this phone. Gingerbread Glitch-train, making all stops.
I had a issue with the home screens, swyping from one to another became very slow. So I went to apps in execution and stopped the launcher then back to normal, odd...
Also, I had the difficult trying to unlock the phone to receive a call, but it was a minor one.
Sent from my Nexus S using XDA App
jamiemac1977 said:
I've encountered the inbound call issue twice now. Heres the sequence for me:
1. User calls..
2. I go to slide to unlock..
3. Nothing happens...
4. Try again...
5. Nothing happens...
6. Lock screen
7. Unlock (pattern unlocker for me)
8. Eureka it Works! (Finally call answered).
...Very odd.
Click to expand...
Click to collapse
That happened to me many times
winteum said:
1) Sometimes it takes more than a minute to fix gps.
Click to expand...
Click to collapse
Taking more than a min to find a GPS signal doesn't mean anything...satellites move
resetting/shutting down phone will reset GPS data and might take longer to get fix and also depends on available sats where u are located and might take longer
If everything you mentioned were bugs we all would have them and its not the case...have you tried restoring and if so IDK maybe return phone
I was wondering if anyone else was experiencing KnockON inconsistencies with their G2. Turning off always works properly. But if the phone has been idle long, it hardly will ever turn on the first one, two, or even three times I knock on it. Sometimes I have to tap it rather hard to function. I've tried different locations on the screen, as well as the center where the phone actually instructs you to do so. Then I tried faster and slowerand it makes no difference. The tips of my fingers are hurting now lol.
Thanks!
fhblake04 said:
I was wondering if anyone else was experiencing KnockON inconsistencies with their G2. Turning off always works properly. But if the phone has been idle long, it hardly will ever turn on the first one, two, or even three times I knock on it. Sometimes I have to tap it rather hard to function. I've tried different locations on the screen, as well as the center where the phone actually instructs you to do so. Then I tried faster and slowerand it makes no difference. The tips of my fingers are hurting now lol.
Thanks!
Click to expand...
Click to collapse
Surprised you're the first to bring this up, lol! Been watching this device closely on on youtube reviews on this device you can see it right infront of your eyes. Doesn't ALWAYS wake on double tap but does ALWAYS turn off, weird. Idk what to tell ya but yes it isn't just you...
Are you using the stock launcher?
I switched to Nova and noticed its very finicky for me ever since I stopped using the stock launcher.
Still on stock launcher.
I just tap it 4 times when turning on, no big deal.
The only time it fails for me is if I tap too softly. I notice that when turning it on, it does take two distinct forceful taps. It seems to register anything else as a touch. So, while I think it could be better, I don't see it as inconsistent. If it was too sensitive, it might end up turning on in your pocket.
I think it has to do with the motion sensor in the phone. Mine works fine if I just tap it twice while it's in a steady position (even in my hand), but when I'm riding my bicycle I can't get it to tap "on" most of the time (unless I stop). Tap off works much more reliably.
i'm pretty sure there's a deep sleep issue, but that's to be expected..once the process that controls knockon goes to a deep sleep, of course it won't work right away.
Tapping near top of screen seems to work much better.
geoff5093 said:
I just tap it 4 times when turning on, no big deal.
Click to expand...
Click to collapse
Exactly.
Can't have both battery life and also expect the Knock feature not to go to deep sleep. I prefer to eat my cake.
Also, I like that it does not accidentally turn in my pocket or when gripping the screen in my hands, etc.
The Korean version has gotten a few updates to make KnockOn smoother, so you might not have that update yet.
Well, I have a VZW version so updates will not be plentiful lol. Knocking on it several times, rather than twice seems to work better. Thank you guys for your suggestions.
jayochs said:
i'm pretty sure there's a deep sleep issue, but that's to be expected..once the process that controls knockon goes to a deep sleep, of course it won't work right away.
Click to expand...
Click to collapse
Maybe we should shake it a few times and then double-tap the screen. It would be like a Moto X/LG G2 hybrid!
I’m doing a study right now with this feature by recording the time and results. So far 3 quick knocks resulted in successful power ups 100% of the time (7 for 7). When doing 2 knocks (prior to the study) it was intermittent to the point of driving me crazy.
Come to think about it when you knock on someone’s door do you knock 3 times or 2? I always knock 3 times but the video reviews of this feature messed my thought process up with 2. First world problems I guess. LOL
I will report back with my results tonight.
BaronInkjet said:
Tapping near top of screen seems to work much better.
Click to expand...
Click to collapse
Same for me. It says you need to either tap in the middle or top of screen. Anywhere else doesn't work as well.
Sent from my LG-D801 using xda app-developers app
Seems to work best if you tap where the lock screen widgets are located -- top center, but not at very top.
Anyone having a problem with the phone going unto deep sleep and then just shutting down?
Sent from my LG-D801 using Tapatalk 2
I have an explanation. I think this happens because when the phones asleep (screen and touch panel is off), knockon uses the motion of the phone, read by the accelerometer, to recognize that two-tap pattern and subsequently turn on.
When the phone and screen are on though, the mechanism happens by direct touch input and is much more reliable, so it should happen every time.
This would explain why in moving situations like riding a bike, or when I was trying to turn it on while it was on the bed, which probably absorbed the motion from the taps it doesn't work as well.
I did hear that the Korean version got a firmware update that helped, though who knows when we'll see that in America.
razball said:
Anyone having a problem with the phone going unto deep sleep and then just shutting down?
Sent from my LG-D801 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like a defective phone.
Factory reset time!
Good to know dam lol that's annoying well I guess I'll wait till it happens again to be really sure
Sent from my LG-D801 using Tapatalk 2