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.
Can anybody help me out with this? I've already searched but haven't found a clear cut answer on what to do.
For a while, I've had random events that cause my HTC Evo (running the latest stable release of CM7) cause my phone to suddenly show the "HTC Evo 4G" white screen, then go black and vibrate 5 times while having the green LED on, which never lets me do anything until I pull the battery out and start it up again. It used to only happen when I did specific things, like whenever I tried using Google Goggles at the store (and had to go through all the trouble of disassembling my 3 layer protective case just to pull the battery again). It even happened again yesterday when I was trying to use Goggles on a specific item, but it has happened before in other events since then, like when I was browsing my phone's running applications menu, or even one time when I was simply browsing the internet on it.
I've been taking steps to try and fix it, but I think it's been getting worse. I tried downloading CM7 and Google Apps again to flash on the phone to see if it fixed anything. I tried doing this again, but clearing the data and cache this time. I tried flashing the latest CM Recovery (since I stayed with 2.5.x.x for as long as I could remember), and I'm pretty sure it's gotten worse. There's points where I get to the CM7 boot animation and the phone then does the white screen and five vibrates again, and just a moment ago when I was sure I finally solved it after clearing data and cache, while filling out my Google account info, it happened again and I was greeted once again by that horrendous white screen and the five vibrates.
Now I don't know what to do. I still have S-OFF, but I have no plans to unroot. Can anybody think of suggestions? I've already tried Googling and haven't gotten anything useful enough to help me so far.
EDIT: I guessed it would help if I was a bit more specific. This started happening about two or three weeks ago after I tried using Goggles for the first time in ages. Since then, I've had this issue coming back over and over. It also puzzles me how Goggles usually works completely fine when I'm at home but causes the phone to go black and vibrates 5 times whenever I'm at a store.
Also, right now, I re-downloaded CM7 and Gapps from the CM mirrors instead of simply reusing the ones that ClockworkMod had saved for me already. I hope this somehow makes a difference.
Also, last edit, if I manage to solve this somehow, I'm going to definitely post the answer to what I did in case anybody else out there is having the same issue.
EDIT 2: Welp, re-downloading CM7 and flashing again didn't do anything to fix the problem. I'm going to try another ROM to see if the problem persists. I really want to stay with CM7, though.
Did you wipe everything? Cache and so on ect....?
I wiped everything and I'm still having the issue.
I also caved and I'm going to unroot because the retards over at the Sprint repair center refuse to look at it otherwise. I got my hopes up after hearing on places like XDA or the CM forums about how Sprint didn't care about rooted phones, but I guess the Sprint guys in my area do. I'm currently downloading unrevoked forever son and PC36IMG right now.
I'm just hoping I can get a new Evo after this, because there's a chance I could lose root forever after doing this. But I'm so certain it's a hardware problem.
SirSigma said:
I wiped everything and I'm still having the issue.
I also caved and I'm going to unroot because the retards over at the Sprint repair center refuse to look at it otherwise. I got my hopes up after hearing on places like XDA or the CM forums about how Sprint didn't care about rooted phones, but I guess the Sprint guys in my area do. I'm currently downloading unrevoked forever son and PC36IMG right now.
I'm just hoping I can get a new Evo after this, because there's a chance I could lose root forever after doing this. But I'm so certain it's a hardware problem.
Click to expand...
Click to collapse
Why would you lose root "for ever"?
Just curious ....
Sent From The Tree House Out Back!
I had the same exact issue with my Evo over the past 2 weeks. But I never use Goggles and run MIUI pretty much exclusively. I was never able to fix it and it just got worse. I unrooted and still have the same problems.
I notice it happens on 3g data, I can't remember when it happened on wifi.
I am selling mine back to Sprint tmrw and using my upgrade to get the Nexus S for$50. Then hoping the Evo 3D comes out within 30 days.
Sent from my PC36100 using XDA Premium App
I took it back to Sprint today, and after being treated like a second class citizen for rooting over and over, they managed to somehow fix the random reboots, but have initiated the OTA update for me. Now I'm sitting here with it and it's asking if I should install it now or later.
I'm hesitant because I tried to unroot earlier, and since then, the technician at Sprint said that it wasn't really unrooted or something (I remembered using unrevoked forever last year when I rooted). I'm scared that maybe I'll lose my chance at being able to root again if I accept the update or not. I'm also scared if I won't be able to get full root from here.
EDIT: SON OF A *****. I can't believe this. I applied the OTA update like a good boy and everything, and then the phone starts boot looping randomly again. This is the last straw. I'm going to go back to Sprint tomorrow and be more in-your-face about this problem. I'm through letting them treat me like **** just because I rooted my phone once.
I have a similar problem.....
My problem is random. My phone will go into constant reboot mode until I pull the battery out for 10 minutes. Just pulling the battery and putting it back does not help.
I also noticed that I am losing GPS signal occasionally. It is random too. The GPS will come on and work for about 5 minutes then just lock up. I have to reboot to get it working again and there is no rhyme or reason as to when it will stick (or wont) or how long it will last. It may work for 3 days and then not work a lick for 3 days.
The local Sprint store replaced the back red portion of my phone (the part with the camera lens and kickstand) stating it was an GPS antenna problem. I got 30 secs outside the store and tried the GPS....same problem. I went back into the store and showed them and they tried to convince me I needed AGPS on as well. AGPS always worked but is not as accurate as the satellite GPS. The repair shop refused to do more or order a replacement. I just got scammed out of $35.00 cause nothing is fixed.
I got so pissed, I called Sprint. They were terrific. They refunded the $35.00 the repair center charged me of the repair (the rip-off repair) and agreed to send a replacement phone. Awaiting arrival of the replacement but they are back ordered...so, maybe, I'll get a new phone instead of a refurb.
Long story short...I don't know what is causing your reboots. Mine could not be solved by software changes. My phone was rock solid until around a month ago. Then the GPS dropouts and reboots became more frequent until they became unlivable. I think you have a bad device and would seek replacement.
I had the same problem with mine about a month ago. It happened once about a month before that and then a month ago started happening a lot. I finally narrowed it down to how "hot" it was (body temperature in this case). So basically any time that I was in the car it happened. I was able to unroot (you have to make sure you to s-off on) and put a stock rom on it, and take it in with it happening. They took it for an hour and said they had not seen any issues. I finally convinced them and the replaced it with a refurb. I'm okay as long as it works, but it makes me wonder what happened. When I first got it I used fresh for about a week and then went to CM and was on it the rest of the time. I used an SBC kernel starting around the same time and am thinking maybe that had something to do with it... Just as a precaution I'm staying away from SBC kernels.
If I were you I would just go to the store and get a replacement if you can otherwise if it's like mine you won't be able to count on it working...
Good luck
Hi everyone!
I recently got a t-mobile galaxy s2. After having it for a week, I rooted it and tried different roms. The last rom that I installed on it was an alpha version of cyanogenmod 9. Everything was working perfectly for a few days and then I started having problems.
The problems are with my wifi and bluetooth, they wouldn't turn on. When wifi did turn on, the phone slowed down and then turned off after a few mins. Thinking this was a cause of rooting, I decided to go back to stock. I wiped everything, formatted the internal sd card, cleared all caches and completely restored everything to stock using odin and the problem won't go away.
Now I'm running stock touchwiz gingerbread rom and when I turn on wifi, it just says "error". I was only able to get it going once and thats when the phone got extremely slow and turned off.
Also it seems like everytime the phone turns off from wifi, the battery looses like 7-10% and it gets really hot.
Here are my questions,
Is this a hardware problem?
I don't have warranty because I bought it from another person. Can I send it out for a warranty repair somehow?
Thanks in advance.
I had the Wifi error also, had to send it in for repair. Make sure you Odin everything back to stock
Sent from my SGH-T989 using xda premium
Thanks for replying.
Did your phone freeze and restart as well?
I called up samsung and they asked me to ship the phone..sent me a shipping label and etc. The problem is, I bought this phone from someone on craigslist. Will I need a receipt? So far it seems like they want me to ship just the phone.
Also I went back to stock completely with odin, do I need to do this as well?
http://forum.xda-developers.com/showthread.php?t=1578184
[Flashable] Odin/Flash-Counter Reset SGH-T989D (Telus) and SGH-T989 (Tmo)
edit: Forgot to add, how can I check if my phone is good to go for warranty repairs?
edit2: Ok I did some research and figured it out. Will update when I get the phone back
Same here...
Problem started with Bluetooth (dont remember which ROM) but I dont use wifi often so I dont know if it started at the same time. Then I switch from ROM to ROM for awhile... now my phone is kinda messed up.
I had the same problem as you, one of the phone which had a very bad battery life did not put the bluetooth to sleep and the phone got pretty hot. Something similar must have happenned to the wifi (same IC maybe?)
I think the IC is now messed up because I returned to stock, (recovery and all) did it 3 times, tried stock ICS stock GB. Then for no reason yesterday, Yay wifi working again, and bluetooth.. but by the end of the day, dead again !
So I get stuck with a wifi that can't turn on/off and a bluetooth that works when it want to...
I even tried messing with my /efs (everything was fine... I think...)
My Wifi & bluetooth MAC address are "unavailable" so I guess it's back to Samsung...
I saw some people complaining about this problem and saying Samsung products are not good... I must say that I owuld not have this problem if I stayed stock... like when I rooted my HTC desire and the "flashlight" turned on and burnt the LED... not HTC's fault... anyway anyone have another dea to try ?
---------- Post added at 03:08 PM ---------- Previous post was at 03:01 PM ----------
Also,
I read like hundreds differents forums about this issue... most if not all of them ended sending their phone to Sammy...
Some did not search very hard for a solution but still. Many have reported that Sammy changed the motherboard, so I guess it's not all our fault ?
Hi has anyone noticed issues with bluetooth headset keep getting disconnected every 2 mins after this ics update? i have Voyager pro HD which was working fine on GB and problem started after this update.
syedfaz26 said:
Hi has anyone noticed issues with bluetooth headset keep getting disconnected every 2 mins after this ics update? i have Voyager pro HD which was working fine on GB and problem started after this update.
Click to expand...
Click to collapse
Yes but it could be all related to my othe rproblems, so...
Bluetooth lost Galaxy s2 ics
I am loosing every 2 min about bluetooth since my update to ICS
Has anyone ever fixed this problem? I have been having the same problem for about a year now and I can't seem to find a solution.
I had this start with my phone around December 2012. It only affected Bluetooth, so I didn't worry too much as I don't use Bluetooth. Then my Wi-Fi started copping out about a month ago. I did some research, and it looks like it's hardware related.
I have an extended warranty that I've paid into every month since I bought it (December 2011). I called the warranty company up, and because it was out of manufacturer's warranty, I had to drop $150 on a new phone. I also spent close to an hour trying to explain to them that I had done nothing wrong to the phone. Apparently, it is in the same category as it being stolen or broken. I was so choked. I've babied this phone like crazy, in fact, it still has the protective cover you find on it when you open it fresh out of the box (I just cut off the tab). I was livid.
Well, my amazing wife ended up calling Samsung directly. The call lasted 5 minutes and they didn't even question the integrity of the phone (other than what I did to fix it and the problem itself). The representative said that because we had never called them before, they would replace it for us, free of charge. I question that they might know there is a defect that happens as this isn't a one-off, but I'm very satisfied with their service. I'll be
If you can produce your original receipt, call Samsung. They should do the same thing for you as they're doing for me. Ironically enough, I'm reverting everything back to stock and backing everything up and happened to see your post.
Hope this helps and good luck.
So just a bit of a bump/update:
I sent my phone in to be repaired (honored by Samsung) and once I got it back, it worked for a while. Shortly thereafter, it started acting up again. I noticed on the sheet showing what they did for service, was apparently doing a re-flash of the original ROM and a factory reset.
Funny thing is, I used a branded TELUS ROM that wasn't exactly stock. If you pressed and held the power button, it would automatically restart... which I found fishy. I saw that this was the exact same ROM that I had put on there once I got it back, so I doubt any flashing took place. All that was done was that factory reset.
Now, to the credit of the factory reset, it worked for a brief while, but ended up with the same issue.
I'm in the midst of doing some diagnostics, but I'm not familiar with logcat. I'm back to the latest PAC build as no other ROM made a difference. I'm going to tinker for a few more days, but I'm pretty sure I'm back to square one.
Okay, I originally got this phone as an upgrade over my HTC Inspire in July. It worked great, minus a few random reboots every once in a while (if I left it in my pocket for a long time or if it was really hot in my car it would do this, but that was it). Then, about a month or two ago, I rooted it and installed a custom ROM. I noticed that a bunch of my files were missing from my internal SD card, but I wasn't too worried about it. Then my phone started acting really weird and got stuck in a bootloop. I was able to boot into recovery, but I ended up using the LG Flash Tool and went back to bone stock. Still had the issue, except I noticed that my signal would drop, and then it'd get stuck in the bootloop. So, I contacted AT&T warranty and they sent me a replacement. Now the same thing is happening to this one. It gets warm, loses cell signal, then reboots, sometimes a bootloop. This phone hasn't been rooted at all, it's been left stock. So I contacted AT&T and the guy in warranty said he thinks it's the battery, but he didn't have any in stock so he couldn't send a replacement. So I was thinking it was the battery and called LG after it seemed to get worse. They told me that they could replace the battery free of charge if I send in the one I'm using first. Since this is my only way of communication, I contacted AT&T again, and they're sending me another replacement. (Said if this one screw up too, they'll give me a different phone all together). The guy had me download some AT&T remote support app and he looked at the battery health and said it's reading fine, and that because it's reading fine, he didn't think it was the battery. :|
Here's the weird thing, about two weeks ago, it went into a bootloop. I took out the battery for a minute an tried to put it back in. Nothing. I plugged the charger into it and it basically told me that it didn't have enough juice to power on. (battery was at ~40%). So I took the battery back out and tried again. This time it came on.
Then last friday, I was jammin out to music while I was working, it would reboot when I unlocked the phone. (battery was in upper 90%'s). I plugged the charger in while it did this and everything came up as it should. But after taking it off the charger and trying to do more work, it happened again and again.
Like I said, this phone is straight from AT&T and has not had anything flashed onto it by me, hell I never even disabled all the AT&T bloat this time. I've tried a hard reset, and it didn't help. Does anybody know what would be the cause of my problems? I really like this phone and really hope I can get this figured out.
EDIT: Forgot to mention, the phone still has its IMEI number and it has the value pack update.
Got the second replacement in the mail today. It hasn't screwed up yet, but only time will tell.
-SeCra- said:
Got the second replacement in the mail today. It hasn't screwed up yet, but only time will tell.
Click to expand...
Click to collapse
Wow hope this works for you. I just got 3 Optimus G Pro's on 12/30/13 and all 3 of them to date have not had any issues. 2 black and 1 white. 2 which are running stock. 1 stock which has had a bunch of the bloatware yanked (that we could get off of it). 1 stock which has had nothing pulled, everything left the way it is. And the 3rd one (which is the one I use) which I rooted to CyanFox 4.4.2 and later to CM11 4.4.2 Nightly and haven't had any issues like the ones you've explained.
Good luck though hopefully your issue is gone. Seems like a nice reliable phone (minus LG not wanting to support it furthermore ).
mattverg89 said:
Wow hope this works for you. I just got 3 Optimus G Pro's on 12/30/13 and all 3 of them to date have not had any issues. 2 black and 1 white. 2 which are running stock. 1 stock which has had a bunch of the bloatware yanked (that we could get off of it). 1 stock which has had nothing pulled, everything left the way it is. And the 3rd one (which is the one I use) which I rooted to CyanFox 4.4.2 and later to CM11 4.4.2 Nightly and haven't had any issues like the ones you've explained.
Good luck though hopefully your issue is gone. Seems like a nice reliable phone (minus LG not wanting to support it furthermore ).
Click to expand...
Click to collapse
I really hope my issues with this phone are done too, I really love this phone. If I don't have any issues, it's going to get rooted and updated to KitKat. Otherwise, I'll try to get AT&T to give me a MotoX or a HTC One.
-SeCra- said:
I really hope my issues with this phone are done too, I really love this phone. If I don't have any issues, it's going to get rooted and updated to KitKat. Otherwise, I'll try to get AT&T to give me a MotoX or a HTC One.
Click to expand...
Click to collapse
Yeah I like this phone with KitKat. Looks like a larger Nexus 5
Only problems i'm having with CM11:
1. ATT Visual Voicemail will install but upon playing voicemails program will freeze and crash
2. Tried Google Voice however you can only hear the voicemails through speakerphone, headsets, or bluetooth. Voicemails will no play through earpiece.
3. CM11 doesn't have Screen Recorder yet (Which CyanFox did although CM11 is still fairly fresh).
4. I would like to have the LG Camera app back! Dual video recording and some of those other features are gone with the android stock Camera app. Need to look into porting that back over to KitKat (if I can).
That's bout it though...
mattverg89 said:
Yeah I like this phone with KitKat. Looks like a larger Nexus 5
Only problems i'm having with CM11:
1. ATT Visual Voicemail will install but upon playing voicemails program will freeze and crash
2. Tried Google Voice however you can only hear the voicemails through speakerphone, headsets, or bluetooth. Voicemails will no play through earpiece.
3. CM11 doesn't have Screen Recorder yet (Which CyanFox did although CM11 is still fairly fresh).
4. I would like to have the LG Camera app back! Dual video recording and some of those other features are gone with the android stock Camera app. Need to look into porting that back over to KitKat (if I can).
That's bout it though...
Click to expand...
Click to collapse
Haha yeah, this phone is beautiful with stock Android, I just end up missing certain touches that LG puts in their overlay.
BTW, this phone is doing the same thing as before. I strongly believe it's the battery b/c when it went into a bootloop, I took out the battery it was warm, so I put it in front of the AC for a minute to cool it down and it's been working fine since. So, I'm going to call AT&T and see if they will send me a battery, and if they can't, I'm going to have to send this one in to LG and be without a phone for a week...:'(
UPDATE: AT&T told me "since we have tried everything else-hard resets, replacement phones- and nothing worked, we will send you a battery since it's the only thing that has stayed persistent through this ordeal. We just got some in stock and are sending one your way. If the problem continues to persist, we will replace the phone again." IT'S ABOUT TIME!!!
Just curious, but what if I continue having this issue after I get my new battery? Should I try a similar mah zero lemon battery or just have att give me a different phone altogether?
Sent from my LG-E980 using xda app-developers app
-SeCra- said:
Just curious, but what if I continue having this issue after I get my new battery? Should I try a similar mah zero lemon battery or just have att give me a different phone altogether?
Sent from my LG-E980 using xda app-developers app
Click to expand...
Click to collapse
i think there is an issue with the battery and whatever cable you use to charge the phone.I had to Lge980 when I used a thin cable I have in my room sometimes it did not charged at all and or shut down itself even when the battery had half charge ,sometimes it showed full charged but if I plugged the phone to a thicker cable connected using the oem charger or a usb 3.0 port at my laptop it showed the real charge level at 1/4 charge.I myself could't do anything since I got the phone second hand but as long as I used thick cable connected to a oem charger usb 3.0 or eben 2.0 I had no had any issues.
how'd it go?
-SeCra- said:
Haha yeah, this phone is beautiful with stock Android, I just end up missing certain touches that LG puts in their overlay.
BTW, this phone is doing the same thing as before. I strongly believe it's the battery b/c when it went into a bootloop, I took out the battery it was warm, so I put it in front of the AC for a minute to cool it down and it's been working fine since. So, I'm going to call AT&T and see if they will send me a battery, and if they can't, I'm going to have to send this one in to LG and be without a phone for a week...:'(
UPDATE: AT&T told me "since we have tried everything else-hard resets, replacement phones- and nothing worked, we will send you a battery since it's the only thing that has stayed persistent through this ordeal. We just got some in stock and are sending one your way. If the problem continues to persist, we will replace the phone again." IT'S ABOUT TIME!!!
Click to expand...
Click to collapse
I've had the exact same problem with my E980 and the refurb they sent me. Contemplating a battery replacement now. Did a new battery fix your boot loops?
-SeCra- said:
Okay, I originally got this phone as an upgrade over my HTC Inspire in July. It worked great, minus a few random reboots every once in a while (if I left it in my pocket for a long time or if it was really hot in my car it would do this, but that was it). Then, about a month or two ago, I rooted it and installed a custom ROM. I noticed that a bunch of my files were missing from my internal SD card, but I wasn't too worried about it. Then my phone started acting really weird and got stuck in a bootloop. I was able to boot into recovery, but I ended up using the LG Flash Tool and went back to bone stock. Still had the issue, except I noticed that my signal would drop, and then it'd get stuck in the bootloop. So, I contacted AT&T warranty and they sent me a replacement. Now the same thing is happening to this one. It gets warm, loses cell signal, then reboots, sometimes a bootloop. This phone hasn't been rooted at all, it's been left stock. So I contacted AT&T and the guy in warranty said he thinks it's the battery, but he didn't have any in stock so he couldn't send a replacement. So I was thinking it was the battery and called LG after it seemed to get worse. They told me that they could replace the battery free of charge if I send in the one I'm using first. Since this is my only way of communication, I contacted AT&T again, and they're sending me another replacement. (Said if this one screw up too, they'll give me a different phone all together). The guy had me download some AT&T remote support app and he looked at the battery health and said it's reading fine, and that because it's reading fine, he didn't think it was the battery. :|
Here's the weird thing, about two weeks ago, it went into a bootloop. I took out the battery for a minute an tried to put it back in. Nothing. I plugged the charger into it and it basically told me that it didn't have enough juice to power on. (battery was at ~40%). So I took the battery back out and tried again. This time it came on.
Then last friday, I was jammin out to music while I was working, it would reboot when I unlocked the phone. (battery was in upper 90%'s). I plugged the charger in while it did this and everything came up as it should. But after taking it off the charger and trying to do more work, it happened again and again.
Like I said, this phone is straight from AT&T and has not had anything flashed onto it by me, hell I never even disabled all the AT&T bloat this time. I've tried a hard reset, and it didn't help. Does anybody know what would be the cause of my problems? I really like this phone and really hope I can get this figured out.
EDIT: Forgot to mention, the phone still has its IMEI number and it has the value pack update.
Click to expand...
Click to collapse
If you want to stay on stock i recommend going to jellybean TOT 10k and rooting and installing a custom recovery back up the rom, and flash hkfriends kernel, and see what happens if you raise or lower your phones voltage, that might be the problem with it rebooting.
THE NEW BATTERY SOLVED THE ISSUE, BUT ONLY FOR A SHORT TIME. I upgraded to an HTC One M8 since, and haven't had hardly any problems with it, aside from the death star's BS
-SeCra- said:
THE NEW BATTERY SOLVED THE ISSUE, BUT ONLY FOR A SHORT TIME. I upgraded to an HTC One M8 since, and haven't had hardly any problems with it, aside from the death star's BS
Click to expand...
Click to collapse
Thanks for the response. I talked to the techs at an AT&T direct service center and they told me it's a common problem with the Optimus Pro. I'm on my third one in 8 months now and this one started randomly powering off within 15 minutes of when I took it out of the box three days ago.
zhirrad said:
Thanks for the response. I talked to the techs at an AT&T direct service center and they told me it's a common problem with the Optimus Pro. I'm on my third one in 8 months now and this one started randomly powering off within 15 minutes of when I took it out of the box three days ago.
Click to expand...
Click to collapse
Yeah. My issue was the battery for sure. Make them replace the battery and it should temp solve the issue
From what I read on the first e980 i had these phone tend to have a hardware problem where the power button is creating the same issues as OP. Some refurbished e980s have the hardware problem solved.
I'm wondering what to do, should I sent it in for repair? I've had it about a month. Since day 1 I've noticed a few issues. First Bluetooth has been terrible and would disconnect from my car. Well would say connected but would start playing over phone speakers. Also when using GPS apps such as Google Maps the phone would restart. Also I keep getting GPS signal lost over and over in both Google Maps and Pokémon Go. I tried reinstalling different versions of of Oxygen and they help for a few hours but then the issues start up again. I've also tried CM 13 and the issue still persists. I have ordered a shipping label from One Plus. I know RMA is a nightmare but do you think I should do it? What will they do when they get the phone?
got sensors problem, no proximity, compass, camera started to lag. reflashed stock rom, still the same. ordered rma, today checked at Arvato, they replaced motherboard and sended back phone to me. it was repaired in Germany, tooked 4 work days till dispatch. If your phone isn't 15 days old from purchase, i recommend to get replacement instead of repair. Good luck
Unfortunately it's been more then 15 days. Thanks for the info though. I was wondering what the process was. I just don't know what else I could do to fix it other then send it in.
I also have issues from time to time with bluetooth. I'm currently on CM btw. If I connect my phone to my car, it shows connected and also the bluetooth volume is available but it does not play music at all.I have to reboot and everything is fine but I found also a workaround. If I start playing music before connecting it worked 100% of the time... Very strange... My GPS disconnects didn't went to zero with cm but it's a lot better. With OOS I had disconnects like every 15 min and with CM randomly every few days.
Do you have another device you are ok with using if your phone is off to RMA for a week or more?
Support is pretty good they'll fix it. Just have to have a spare should that be an issue.
You'll need to create a OnePlus account and register your device. Should be there if you bought from them directly. Then open a ticket. Turn around time was like 10-15 days depending on the issue. I've had a good experience.
Experience was alright. Their repair center is in Texas so should be alright.