So apparently my battery drain/overheat problem has to do with a defective phone
so since its only been 2 weeks since I had this phone. I'm going to try and
exchange it for a new one and see I still have the issues.
I thought it was more of the new radio/firmware problem but from reading from
what some devs says its a bad phone.
cant be your phone .. ive had those issues time to time since installing the new firmware. and ive had this phone since november.
Sent from my ADR6425LVW using Tapatalk
That what I thought, but I'm going to give it a try so I can at least rule it out.
kryptik06 said:
That what I thought, but I'm going to give it a try so I can at least rule it out.
Click to expand...
Click to collapse
REturn it, I had the same exact issue did a bunch of troubleshooting and none of it helped. It's defective.
nolimit78 said:
REturn it, I had the same exact issue did a bunch of troubleshooting and none of it helped. It's defective.
Click to expand...
Click to collapse
Just got it exchanged going to unlock and reroot
Sent from my ADR6425LVW using xda premium
Battery still seems hot even at stock everything, but the battery drain is better
Sent from my ADR6425LVW using xda premium
Thadrow said:
cant be your phone .. ive had those issues time to time since installing the new firmware. and ive had this phone since november.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Ive had my phone since November too and I Just started having problems when I ran the leak ruu.
Sent from my HTC Rezound
Related
I just got my S II and when on calls it has a buzzing or static sound during calls at times when the person I am talking to gets louder. I have turned the volume down to almost silent and it still does it. I am using Unnamed ROM, but it did it before the new ROM was loaded. Does anyone know if this is a physical problem with the phone or a software issue, and does anyone know anyway to fix it?
Thanks in advance!
I am using Unnamed v. 1.3.1
Probably just a hardware issue. I haven't seen similar problems from friends or online. If it was a software problem, it would be patched probably.
shadowskorch said:
Probably just a hardware issue. I haven't seen similar problems from friends or online. If it was a software problem, it would be patched probably.
Click to expand...
Click to collapse
Thanks! That is what I thought, but I was hoping maybe there was a software issue that could explain it. I guess I will have to return it for a new one.
I just recently noticed that mine has the same exact buzzing issue. Only just noticed a week ago and have had the phone just over 4 weeks. I am planning on returning when I get a chance also.
derekbro said:
I just recently noticed that mine has the same exact buzzing issue. Only just noticed a week ago and have had the phone just over 4 weeks. I am planning on returning when I get a chance also.
Click to expand...
Click to collapse
I called AT & T and worked through all their troubleshooting, which included a factory data reset, and nothing worked. So Amazon is sending a replacement phone out. It must be rare, because I could not find other S II owners mentioning this issue before.
faithofgod said:
I called AT & T and worked through all their troubleshooting, which included a factory data reset, and nothing worked. So Amazon is sending a replacement phone out. It must be rare, because I could not find other S II owners mentioning this issue before.
Click to expand...
Click to collapse
My sgs2 has an aux port that only plays 1 channel of sound and I just noticed this 2 months in. Great....
Sent from my AT100 using Tapatalk
The paint inside the port is wearing away. The phone itself is perfectly normal. Just for clarification.
I just started getting the same thing on my s2. Just got it 2 months ago.
Necromancer! Nice!
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Necromancer! Nice!
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
it's the first one that came up when i googled.
Add me to that list. Mine recently started to buzz and it's fairly annoying. Since I got mine in December of last year, I guess I'll be getting a refurb, sigh.
Let's let old threads die. That was the point.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Let's let old threads die. That was the point.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
no thanks.
then i'd get yelled at for posting a new thread and not searching when one already existed.
I have this issue where my phone screen will randomly become unresponsive. To get it back all I have to do is shut the screen off and back on and the it will accept my input. The menu, home, back, and search buttons will still work just the screen wont respont to me touching it. It may happen several time in a few minutes. Then again i might go a day it only happen once. I dont recall this happening on unrooted 2.2.2 but Im not 100% sure. It does do it 2.3.3, 2.3.4, 2.3.5, and it has done it on Liberty, Eclipse, and Molten. If anyone else has run into this problem and has a way to fix it i sure would appreciate the help.
I have the same issue. Its a deffective screen. No matter what rom you are ob it will be there. And if your is like mine it was there on 2.2.2 unrooted.
Answer to it is getting a referb. But what i learned on referbs from moto (i went through 6 razr2 in one 1 hr never left the verizon store. One worse then the other) so if thats all your worring about then id say put up with it you could get one thats even more of a pos.
Its only annoying to me when it acts up while im typing a long txt or playing a game other then that its two presses and a swipe and all better (and mine happens at least 6 times a day everyday) consider yourself lucky you could have my pos dx2.
Sent from my DROID X2 using XDA App
Ok. Its not to bad I mean Ive kinda gotten use to it. Its just annoying as hell cause it always happens at the worst time.
Mine does this too from time to time. Same fix.. Turn screen off and then back on and all is well again. Hasnt done it a long time though
Sent from my DROID X2 using XDA App
Yatkoos said:
Mine does this too from time to time. Same fix.. Turn screen off and then back on and all is well again. Hasnt done it a long time though
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
If mine did that more then once I would be in with Verizon getting a replacement...not a refurb. No way would I deal with a unresponsive screen but mine is only a few weeks old. If you deal with them right you might get a new phone out of it. The in store employees have always treated me well.
Over the course of 6 months back when I had my Samsung Rogue they exchanged it for a new one 3 times until I got a new one. After about a month or so it would start to randomly reboot.
motcher41 said:
If mine did that more then once I would be in with Verizon getting a replacement...not a refurb. No way would I deal with a unresponsive screen but mine is only a few weeks old. If you deal with them right you might get a new phone out of it. The in store employees have always treated me well.
Over the course of 6 months back when I had my Samsung Rogue they exchanged it for a new one 3 times until I got a new one. After about a month or so it would start to randomly reboot.
Click to expand...
Click to collapse
Its been so rare for me it hasnt bothered me enough to worry about. Ive also had poor luck convincing people problems exist when I can't recreate them on demand.
Sent from my DROID X2 using XDA App
Yatkoos said:
Its been so rare for me it hasnt bothered me enough to worry about. Ive also had poor luck convincing people problems exist when I can't recreate them on demand.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
I could never get it to reboot in there so I would explain the issue and politely suggest that I should switch to a different carrier since I cant depend on my phone and it worked every time.
I might go up to the store and see what they will do. At the worst im still stuck with the phone till I upgrade.
This sounds like a defective screen. You should look into getting a replacement.
I might go up to the store and see what they will do. At the worst im still stuck with the phone till I upgrade.
Click to expand...
Click to collapse
I would go in....if you play it right you might even be able to talk yourself into an early upgrade.
Sent from my DROID X2 using xda premium
Mine does this quite regularly, and I have issues typing sometimes because of this. It's incredibly aggravating, but I'm getting a GNex soon, so I'm not too worried about it anymore.
motcher41 said:
I would go in....if you play it right you might even be able to talk yourself into an early upgrade.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Now that alone would make it all worth while. Now I've got to give it a shot.
If my phone started doing that I would have been at the store before I even thought about making this thread lol.
Sent from my DROID X2 using xda premium
pacman377 said:
Now that alone would make it all worth while. Now I've got to give it a shot.
Click to expand...
Click to collapse
Shmooz them.with all the I love the network. Ut this screen just drives me nuts and blah blah. Then shmooz into you need a replacement cuz you've only had is x amount of days...then if they agree to it just bring up you know when I got this phone this other phone wasn't out and I would got that one. Instead of giving me a new one how about I just pay the difference with the upgrade cost like if I just upgraded now instead. I mean a sale is a sale and im just trying to have a good phone I don't trust this one not to brake again. Maybe throw in id hate to have to go to att or sprint for a good phone.
You'll be golden
Sent from my DROID X2 using xda premium
I like it. I like it a lot. Of course this never worked with sprint. But who knows. Razer here I come? Uh.... Maybe.... I hope.
03civicdx said:
If my phone started doing that I would have been at the store before I even thought about making this thread lol.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
This phone is a replacement. My first x2 had an unfortunate accident at the river. This one wasn't stock for an hour before I was getting eclipse on it. So I was asking to be sure it couldn't be related to the things I had changed on my phone. If I had be certain of this yes I would have gone directly to Verizon.
pacman377 said:
This phone is a replacement. My first x2 had an unfortunate accident at the river. This one wasn't stock for an hour before I was getting eclipse on it. So I was asking to be sure it couldn't be related to the things I had changed on my phone. If I had be certain of this yes I would have gone directly to Verizon.
Click to expand...
Click to collapse
One sure fire way to be certain is to sbf to stock. If the problem continues then you know its hardware related.
Sent from my DROID X2 using xda premium
03civicdx said:
One sure fire way to be certain is to sbf to stock. If the problem continues then you know its hardware related.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
+1
Sent from my DROID X2 using xda premium
03civicdx said:
One sure fire way to be certain is to sbf to stock. If the problem continues then you know its hardware related.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I have sbf multiple times since I've noticed it. It has done it every time, and every rom, even when i went and mixed and matched between a couple different roms. So from what I've heard it is deffinetly hardware related, which is why i asked. So to all of you who have helped me, a big thank you.
I've had this happen too. Not hardware related though. In my case it was caused by Launcher Pro. Switched to Go Launcher and haven't had a problem since. Might be something to look into if you use LP too.
Sent from my DROID X2 using xda premium
I've had the random reboot problem (about once per day and I've only seen it happen once), and was wondering if there was anyway to go in and see the crash report that gets sent to htc? When it asks me to send it I know I can preview the log, but is there anyway for me to go back and view it?
Also do you guys think I just send this evo back under warranty? It's completely stock haven't ran an ruu yet but I'm about to.
This seems to be a common problem with the htc amaze. Is this also an issue with your phones?
Sent from my HTC_Amaze_4G using xda premium
fcpelayo said:
This seems to be a common problem with the htc amaze. Is this also an issue with your phones?
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
There's a multipage thread a few pages back. Doesn't seem all to common but it definitely is an issue.
chococrazy said:
There's a multipage thread a few pages back. Doesn't seem all to common but it definitely is an issue.
Click to expand...
Click to collapse
I bought one on launch day and it rebooted a lot so I exchanged it this one hasn't rebooted at all after a few weeks
I think if you use root explorer you can view HTC log I just don't remember where exactly its located. You can also pull a last_kmsg with adb or an app.
Sent from my HTC_Amaze_4G using xda premium
Mine just started to do this 2 weeks ago. I thought it was an app that was updated. I was thinking about doing a reset before trying to take it in. Has anyone tried resetting when this happens?
So we all know about the sleep of death issues with this phone initially. It caused me to replace my phone. However, I am STILL getting stuck in deep sleep every day. I got it on SnowJB and now I'm getting it on SlickJB. The only time I didn't get it was with the 11c update. I've gotten it with every ROM since then though. Am I alone on this?
Nope. I'm in the same boat. I've been trying different things to remedy the situation. Today I'm trying underclocking. Ill know if it worked when I go to school.
Only happens when data is on and being used but wifi is on but not connected.
If I am connected to wifi, I never get them.
Sent from my LG-E970 using xda premium
Maybe there's still a "bad batch." I only get bsods maybe once or twice a month if that. To get so many is really bizarre.
Sent from my LG-E970 using xda app-developers app
I hardly ever have wifi on, and when I have it on it's connected. I get locked out when just data is on. Maybe I'll see about unrooting and getting another replacement.
Is it possible the BSOD issues are being caused by CPU grade?
Mine is a 3/FAST, and I got SoD's on SnowJB and Nocturnal LE, but only like one or two on SlickJB, and NONE on the JB OTA or new CM10.1.
I posted a last_kmge.txt file that Mystery said had some good info in it and said that it was definitely the kernel. See the convo below:
Joecascio2000 said:
I was finally able to get the last_kmsg.txt file after my latest BSOD. This one actually has some info in it. I really hope it holds some answers.
http://db.tt/eeag41ot
Edit: more info, I caught the BSOD at around 10:35 and pulled the log right away. I noticed the last event is at 10:27am. So my phone BSODed 7 minutes after I left my house and was on the freeway.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
MysteryEmotionz said:
This is the best log ive got yet. Thank you. I see allot of gold information. Looks like the phone doesn't know where to root power to n its crying about it.
I don't plan on fixing it cause official source should be out soon.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
MysteryEmotionz said:
Houston is using the same source I'm using as a base. The error is def Kernel related. Just waiting for are pseudoremora source. In the mean time I released v3.2 today
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
I've increased my minimum frequency from 384 to 486 and I haven't had a SOD in over a month.
Sent from my LG-E970 using xda app-developers app
If your using the stock kernel from the at&t jb update there shouldn't be no bsod. Snowjb, slick, my kernel are using the source from the Korean lgog. What baffels me us the fact it only happens to a handful of people.
Sent from my LG-E970 using Tapatalk 2
Hello,
If anyone can save me a couple hundred bucks that I dont have, I would appreciate it.
Im running an S-OFF Unlocked DNA with
This rom - http://forum.xda-dev...d.php?t=2141129
and this kernel - http://forum.xda-dev...d.php?t=2021714
I've been running it without issues for two weeks. Today it just wouldnt turn on. It doesnt accept a charge. Ive gotten the white HTC screen to come on for a second a couple times, and I've gotten it to boot up fully once. But after the screen timed out, it wouldn't come on again.
Any help would be appreciated. Dont have money to buy another phone.
I've tried searching. Most people that have boot issues can at least get to a bootloader or recovery screen. I cannot.
Have you tried letting it charge for a long while? I've heard it takes some times up to fifteen minutes for the charging led to even lit.
Sent from my HTC6435LVW using xda premium
motumbo said:
Have you tried letting it charge for a long while? I've heard it takes some times up to fifteen minutes for the charging led to even lit.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Yea, its been on charger for a couple hours now. It had a good charge when it stopped working also. When I first put it on the charger, the orange light came on. But its gone now.
kkeller87 said:
Yea, its been on charger for a couple hours now. It had a good charge when it stopped working also. When I first put it on the charger, the orange light came on. But its gone now.
Click to expand...
Click to collapse
Try a different charger, see if that helps
RLGL said:
Try a different charger, see if that helps
Click to expand...
Click to collapse
Tried OEM, car, and different USB to computer. No go
Sent from my DROIDX using xda app-developers app
Open up the phone and try disconnecting the battery and reconnecting it if you feel comfortable doing that. I suggested that to a user having the same problem as you and that fixed it a couple of days ago.
Sent from my HTC6435LVW using xda premium
Jaggar345 said:
Open up the phone and try disconnecting the battery and reconnecting it if you feel comfortable doing that. I suggested that to a user having the same problem as you and that fixed it a couple of days ago.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
hm. let me try that. I think i could manage it.
kkeller87 said:
hm. let me try that. I think i could manage it.
Click to expand...
Click to collapse
Let me know how it goes. I hope it works out.
Sent from my HTC6435LVW using xda premium
Jaggar345 said:
Let me know how it goes. I hope it works out.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
well. I've got the back cover off. Watching some youtube videos to figure out where the battery connector is. Do you happen to know which it is?
kkeller87 said:
well. I've got the back cover off. Watching some youtube videos to figure out where the battery connector is. Do you happen to know which it is?
Click to expand...
Click to collapse
I personally have never opened up this phone so I wouldn't know. But this is a suggestion that worked for someone else and has also worked when my nexus 7 did a similar act. It wouldn't indicate it was charging and wouldn't turn on but disconnecting the battery and reconnecting it worked for me. I doubt it's something to do with software as you said your set up was working fine for 2 weeks. I'm pretty sure this should fix it for you.
Sent from my HTC6435LVW using xda premium
Jaggar345 said:
I personally have never opened up this phone so I wouldn't know. But this is a suggestion that worked for someone else and has also worked when my nexus 7 did a similar act. It wouldn't indicate it was charging and wouldn't turn on but disconnecting the battery and reconnecting it worked for me. I doubt it's something to do with software as you said your set up was working fine for 2 weeks. I'm pretty sure this should fix it for you.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Well, I got the battery disconnected and reconnected. Even though the battery sits under the motherboard, the battery has a thin connector that its accessible without removing anything else. It doesnt appear that my problem has been fixed. I guess I wont ever know, my screwdriver slipped off the screw and connected with a pin on the board and sparked. Pretty sure I just shorted the whole thing.
Claim insurance or warranty. It sounds like a hardware problem if that didn't fix it.
Sent from my HTC6435LVW using xda premium
Jaggar345 said:
Claim insurance or warranty. It sounds like a hardware problem if that didn't fix it.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I should mention it was jtagged. Not saying that was the root cause. But the inside of the phone is definitely different than a stock one. Mobiletechvideos.com put a different film on it than the one it came with. Any chance of warranty or insurance is out.
You can still try to claim it. Most of the time they aren't looking inside the phone. Though this really isn't your fault. It sounds like the hardware failed and that is why it wouldn't charge and boot. But we won't know now. I don't know how jtag works but it could have contributed to it.
Sent from my HTC6435LVW using xda premium
Jaggar345 said:
You can still try to claim it. Most of the time they aren't looking inside the phone. Though this really isn't your fault. It sounds like the hardware failed and that is why it wouldn't charge and boot. But we won't know now. I don't know how jtag works but it could have contributed to it.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I guess i could still try. Should they happen to figure it out, would they contact me before fixing, replacing, or charging me? I guess thats the part I'm worried about.
I believe they would probably just charge you. Not really sure how it works. I have never paid for insurance and I have never broken my phones.
Take a look at this.
http://www.droid-life.com/2011/06/1...ging-full-price-of-warranty-phones-if-rooted/
Sent from my HTC6435LVW using xda premium
Jaggar345 said:
I believe they would probably just charge you. Not really sure how it works. I have never paid for insurance and I have never broken my phones.
Take a look at this.
http://www.droid-life.com/2011/06/1...ging-full-price-of-warranty-phones-if-rooted/
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Thanks for the link
Also, IT WORKED! I tried turning it on this morning and it booted fine. I got into recovery and flashed rooted stock. Everything is normal again.
Jaggar345 said:
Open up the phone and try disconnecting the battery and reconnecting it if you feel comfortable doing that. I suggested that to a user having the same problem as you and that fixed it a couple of days ago.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
THANKS!
For anyone else reading this, its pretty easy to do.
That's great I'm glad your up and running.
Sent from my HTC6435LVW using xda premium
Jaggar345 said:
I believe they would probably just charge you. Not really sure how it works. I have never paid for insurance and I have never broken my phones.
Take a look at this.
http://www.droid-life.com/2011/06/1...ging-full-price-of-warranty-phones-if-rooted/
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Just to add my 2 cents,
I have sent back phones to verizon and asurion for issues and every phone except one was rooted and never had an issue. I even traded in my thunderboolt towards the dna when it came out (they offered me $72.00) and all i did was uninstall superuser/busybox & titanium backup right in front of the rep and my fiance then handed it right to the guy on the spot. He turned it on, made sure the touch screen worked & then said ok, you get full trade in price.
As for the other phones that I sent in, droid eris, incredible and 2 samsung, all with one issue or another, never once did they charge me or call or anything. Got the new phone next day, sent the old one in and thats it. I have never had an issue.
Now I know this may not have happened for every one but I think if you just send it in via mail and not have an instore rep look at it, you will never have an issue. I think if an in store rep sees an issue and realize its rooted, they may flag it in case it goes in for verizon replacement or asurion replacement but just a normal send in should not cause an issue.