Related
Hi there!
My girlfriend just bought a T989 and we're having a horrible time with it so far.
We flashed Juggernaut ROM on it because the stock battery life was completely ridiculous (I'm talking losing 80% in 3 hours ridiculous, with the screen off and no apps running apart from the basic ones).
Ever since we flashed Jugs, though, the phone just keeps dying every so often, although usually when she's in a skype call. The screen will turn off, and the phone won't turn back on unless you pull the battery. If you try to plug it in to charge, it just vibrates weakly.
What the hell is going on -- can anyone shed any light? Is it a ROM issue or a phone issue? Should we send it back to Samsung/T-Mobile?
Thanks.
When you installed the ROM did you do a compete wipe?
Sent from my SGH-T989 using xda premium
Yes we did, and we cleared the cache and dalvik-cache.
re re
try a different rom or reflash it
---------- Post added at 08:24 PM ---------- Previous post was at 08:22 PM ----------
it could be the battery you can call t-mobile and just tell them your phone is getting hot and they will send you a new one free lol
Had this problem with my first gs2 still stock...would also over heat allot...had get a replacement...id suggest doing the same
Sent from my SGH-T989 using XDA
Mrettercap said:
Hi there!
My girlfriend just bought a T989 and we're having a horrible time with it so far.
We flashed Juggernaut ROM on it because the stock battery life was completely ridiculous (I'm talking losing 80% in 3 hours ridiculous, with the screen off and no apps running apart from the basic ones).
Ever since we flashed Jugs, though, the phone just keeps dying every so often, although usually when she's in a skype call. The screen will turn off, and the phone won't turn back on unless you pull the battery. If you try to plug it in to charge, it just vibrates weakly.
What the hell is going on -- can anyone shed any light? Is it a ROM issue or a phone issue? Should we send it back to Samsung/T-Mobile?
Thanks.
Click to expand...
Click to collapse
It's an undervolting issue. Juggernaut has a pretty aggressive undervolting and not all phones can handle it. You don't need a replacement or a new ROM, just download system tuner from market and up your voltage settings by 1 or 2 steps (12.5mV per step). A lot of random reboots are due to undervolting too much and are simple to fix but devilishly hard to identify if you're never encountered it before.
I am having similar issue with mine. i have stock rom running. and here is the thing. it happens to me about twice a week. It will turn off, in order for me to power it back on i need to pull the battery. it will come on and then turn off again. and i need to pull the battery again. after the second attept it will finally come on! I did a clean install twice and still has not resolved that issue!
Maybe its a hardware issue? i got that phone 2 months ago will t-mobile replace it for free? i have the 7.99 a month insurance!
thanks in advance
So I've had about 7 different android phones, flashed tons of roms on em', but there has never been a consensus on the 10 minute rule.
Some rom makers recommend you wait 10 minutes to let the phone "set" before you do anything to set it up. But others don't mention it at all.
Is this 10 minutes absolutely necessary, and whats the point?
Do you do it?
Thx
That was more for older phones. Doesn't really apply to newer phones since they are so much faster and have a ton of memory
Sent Telepathically
There's not necessarily anything that will go wrong if you boot up for the first time after a flash and just start doing things...
But it can't hurt to boot up and let it "settle" for a minute, do a fix permissions (I like to do a nandroid backup of the clean ROM too) and a reboot, and then customize things. Just good process to follow.
It was to allow stuff to cache so it doesn't lag like **** and make the rom seems ****. Rebooting after 1st boot solves this also.
Sent from my Galaxy Nexus using Tapatalk
I don't follow this anymore but I also don't immediately tinker with the phone after flashing. It would not hurt at all to do some waiting though. It pays to be patient once in awhile.
Wasnt it just because the dalvik cache has to buold upon first boot?
I'm really new to this but I figured out to be patient and let things settle.. :screwy:
Sent by my xda dev Approved:
Galaxy Nexus.
I want to ask you the combo (Rom + kernel) which use the best?. thanks
AOKP M4/Franco's Kernel M2
Sent by my xda dev Approved:
Galaxy Nexus.
axne1 said:
AOKP M4/Franco's Kernel M2
Sent by my xda dev Approved:
Galaxy Nexus.
Click to expand...
Click to collapse
Agree. That's what I'm running too.
dongtuson said:
I want to ask you the combo (Rom + kernel) which use the best?. thanks
Click to expand...
Click to collapse
Everyone is going to have different preferences and different results (even on the same model phone), but I have ran most of the ROMs currently out there for our phone and right now I am in love with AOKP with Faux kernel. This is the best my Nexus has ran since I have purchased it.
I just recently started using AOKP and I am not turning back.
---------- Post added at 09:13 AM ---------- Previous post was at 09:11 AM ----------
mark manning said:
That was more for older phones. Doesn't really apply to newer phones since they are so much faster and have a ton of memory
Sent Telepathically
Click to expand...
Click to collapse
Isn't it funny how things have changed over time.
Let the ROM settle. (no longer matters)
Use Task Killer to manage multi tasking (now bad for the OS)
Use battery calibration software on a new ROM (google says it does nothing)
This is the evolution of things and I assume it will continue to change.
Sometimes change is good.. Hopefully Google can make ics even better. But the devs are way ahead! Lol
Sent by my xda dev Approved:
Galaxy Nexus.
Haha ok, so it looks like only 10% of the conversation has been on topic.
Either way - thanks for those of you that replied. I guess i'll give it a minute..
.[/QUOTE]
Isn't it funny how things have changed over time.
Let the ROM settle. (no longer matters)
Use Task Killer to manage multi tasking (now bad for the OS)
Use battery calibration software on a new ROM (google says it does nothing)
This is the evolution of things and I assume it will continue to change.[/QUOTE]
The funny thing is that only the first was true, in android there were never any need for a task killer and also those battery calibration were never necesary...
7unk3r said:
.
Click to expand...
Click to collapse
Isn't it funny how things have changed over time.
Let the ROM settle. (no longer matters)
Use Task Killer to manage multi tasking (now bad for the OS)
Use battery calibration software on a new ROM (google says it does nothing)
This is the evolution of things and I assume it will continue to change.[/QUOTE]
The funny thing is that only the first was true, in android there were never any need for a task killer and also those battery calibration were never necesary...[/QUOTE]
+1
Sent from my Galaxy Nexus using Tapatalk
All of my friends that are linux geeks say that there is validity to giving a fresh flash some time to settle in.
KWKSLVR said:
All of my friends that are linux geeks say that there is validity to giving a fresh flash some time to settle in.
Click to expand...
Click to collapse
That's more for the kernel, Linux geeks are normally right
the day is mine
the night is also mine
asaire ppr.
I've never heard of letting it sit for ten minutes
jeetS said:
I've never heard of letting it sit for ten minutes
Click to expand...
Click to collapse
That's probably because your new to this
Sent Telepathically
It sounds like it's worth trying at least I'll wait 10 minutes
Sent from my Galaxy Nexus using Tapatalk
Hi all,
I've noticed that since the most recent ota update (xxll2) my phone discharges super fast. For example my phone has been on charge from the mains for about 6 hours, it has been unplugged for half an hour and is already at 50 percent.
I've never had this problem before, rebooted phone multiple times since I updated it. The only other thing I can think of is to flash an older version
What do you think?
Same problem here. I went back to I8160XXLK6 soon after I discovered battery drain.
Just today my phone got this ota update. Lets see whether I face this same issue or not.
Sent from my GT-I8160 using xda app-developers app
---------- Post added at 09:51 AM ---------- Previous post was at 09:43 AM ----------
arroyo said:
Same problem here. I went back to I8160XXLK6 soon after I discovered battery drain.
Click to expand...
Click to collapse
How did u go back to the old software? Does it require rooting?
Sent from my GT-I8160 using xda app-developers app
omer7 said:
Just today my phone got this ota update. Lets see whether I face this same issue or not.
Sent from my GT-I8160 using xda app-developers app
---------- Post added at 09:51 AM ---------- Previous post was at 09:43 AM ----------
How did u go back to the old software? Does it require rooting?
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
Nop, you just go to download mode and flash the firmware with odin
mojito0 said:
Nop, you just go to download mode and flash the firmware with odin
Click to expand...
Click to collapse
Ok. Lets see whether i face this batery drain issue or not... So far it is working fine, but still too early to say.
Sent from my GT-I8160 using xda app-developers app
I think the battery is fine for me. No battery issue at all.
well i rebooted it earlier and whilst out working my phone which gets used as a sat nav has been on charge, it hasnt discharged as bad as it did this morning, its been off of charge for about 2 hours and its only 95% i did pull the battery after it had updated so maybe its just getting used to it. i will see if it gets any worse and ill flash the previous update... or just wait for samsung to release the jb update :fingers-crossed:
I have the XXLL2 too, and I don't have any battery issue.
My phone was updated to the latest firmware yesterday, and even I've not faced any battery issue with the latest update (XXLL2)
Im using xxk6 and i have the battery.issue..I'll try to update later...Im not sure if my theme was the one that effected the battery or the firmware...
Sent from my sending thingy
Have you ever let the phone shutdown because of an empty battery and the recharged it to 100%?
That should maybe help, because that should wipe the battery cache.
Duke_Suppenhuhn said:
Have you ever let the phone shutdown because of an empty battery and the recharged it to 100%?
That should maybe help, because that should wipe the battery cache.
Click to expand...
Click to collapse
i didnt because i need my phone almost all the time, alarm, sat nav and gmail for viewing jobs etc and takes ages to charge on my cars cigarette lighter... ill have to leave it till the weekend but you are right, it wouldnt hurt
Odp: Battery issues since update
Don't you know that draining Li-Ion battery till zero damages it.You should never let battery drain till device shuts down.Do it three or for times and your battery will have like a half capacity.
You can clear battery stats with many google play apps or by CWM.There is an option for it.
Duke_Suppenhuhn said:
Have you ever let the phone shutdown because of an empty battery and the recharged it to 100%?
That should maybe help, because that should wipe the battery cache.
Click to expand...
Click to collapse
Btw, this battery calibration thing or the "let battery go dead zero and then charge to 100" are not working. Battery Calibration is just a myth (a busted one), And according to Google Engineer Dianne Hackborn the batterystats file has no impact on the current battery level shown to you wether you wipe it or not.
Sources:
http://forum.xda-developers.com/showthread.php?t=1460553
https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT
I also have this issue... Since XLL2 update, battery is drained more when phone is on sleep than with previous firmware. But I'm waiting for jelly bean.
Sent from my GT-I8160 using xda app-developers app
I am having a really bad problem in my Galaxy S4, and have been trying to fix it for a full day.
Basically, many of the default android apps fail to work. By fail, I mean the screen becomes fuzzy, or completely dissorited, and just crashes. The phone also randomly restarts when I use it.
Overall, I really can't use the phone. I have attached screenshots of some of the issues I am facing on the phone.
I have tried reinstalling Android version 4.2.2, but the same problem occurs.
Any help on this matter would be MASSIVELY appreciated!
More pictures of the problem.
Looks like you might have gotten a bad unit. At this point, I think you should just go ahead and exchange the device rather than trying to waste time trying to figure out what's wrong. If you buy it from T-Mobile, you should get free overnight shipping. If the one you got was from T-Mo, just return it to that 4500 address and they'll refund you fully.
---------- Post added at 06:03 PM ---------- Previous post was at 06:02 PM ----------
I should probably have also asked if you have tried to factory reset the device?
For sure its not even a week so they willl refund u full
Sent from my SGH-M919 using xda premium
Yeah deff return.. I had a few issues with my note2 a week after I got.. get a new one bro...
Sent from my SGH-T889 using xda app-developers app
So in a bout of epic boredom, I fished my Sprint Galaxy SII (sph-d710) out of a drawer, and decided I'd try to update it. It's currently running:
Touched by an S4 rom
Android 4.1.2
GB27 Agat recovery
I'd like to install an aosp rom or Cyanogen but every time I attempt to flash via Agat, I get error code 7.
Same with CWM 5. Where should I start with trying to get an AOSP rom on this device?
exjinn said:
So in a bout of epic boredom, I fished my Sprint Galaxy SII (sph-d710) out of a drawer, and decided I'd try to update it. It's currently running:
Touched by an S4 rom
Android 4.1.2
GB27 Agat recovery
I'd like to install an aosp rom or Cyanogen but every time I attempt to flash via Agat, I get error code 7.
Same with CWM 5. Where should I start with trying to get an AOSP rom on this device?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2637510
ok, have I been bit by the brick bug? I have a E4GT that I've had rooted and Rommed for a while, I had it in a drawer with a full charge, I pulled it out last night to mess with it but its dead, won't boot and won't charge, just flashes the battery image over and over, try booting to recovery or download, no cwm, says battery low, can't download, I changed nothing before I put it in the drawer and I put it there with a full charge, I had noticed a week or two before that it was randomly powering down or rabdomly rebooting. I'm not new but I've never gad thus happen, I know the gs2 has a brickbug, is this my problem? I've unbricked devices so can I fix this if its the bug? I can charge my battery by some means if its possible to get this working again but do I odin stack tar or USB jig? Any other methods? is it brickbug? Can brickbug be fixed?
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
ok, have I been bit by the brick bug? I have a E4GT that I've had rooted and Rommed for a while, I had it in a drawer with a full charge, I pulled it out last night to mess with it but its dead, won't boot and won't charge, just flashes the battery image over and over, try booting to recovery or download, no cwm, says battery low, can't download, I changed nothing before I put it in the drawer and I put it there with a full charge, I had noticed a week or two before that it was randomly powering down or rabdomly rebooting. I'm not new but I've never gad thus happen, I know the gs2 has a brickbug, is this my problem? I've unbricked devices so can I fix this if its the bug? I can charge my battery by some means if its possible to get this working again but do I odin stack tar or USB jig? Any other methods? is it brickbug? Can brickbug be fixed?
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
First thing I'd check is if your battery is bloated. If it is, replace it.
Something similar occasionally happens to me, but it's the power button that causes it... Even randomly reboots from recovery or download mode sometimes. It's as if I'm permanently holding down the power button. Usually a few good hard finger-flicks to the button jars it loose... I think it sticks sometimes from moisture, debris, etc.
I kinda noticed the sticky button, I wondered if its the battery, I checked it before I posted, therez no swelling but it was definitely very warm, I even took the cover off and pulled the whole assembly out to check the button I put it on charge without being in the cover, just the board and the battery in case it was the button, battery was warm when I checked after that so you're probably right, it just didn't make sense because it was working fine when I powered it down and put it away, thought it was strange it wouldn't do anything when I got it out, ill get a battery and see what happens, thanks.
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
I kinda noticed the sticky button, I wondered if its the battery, I checked it before I posted, therez no swelling but it was definitely very warm, I even took the cover off and pulled the whole assembly out to check the button I put it on charge without being in the cover, just the board and the battery in case it was the button, battery was warm when I checked after that so you're probably right, it just didn't make sense because it was working fine when I powered it down and put it away, thought it was strange it wouldn't do anything when I got it out, ill get a battery and see what happens, thanks.
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
If the power button is indeed stuck, then it's very possible it booted/rebooted in your drawer until it died.
Hope you get it going... Good luck [emoji106]
I'll get it, I unusually do, you know how it is. "OH H**L NO, This thing ain't beating me!"
Sent from my SCH-S968C using Tapatalk
/\
lol, I just caught it in passing when I paged down my list of threads, I meant usually, freakin' auto correct and predictive text can be some really inconvenient modern conveniences, [emoji16]
Sent from my SCH-S968C using Tapatalk
Surj138 said:
If the power button is indeed stuck, then it's very possible it booted/rebooted in your drawer until it died.
Hope you get it going... Good luck [emoji106]
Click to expand...
Click to collapse
just to update, I let the battery cool for a while then tried to charge again, its taking charge this time, I'm gonna see if it will boot just to verify if the phone itself is in working order but I'm still getting a battery. Whew....close one.
I only came here to ask because I've read a lot if posts during the time I was working on that phone about random bricks, same situation, they put it in a drawer just fine and wouldn't do anything the next time they got it out
Sent from my SCH-S968C using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------
thanks for the advice
Sent from my SCH-S968C using Tapatalk
---------- Post added at 04:06 PM ---------- Previous post was at 03:43 PM ----------
Surj138 said:
If the power button is indeed stuck, then it's very possible it booted/rebooted in your drawer until it died.
Hope you get it going... Good luck [emoji106]
Click to expand...
Click to collapse
ok, it charged and when it got to a certain point it booted on its own, I can confirm that the button isn't stuck so why did it power on by itself? If it were the button it would repeatedly boot wouldn't it?
Sent from my SCH-S968C using Tapatalk
Surj138 said:
http://forum.xda-developers.com/showthread.php?t=2637510
Click to expand...
Click to collapse
Excellent info thanks a lot!