Related
Within the 14 days return policy I took my Galaxy back after it bricked for no reason. I was almost stock other than unlocking it and running ADW. Too many things wrong with them so I gave it one more chance with a replacement. The new one has a working recovery/download mode so that's the biggie for me. The lag seems better and the GPS actually works. Great, I feel better. But I decided that I won't root it yet since 2.2 is coming soon. I'll let it flash as designed before digging deep.
Yeah, right. After noticing that the WiFI is still flaky at random times I turned it off again today when it wasn't passing any data. 3G still working so fine. But then the Market started to FC which I've not seen at all. I shut it down and rebooted again which is the fix for my WiFI. Well, it once again decided to brick just like the last one. I get past the logos and then just a black screen. She's bricked and I didn't even root it this time. Only thing not stock was ADW launcher instead of the Samsung thing that I don't like.
So I put her into recovery mode and did a factory reset. That fixed it and I setup all over again. Luckily with 2.1 you get a list of all your previously installed apps in Market the first time you enter so if you don't leve the app you can quickly install everything again. 20 minutes later I'm back in business except this time I'll stick with the launcher it came with, can't think of anything else that would cause this sudden bricking other than the wonder phone might be a piece of crap. I just don't know yet.
By reading the title I thought you meant that Samsungs new update to activate the 3 button combo had saved you. Having a phone with download mode enabled is quite hard to brick, you can always just put it into download mode and reflash with Odin.
That's the point, my replacement phone came with the update that Samsung is pointing people to. Labeled the same as the previous update but indeed has the button thing fixed. Until the next update comes along I'm not touching Odin or anything else, these phones have enough troubles as it is. I'm still concerned that mine bricked again simply by turning it on.
3rdcoast said:
That's the point, my replacement phone came with the update that Samsung is pointing people to. Labeled the same as the previous update but indeed has the button thing fixed. Until the next update comes along I'm not touching Odin or anything else, these phones have enough troubles as it is. I'm still concerned that mine bricked again simply by turning it on.
Click to expand...
Click to collapse
This is just my opinion but I don't think the phone would have come with the update, it would have just been an untainted unit that didn't exhibit this problem. Only a subset of new units were lacking the download and recovery modes and the fix released a couple of days ago was designed to correct that problem.
These modes are a standard feature of pretty much any Android device.
At any rate, good to hear that you have a fully functioning unit out of the box. I had to go to some length explaining and demonstrating the issue to the store from which I got my unit lacking these modes as well as my carrier until the fix came out and I fixed it myself.
I don't know either. I based my guess on the fact that Sam's fix happened to be an update that version matches what mine now shows. And my situation is a prime example why all phones need this mode. Not everyone would fix it the way I did but it only cost me 30 minutes and a few curse words because my pictures are all gone before I could get them off but I'm back up and running and that had to save somebody a few hundred dollars.
I'm still very nervous though, it did brick this morning without me doing anything. This time I don't even have NoLED or ADW but I can't leave it that way forever. My trusty Magic is way more tolerant of OS abuse.
Ok, so I returned my phone still in DOA period.
My problems were the glitching all over the place, and not just once a day, but it kept on getting worse, youtube, camera, browser, status bar, apps, multitasking, scrolling, keyboard, jumping white line in messages,etc...
Mine also was creaking arround the front camera and part of the corner of the screen there too.
My battery was displayed wrong all the time, so I couldn't see the right %.
Yellow bottom of on the screen.
Games were lagy, Tegra 3 and normal like teeter.
1 dead pixel.
Probably forgetting some problems now.
Somethings will be software, but because I(and most of us) don't know what is software I preffered to send it back before the doa period was over. Also some posters stated htv told them to send it back, witch problems same as mine.
Also if this is software for most of the part, than why isn't everybody getting the problems.
So I made this topic so you can tell what the problem was with your first device, and if you allready had your second (or third, etc) and what improved and what stayed the same... So you can we get a better vision on that.
My first phone arrived yesterday and is getting swapped out by a currier tomorrow for what will then be my second device.
The problems I am having is the jumping/bumping at the bottom of the screen; this is very inconsistant but does happen more often than it doesn't. For instance I was using the phone for 40 mins earlier it was happening, then for 10 mins it wasn't, again it happened for 5/6 mins and then didn't happen for around an hour but again its happening as we speak.
I've also had the problem whereby you can't unlock the device by pulling up the ring, and I have to shut down and startup the phone for this to be fixed. This has only happened twice so far; but again should not happen at all.
Lastly I have had the problem that when you lock the device the screen turns back on, even when you only pressed the lock button once.
I think thats everything... I do believe its software problems more than hardware, however as you have said why isn't this happening to everyone if that's the case. I guess you could look at it that maybe it is but they are either living with it or reporting it direct to where they purchased it from; either way they are not posting it on here. Who knows?
Now I do understand bugs are there in just about every phone and to be honest they are normally bugs you can live with until an update; the problem here is that the bugs are completely preventing the use of the device and/or making the use of the device very difficult. No phone should be released with this being the case.
One thing I do know for sure is that its happening to those who got the phone from a network (mines from Vodafone) and those who got it SIM free; in all areas or the world. This means they (Vodafone, Orange, O2 etc...) have not caused these problems so it eliminates any tweaks/software they may have placed onto the device meaning the problems do entirely lie with HTC to resolve. Lets just hope they do; or more importantly lets just hope its a small number of phones that are affected and that our replacements are okay.
I will let you know tomorrow what the second one is like... (sorry for the long post),
How did u notice a dead pixel
Sent From My HTC sensation (desire with rcmix s )
Phone turning back on after i pressed power button to lock the screen, got that too. But happens at random, so not always.
I saw a very tiny shiny spot when in a complete dark room, on a black background. Dead pixel i suppose.
Im considering getting it online but not sure what to do if i get a dead pixel
Sent From My HTC sensation (desire with rcmix s )
Send mine back because one of the 2 yellow spots didn't go away after 10hrs screen on (5 days) and I had some random restarts.
I don't want a faulty device, some devices will keep giving problems while others have no issues from the start.
Nitin985 said:
Im considering getting it online but not sure what to do if i get a dead pixel
Sent From My HTC sensation (desire with rcmix s )
Click to expand...
Click to collapse
You would be able to send it back if you bought it online, just like buying it from a shop. They have to give you the same period of support...
Born Twitchy said:
Send mine back because one of the 2 yellow spots didn't go away after 10hrs screen on (5 days) and I had some random restarts.
I don't want a faulty device, some devices will keep giving problems while others have no issues from the start.
Click to expand...
Click to collapse
Have you had the replacement device; how is that getting on?
Dear god I don't even know where to start.
So.....
very recently I rooted my phone and the usual, because stock is boring.
And I installed some xposed modules, only one actually, TabletMetrics for reasons.
That's when things started to get weird, first of all when I turned my phone on in the morning it would switch the color scheme to some sort of negative scheme thing, and it would get kind of static-y like an old TV, until I hit the lock button which would change everything back to normal. It continued this every time I restarted the phone.
Then a couple of hours ago it started getting real crazy. Like before turning it off would do the negative thing but now it would flash very fast and colors would be out of balance (like more red, or all green or blue) and it would scroll like a webpage that hadn't finished loading on slow internet.
And then.......it died......it left me like the summer leaves that fall to the ground.....it left me like the warmth that is stolen by winters icy kiss.....it was my child.......taken by Rumpelstiltskin in some sick game.
(Meaning it had hard-bricked and wont enter download mode, let alone turn on)
So my Question is...what do I do now?
Should I return it under warranty? Or will they see my misadventures?
Shall I sell it for cold hard cash?
Dare I strip it down and create a weapon of unparalleled devastation, capable of wreaking havoc on a small group of nomadic people?
Who shall be my Shirpa on the Mountain of sorrow?
PLz:crying:
If you have truly hard bricked the device then there is no easy way to tell if it was hardware or software caused. If you take it in to the store you will more than likely get a replacement at no charge. I killed one (a year ago) from flashing to much (if that’s even possible). Phone would boot but only give me wallpaper and nothing else, no matter what is flashed to it or how many times is wiped it. Sprint ordered me a replacement at no cost; I just had to wait for it to come in.
I'm planning to upgrade to the LG G4 from the G2, because I have enjoyed the G2 mostly, other than the fact that it went into boot loops and the wifi stopped working.. but I have a few questions.
1) If the speakers are on the back, can you hear properly when you're holding something, doesn't your hand cover it? And even if you're holding it horizontally to watch a video or something, is the sound quailty bad?
2) I heard that LG officially announced that they released phones that have boot loop problems. So after a year when my warranty runs out, and the boot loop starts, will they still fix it?
3) How is the quality of the Android 6.0? I live in Canada using TELUS.
4) Also when the LG G5 comes out in a week, will the price drop?
I would really appreciate if someone would answer these questions. Thanks!
Minchan_5 said:
I'm planning to upgrade to the LG G4 from the G2, because I have enjoyed the G2 mostly, other than the fact that it went into boot loops and the wifi stopped working.. but I have a few questions.
1) If the speakers are on the back, can you hear properly when you're holding something, doesn't your hand cover it? And even if you're holding it horizontally to watch a video or something, is the sound quailty bad?
2) I heard that LG officially announced that they released phones that have boot loop problems. So after a year when my warranty runs out, and the boot loop starts, will they still fix it?
3) How is the quality of the Android 6.0? I live in Canada using TELUS.
4) Also when the LG G5 comes out in a week, will the price drop?
I would really appreciate if someone would answer these questions. Thanks!
Click to expand...
Click to collapse
Hi- Almost a week ago, even I upgraded my phone from G2 to G4. So far the experience is really awesome. Please find my answers below. Note: I am not a phone expert and I am putting across my views as a normal person would be able to explain.
1) The shape of the LG G4 is in such a way that the back speaker will not lie flat on its face at any time. So whenever the phone rings it will loud enough. Also when playing games I don't think the speaker will be covered with anyone hand. Again the positioning of the G4 comes into picture. I have installed couple of games and I have not found any issues.
2) Yes. that is correct. LG also accepted the fact about the boot load issues. This issues were primarily found on phones that were released before May or June and the motherboard was replaced free of cost by the Service Center. The one that I bought has the manufactured date as of December 2015 and so far not even once I faced any boot load issue. Probably you can check the manufactured date.
3) I have no clue about Android 6 as I live in India and I am still waiting for the update.
4) Regarding the price factor, I doubt you'll see a drastic cut in the price once the G5 is released.
I need not tell the good things about the phone cause you might have already learnt about it. But yes, it now supports quick charge. :laugh:
Thanks!
Now can someone who has used android 6.0?? per chance??
I have had the phone for 3 weeks soon, and it has two serious problems: keyboard is laggy, meaning that when you write fast, it won't recognize all the presses. There supposedly is an update for the LG keyboard regarding that issue, however I don't have any updates available for the keyboard so I think I already have it, but it is still very laggy. Which leads to a conclusion that the issue is either throttling down the CPU or then it's a digitizer issue not being sensitive enough. Note that unlike Samsung phones, LG doesn't have an option to change the sensitivity of the screen. But as I write now, the lag issue appears when typing and it freezes the keyboard for about 0,5 secs and also the screen too, so it would indicate either a software bug or CPU being throttles or who knows what. Either way, I hate that one of the most recent LG flagships have a problem of this kind... Regarding warranty, I contacted LG Finland and they just replied that most likely it has no problem, even though I've never had any issues like these on my earlier Samsung phones...
Also, Knock code doesn't always wake up the device, neither does double tapping the screen, which most likely goes back to either CPU, software or digitizer issues. Hate it when I should be able to wake my phone when I'm having the phone in my car holder and it won't wake up because of these issues with the device. I do have the 6.0 update available but haven't had the time to install it yet, also i've heard that as it handles something differently compared to Lollipop, some apps might not work and so on... Which is turning my willingness to update down a bit.
The phone has potential, and it's a shame that because of these issues, I might go back to Samsung soon.
heartagramm said:
I have had the phone for 3 weeks soon, and it has two serious problems: keyboard is laggy, meaning that when you write fast, it won't recognize all the presses. There supposedly is an update for the LG keyboard regarding that issue, however I don't have any updates available for the keyboard so I think I already have it, but it is still very laggy. Which leads to a conclusion that the issue is either throttling down the CPU or then it's a digitizer issue not being sensitive enough. Note that unlike Samsung phones, LG doesn't have an option to change the sensitivity of the screen. But as I write now, the lag issue appears when typing and it freezes the keyboard for about 0,5 secs and also the screen too, so it would indicate either a software bug or CPU being throttles or who knows what. Either way, I hate that one of the most recent LG flagships have a problem of this kind... Regarding warranty, I contacted LG Finland and they just replied that most likely it has no problem, even though I've never had any issues like these on my earlier Samsung phones...
Also, Knock code doesn't always wake up the device, neither does double tapping the screen, which most likely goes back to either CPU, software or digitizer issues. Hate it when I should be able to wake my phone when I'm having the phone in my car holder and it won't wake up because of these issues with the device. I do have the 6.0 update available but haven't had the time to install it yet, also i've heard that as it handles something differently compared to Lollipop, some apps might not work and so on... Which is turning my willingness to update down a bit.
The phone has potential, and it's a shame that because of these issues, I might go back to Samsung soon.
Click to expand...
Click to collapse
Thanks for you opinion!
i disagree with heartagramm.
when I bought the phone (2 weeks ago) it came with the 10a firmware (the first one, i think) and it was super smooth, no lag issues, everything it's awesome!
The bootloop issue its present on the 505 devices, (the first releases, manufactered in may)
Installed CyanogenMOD and it still resets, locks up and has other performance related issues.
I did an OTA update to Marshmallow originally. This corrupted my SD card and then caused about 10 resets a day, ranging from when I was using it lightly to heavily or even when it was sleeping/screen off. If I woke it up it would reset or I could feel it reset when it was in my pocket.
First thing I did was a factory reset. I tried other tricks such as swapping out the battery, SD card (or none at all), clearing cache, etc.... Nothing worked. So I tried installing CyanogenMOD, and I failed. But I got the phone back to BPA1. I updated back to marshmallow via my computer and the Verizon software updater.
About a day later the resets and lockups came back. I kept it light of apps but did slowly begin to reinstall some of my usuals (from the play store).
I had some more time so I tried installing Cyan again and was successful. It took a long time to load and optimize but it worked. I used gapps mini and the only step I did not follow in the guide was I did not install xposed.
It's been running for about 12 hours and has hanged, locked up and rebooted on me multiple times. Chrome even locks up (it will stop resounding, I'll get the message asking if I want to wait or close at the same time it starts responding again.)
When it reboots, it still takes forever and even optimizes apps (that I assume have already been optimized). I've seen two boot screens for it, one the little alien guy and the other with gears turning. It did the gears the second time I booted and then I haven't seen them again.
I'm not sure what my next step should be. Maybe I'll try reflashing Cyanogen. I have a feeling it's a hardware issue at this point, but I'm open to ideas. Are there any good diagnostic tools that could help my situation?
The phone is out of warranty and I'm sure that now that I've installed Cyanogen, the warranty was voided anyway. It's a shame because this phone was perfect up until the marshmallow update. I probably had 5 lockup/boots in the year or two I've had it.
Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.
HORIZONx720 said:
Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.
Click to expand...
Click to collapse
Admittedly, I did not even know about lineage until my phone was wiped with no OS. I did a quick Google search for it but could not find a Verizon note 4 mod. Now that I am not pressured to find a fix, I'll research it a bit more. Thank you.
I tried EmotionOS and NSeven, but both share the same error.
Emotion FCs random processes sporadically and then when my cell/data switches to Searching, it crashes multiple processes until the UI (trebuchet is default for Emotion?) and/or settings FCs and I have to restart. I am also stuck on 3G on that platform. I'm guessing network connectivity / switching is the root of the problems.
Nseven installed and right at the Welcome Screen where I pick my language, Google Play Services started crashing. I only had the option to click OK and then every 5 seconds after that, it kept crashing. I set up the phone, restarted and Google Play Services started crashing again. I am in the process of restoring back to Emotion, as it is the most stable platform so far.
I tried a new SIM card, hoping this was the problem but to no avail.
Does anyone have any other suggestions? I'm guessing its hardware at this point, but since it happened on an OTA Update and I can reproduce the same errors every time, I'm hoping there's still an option left for a fix.
Holy crap. As I was typing this and restoring Emotion, it fully installed and booted. I have 4G! I don't know if that will fix the FC issues, but I have regained a little hope!
I'm still getting FCs and restarts. The more I use it the more it happens, but at least with EmotionOS, It's more limited. Only about 3 or 4 a day compared to 10-20.
I'll try one more flash and I guess tough it out until my contract is up in April.
I can't help you with EmotionOS (haven't tried it yet), but if you want to stop the Google Play Services crashing in NSeven you can make your way to Settings - Applications, then select Google Play Services - Permissions and give it all permissions. It's a bit of a chore to get there when the warning pops up every five seconds, but it will stop once you do that.
So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.
Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.
trickyvinny said:
Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.
Click to expand...
Click to collapse
I know a lot of people are blaming software, but I'm fairly certain that the problems in many cases are caused by failing hardware. I went through many of the same trials and tribulations with my Note 4 (except I never rooted the phone). I finally contacted Samsung Customer Support and sent the phone in for repair. They replaced a lot of the hardware including the motherboard and returned the phone in "like new" condition. I've been using it for a few weeks now and the performance is flawless.
I was planning to get either the V20 or the G6 if I wasn't able to get the phone fixed. How do you like the V20?
I'd agree that it's most likely hardware and having to put everything in the freezer for it to when confirms it for me although I have no real expertise to say so. But I'd argue that the update created the hardware issue, it was night and day with the update. It was working 100% and then directly after the update to marshmallow, it started having catastrophic issues. Oh well, it's nice not having to pull the battery every hour or so.
V20 is pretty nice. Having used EmotionOS for a few months the switch to the Nougat was pretty smooth. The xda forums for it are a little more limited but I didn't start messing with my phone until it broke and I'm hesitant to try with a new phone given my limited knowhow.
To be honest it's not a big difference in day to day usage from the note 4. Which I like!
+ I never used the finger print scanner but really like it on the v20. I didn't bother with a screen lock before but now I'm protected and have a just as quick access.
-the grip is too slick, I feel like I will drop it. The note had that rougher back which I liked better. A case or a replacement cover should fix that though.
+ I like this top menu screen, I have quick access to a few select apps or can turn the flashlight on or whatever. I'd like it more customizable, I find I switch screens too much when trying to just pull my top menu down. If I could put everything on one tab and combine their special buttons (ie the flashlight button) with apps, it would be perfect.
-the back button and menu button are switched. I can probably customize that but I don't yet know how and by the time I figure it out, I will have relearned that habit. It actually is probably a better placement for how I hold the phone but I'm a big fan of choices.
+ upgraded camera, sound, storage. I don't notice the screen size difference, but it is a lighter phone.
-bloatware
All in all its a good shift from the note 4. I'm happy to be off of Samsung and still have the same basic user experience.
trickyvinny said:
So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.
Click to expand...
Click to collapse
I have had the exact same problem with my note 4. It wouldn't last 30 seconds at a lock screen from a cold battery before it would start boot looping, and the longer you left it in, the worse it got. Google told me I needed a new battery from several other forums and places I read. So I ordered one and replaced with a genuine Samsung one direct from them, and it didn't change anything.
I figured out it was heat related and I had it sit on an ice pack and it would run and work fine as long as the ice pack held out, about 2 hours. I've down graded, flashed, rooted the boot loader, installed a recovery console, flashed to different versions, all have the same problem. So I've kind of reserved myself to the fact it must be a hardware problem. Perhaps it was caused by the update, but nothing software change wise seems to be able to fix it. Did wake-loc fix as well. I've spent the last week with mine trying everything in the world and every evening having it on the ice pack hooked up trying whatever I could think of or read up on doing, and basically as soon as it warms up, it starts doing it again.
Heres a pic; http://imgur.com/a/5L64V
In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.
trickyvinny said:
In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.
Click to expand...
Click to collapse
Just out of curiosity, what phone did you wind up going to?
The LG v20 and so far so good!