Database Users

KindleFire with Energy ICS ROM not turning on.

I installed the Energy ROM from this thread http://forum.xda-developers.com/showthread.php?t=1528024 a few hours ago and everything worked well. I used the kindle a little and decided to charge it up, so, I plugged in the AC adapter and let it charge for like 1 hour.
When I come back, the adapter is all hot, like unusually hot. The led was red, which means the kindle was charging. Now I unplug it and hit the power button and nothing happens! Nothing, like no led, no nothing. I long-press it and still nothing. I press and let go a couple times and still nothing!
What does this mean? Is my Kindle fried? Because of a ROM!? What can I do now? Please help me
EDIT:
Ok, I fixed the problem. It looks like the Kindle Fire was overheating while connected to the AC adapter. So, I let it lay down a fan for a while and I tried to turn it on and it did. Very dangerous ROM that one, I think I'm going to get CM7 or something until this issue gets fixed.

Unfortunately for now all ICS ROMs have the potential to have that happen if you leave your KF on for extended periods of time when you aren't using it. The widely held solution to that is to shutdown when you know you won't be using it for a while such as while charging or when you go to bed.

If it's fried I don't believe that depends of a rom.... I think it was the fault of the AC adapter...try to charge the KF with another adapter...

jlocohustler said:
I installed the Energy ROM from this thread http://forum.xda-developers.com/showthread.php?t=1528024 a few hours ago and everything worked well. I used the kindle a little and decided to charge it up, so, I plugged in the AC adapter and let it charge for like 1 hour.
When I come back, the adapter is all hot, like unusually hot. The led was red, which means the kindle was charging. Now I unplug it and hit the power button and nothing happens! Nothing, like no led, no nothing. I long-press it and still nothing. I press and let go a couple times and still nothing!
What does this mean? Is my Kindle fried? Because of a ROM!? What can I do now? Please help me
EDIT:
Ok, I fixed the problem. It looks like the Kindle Fire was overheating while connected to the AC adapter. So, I let it lay down a fan for a while and I tried to turn it on and it did. Very dangerous ROM that one, I think I'm going to get CM7 or something until this issue gets fixed.
Click to expand...
Click to collapse
Don't go flaming a ROM when it is a great rom, that is a good way to run a dev off from our community. I have been running the rom since it came out with no issues other than the standard HWA and other listed bugs. Many people have had the same results as me and most of the people who haven't it was because of a bad download and/or a bad flash. The rom is no more dangerous than the general process of rooting and customizing is. Did you get a log cat of what happened at all? Or do any sort of searching for a solution of what caused the issue so on the very slight chance it is a bug it could be fixed?
---------- Post added at 01:36 PM ---------- Previous post was at 01:32 PM ----------
BluesHawk said:
Unfortunately for now all ICS ROMs have the potential to have that happen if you leave your KF on for extended periods of time when you aren't using it. The widely held solution to that is to shutdown when you know you won't be using it for a while such as while charging or when you go to bed.
Click to expand...
Click to collapse
It shouldn't overheat, just freeze and force a hard restart (hold power button for about 20 seconds then turn on). If it is overheating there is something else going on like the AC adapter or some sort of major malfunction from a bad flash. Most likely the AC adapter though.

dnathan13 said:
Don't go flaming a ROM when it is a great rom, that is a good way to run a dev off from our community. I have been running the rom since it came out with no issues other than the standard HWA and other listed bugs. Many people have had the same results as me and most of the people who haven't it was because of a bad download and/or a bad flash. The rom is no more dangerous than the general process of rooting and customizing is. Did you get a log cat of what happened at all? Or do any sort of searching for a solution of what caused the issue so on the very slight chance it is a bug it could be fixed?
Click to expand...
Click to collapse
I believe there's some misconception here. I didn't flame or try to hurt the reputation of the dev or anything. I just posted about an issue and I'm sure, like any other issue, more people must have encountered it. Most people come to find solutions on forums, so, I believe I did the right thing by starting this thread.
Did you even read my OP? I posted an update long before you replied...
EDIT:
AC adapter is fine. Used it just fine on stock ROM before flashing to the new ROM.

jlocohustler said:
I believe there's some misconception here. I didn't flame or try to hurt the reputation of the dev or anything. I just posted about an issue and I'm sure, like any other issue, more people must have encountered it. Most people come to find solutions on forums, so, I believe I did the right thing by starting this thread.
Did you even read my OP? I posted an update long before you replied...
EDIT:
AC adapter is fine. Used it just fine on stock ROM before flashing to the new ROM.
Click to expand...
Click to collapse
Yes I read the op where you claim... "very dangerous rom that one" that is the part that I would say is harsh.
Many people have been running the show rom for days with no issues, but one or two people claiming it will overheat and kill their fire is all it takes for everyone to start bashing a rom and make a dev want to leave.
Sorry I came off as a jerk I just get upset when claims are made based on one bad experience that could have been caused by a number of things (bad flash, left over bits of stock conflicting with rom, lack of knowledge of ICS issues about screen timeout, kernel issue ratjer than rom issue although related, etc...)
Sent from my SPH-D700 using xda premium

No over-heating problems at all for me -- I installed Kang ICS ROM three days ago.

[Q] Phone not charging after gfree method root

I got the phone just 3 days ago from an insurance claim, had no problems with it other than the power button is a pain sometimes.
I rooted the phone yesterday with visionary at first, then gfree after i got the s-off, and I have the CWM 5.8 touch recovery. I then flashed Virtuous Unity 2.39 and the Darkside v12 kernel, as well as all sorts of different radio's. I then fell asleep after installing those, and before setting up the ROM, and i left it charging on my computer overnight.
I woke up about 5 hours later, and the phone was at 4% battery life. I dont know what happened. i can get it to about 2% charge and then it stops and dies out. i did notice that the clock on the status bar froze at one point and said 11:40 when it was really 12:27. the clock widget on the main screen was correct the whole time.
I am able to get into recovery, I am able to get into fastboot, I am able to get into the ROM...
I have switched out the radio to different one than the one last night, and i have switched the kernel to "CollectiveACE-BFS-v0.1.5" and that doesnt solve the issue. I have also cleared the battery stats, even though i didn't want to since it was at such a low level of power...none of these things helped.
I have also noticed that after the phone shuts off, when i power it back on, it goes into recovery. I am unsure why, but when I tell it to reboot from recovery, it goes right back to recovery, and i have to pull my battery to get it to go to the OS.
Any idea's? and I am sorry if this is confusing...

Try flashing a new ROM. But before you do, flash Mike1986's superwipe script from here: http://dl.dropbox.com/u/61962340/Android_Revolution_HD_Super_Wipe.zip , just to make sure everything is fully clean . Then flash your ROM of choice. Also, never flash radios for the heck of it. They can easily brick your device. Be careful, and report back

RUMyBruncle said:
I got the phone just 3 days ago from an insurance claim, had no problems with it other than the power button is a pain sometimes.
I rooted the phone yesterday with visionary at first, then gfree after i got the s-off, and I have the CWM 5.8 touch recovery. I then flashed Virtuous Unity 2.39 and the Darkside v12 kernel, as well as all sorts of different radio's. I then fell asleep after installing those, and before setting up the ROM, and i left it charging on my computer overnight.
I woke up about 5 hours later, and the phone was at 4% battery life. I dont know what happened. i can get it to about 2% charge and then it stops and dies out. i did notice that the clock on the status bar froze at one point and said 11:40 when it was really 12:27. the clock widget on the main screen was correct the whole time.
I am able to get into recovery, I am able to get into fastboot, I am able to get into the ROM...
I have switched out the radio to different one than the one last night, and i have switched the kernel to "CollectiveACE-BFS-v0.1.5" and that doesnt solve the issue. I have also cleared the battery stats, even though i didn't want to since it was at such a low level of power...none of these things helped.
I have also noticed that after the phone shuts off, when i power it back on, it goes into recovery. I am unsure why, but when I tell it to reboot from recovery, it goes right back to recovery, and i have to pull my battery to get it to go to the OS.
Any idea's? and I am sorry if this is confusing...
Click to expand...
Click to collapse
Stop flashing aosp kernels on your SENSE rom... Try darkside sense v7 or one of the unity kernels and all should be fine.
Sent from my HTC Glacier using xda premium

I have installed Icecreaminsanity 7.1 AOKP fixed or whatever the name of it is. I did not know the kernels were different depending on AOSP and Sense. If i have ICS on it now, which kernel should I use since there are no ICS kernels for the glacier?
I dont know if the charging issue is fixed yet, because i just did the superwipe and put on the ICS ROM. I will post if it is fixed or not, but my hopes are low
edit: Sorry, it is IceColdInsomnia 7.1.AOKP-test.
WOW i love this ROM...but i digress...its still too early to tell if it's going to fix the charging issue. I did notice that when the screen was on and i was going through the launcher, it didnt interrupt me telling me my battery was only at 3%...maybe that's a good sign.

No, it didnt fix the issue. While leaving the screen off and plugged into the wall, the charge dropped to 2%, and now it's blinking between the green and orange LED's...what do I do now??? Any recommended kernels for this rom? would an AOSP kernel be better than a Sense kernel for this new ROM?
Edit: I am already using the kernel mentioned by the OP in the thread for that ROM...the Collectives ACE kernel.

Get an external battery charger or find a friend with a glacier or t-bolt and charge the battery. Flash PD15IMG.zip and start over. If it still doesn't charge tell them they sent you a busted device, raise some hell, and see what you can get.
Sent from my HTC Glacier using XDA

i think that may be my only option. I appreciate your guys' help. it was really nice to see people giving actual advice with links instead of just telling me im in idiot and telling me to search for it.

Haha, well some of us are trying. Also, you didn't post in the dev section, so that's an automatic plus.
Don't forget to get S-On if you have to send it back.

estallings15 said:
Haha, well some of us are trying. Also, you didn't post in the dev section, so that's an automatic plus.
Don't forget to get S-On if you have to send it back.
Click to expand...
Click to collapse
Haha yeah, props to OP!

i'm no noob to this forum or to rooting...but i am to the MT4G...lol it's a completely different beast than the MT3G i came from. Thanks again, and i guess a mod can close this thread out...

Red Light Of Death - Should I Be Concerned?

Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??

S.H.A.D.E said:
Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
Click to expand...
Click to collapse
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.

Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...

S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
propably you could check the rev of those n4's (asking them in pm's). i can't imagine rev11+ have this problem anymore. I still won't believe this happened without a reason

S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
These many people you speak of? That's not even half possible for it to RLOD on pure stock without any mods it's just to save the hardware its the phones built in safety net...unless you plan on OCing to 1.98ghz and set it to performance and run antutu that will most likely do it for you
Sent from my Nexus 4 using xda app-developers app

Hi,
It happened wih or without running an Antutu bench. Yes some users have reported the red light on stock with rev 10 or with rev 11.
Antutu is not directly the culprit, it's due to a bad read of battery stuff (in a stress condition even at 50% battery the phone think you are out of battery then shutdown + heat, there is an issue with some phone about the battery contact inside the phone). If it's happen you can try to let your phone in charging for hours, sometimes it's enough. But the better thing is to open your phone then disconnect / reconnect the battery.
It happened also while flashing something in recovery mod, 40% battery, flash then reboot and bam red light...
Also on a French forum it happened during a download while browsing...
I agree we not know all the conditions together when it happened but it seems this is slightly random. Maybe a combination of circumstances...
It's "just" related to some weird battery reading issue.
For example I ran a bunch of Antutu bench with / without overclocking at different battery % (even at 11% battery ) without any issues, at least until today...
Take a look here: http://forum.xda-developers.com/showthread.php?p=36304348

So does this problem happen to everybody or is only a minority of nexus 4 users affected? Do you think google would've fixed this problem by now??

Re,
It seems it's a minority phones who are concerned...
I don't know if Lg / Google have worked on the problem. As I read maybe the rev 11 are less concerned? But I'm not sure...
Don't be afraid, use your phone and if that happens rma or open your phone, there is always a solution

Alright, read a lot of threads and it looks like removing the battery and starting it again works perfectly. I also read somewhere that its due to too much pressure being applied on the thing the connects the battery to the phone.. - http://forum.xda-developers.com/showthread.php?t=2128392&highlight=red+light+of+death&page=2

Yes, it's what I said, ah I forgot this link.
When you search, you find

Happened to me a few days after I got it (100%stock, not rooted); I left it charging for some time and it turned on again like nothing happened. Didn't happened since.

Only time I had it was when I first rooted.
It got stuck in a boot loop on the "X" screen and when I rebooted to clear the cache the red light flashed and I had to hold the power button in to turn it off.
Booted into recover fine after that.
No issues since.

Alright that's good to hear. When did you guys get your nexus?? Maybe google resolved this issue.

I got mine very recently ordered in late February. It did red light because I flashed a mod which was for the nexus 7 but i flashed it on my nexus 4. I just went into recovery and flashed stock, phone was fine.
Sent from my Nexus 4 using xda app-developers app

Alright. Sounds good.

Got mine last week but it's a Rev 10 not an 11.

indoh said:
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Click to expand...
Click to collapse
That is not true.. Red light appears due to some small chip next to the battery which is hardly put in there, you just need to release some pressure and it will be fine.. (there's a youtube video)

Loosen the screws?? Do you have a link to the YT video?

Ordered mine when they were first available, got it 2-3 weeks later (end of November).

Got a bricked rev11 301k here. Tried everything untill I get my replacement (takes a bit longer since I live in holland). Check out http://forum.xda-developers.com/showthread.php?t=2177787&highlight=nexus+4+bricked for more info. Now I try to drain the battery and let it charge (put it in a cold enviroment for a full 24 hrs. Got past the google logo for half a second and saw the stock recovery before it went dead again

Pretty sure I bricked my Nexus 4

I don't know how I did it. I've been rooted/unlocked for over a month (running CM the whole time) with stock kernel. Last night I upgraded to the 03.24 nightly and everything was fine. 3 hours later I downloaded a franco kernel after some reading and I wanted to try it out. I used Rom Manager to reboot into recovery (like I always do) and install the kernel and as soon as I hit "restart now" apps started FC'ing and my phone never came back on. It never made it to recovery mode or anything. It just died completely and I was around 40-50% battery life.
Currently this is what I'm dealing with:
Holding the power button down for 10 seconds flashes a red LED light. No changed on the screen
Holding any combo of the volume keys (up, down, and both) + power does the same as above
The only time the LED flashes red is when I'm plugged in via USB or AC. Otherwise nothing
I've had to charging for nearly 10 hours now... it's like it has no power at all
When plugging it into a PC I see "QHUSB_DLOAD" in my device manager.
I have the Android SDK and Nexus 4 drivers installed
I have seen NOTHING On the screen since this has happened - no charging animations, fastboot, not even a flicker
I've down A LOT of reading and the only thing I haven't tried is charging it for days at a time and taking it apart (which I'm not opposed to doing) but I'd prefer not to. Is there anything else I can try? Thank you

Sounds like you flashed the franco kernel for the Nexus 7. You aren't the first and probably won't be the last. Unfortunately if you see QHUSB_DLOAD its dead.

You can try to get Google to RMA it. Yeah man, its bricked. Next time make sure you look at what your flashing.

That's what I was afraid of... do you think this is legit? I saw the video and it looks good. Says it fixes phones that don't boot at all. I e-mailed and asked them about my situation but I'm curious if you have heard anything about them?
http://mobiletechvideos.mybigcommerce.com/lg-nexus-4-jtag-brick-repair/

blahblah13233 said:
You can try to get Google to RMA it. Yeah man, its bricked. Next time make sure you look at what your flashing.
Click to expand...
Click to collapse
Not to be an ass but it's his fault for flashing the wrong kernel. Google shouldn't have to pay for his mistakes.
Sent from my Nexus 4

blitzzz3434 said:
Not to be an ass but it's his fault for flashing the wrong kernel. Google shouldn't have to pay for his mistakes.
Sent from my Nexus 4
Click to expand...
Click to collapse
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?

duckwizzle said:
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?
Click to expand...
Click to collapse
Most of them are pretty reliable. The one that you linked to, they have their own YouTube channel where people have left pretty positive comments. They seem legit. I'd try them out if you want to be nice and not RMA it.
https://www.youtube.com/user/MobileTechVideos

Yeah its really legit. I got my HD2 Unbricked from there. I flashed a wrong radio and came back with a "RESURRECTED" Bootloader and just flashed a new rom. Its probably different on the Nexus 4.

duckwizzle said:
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?
Click to expand...
Click to collapse
I would still google them to see if there are actually legit. But hope it all works out for you!

Thanks for the replies everyone. I'm going to send it to them to fix it... I'll post back here with the results so other people can search this thread for answers

its bricked. Next time make sure you look at what your flashing.

I got the red light of death, just charged the phone for around 8 hours and it came back.
Sent from my Nexus 4 using xda app-developers app

[Q] How to fix strange battery behavior?

Since last week I am experiencing a really strange behavior of my battery.
Sometimes my phone (in a random app) just vibrates, the screen goes black and then it reboots. After the reboot I have lost 40-50% battery life. Sometimes the phones isn't even able to complete the reboot because it spontaneously has too little power left. See attached screenshots.
Has anybody had similar problems? Or knows a solution?
About my setup: The problem seems to be not rom or kernel related. It occurs no matter what rom or kernel setting I am using. Currently I am running coool boy's 4.3 GE witch KT's kernel (no OC or UV).
Is it possible that the battery is physically damaged? I have NO IDEA...

Experiencing the same problem. I've flashed back to stock and still experiencing this. Phone randomly turning off, not starting, sudden battery drops. Driving me crazy.
Sent from my GT-I9505 using Tapatalk 2

This looks pretty strange 0.o
Consider buying a new recovery
HITTTTTTT THANNNKKKKSSS
galaxy star duos ****rooted*** xda offical app ) )

I've seen the same sort of graph on my old i9000. You're not gonna like this, but it got worse over time, and eventually my battery wouldn't last more than 5 mins. I thought buying a new battery would help, but it didn't. When I sent it in to Samsung they said they would have to replace the entire motherboard...
I think it's got something to do with the motherboard not being able to correctly sense the battery voltage/whatever/%. The phone reboots automatically because it thinks the battery is flat (even though it isn't).
If you're under warranty I suggest sending it in soon... Hopefully it's not the same as what I had heh.

nwsk said:
I've seen the same sort of graph on my old i9000. You're not gonna like this, but it got worse over time, and eventually my battery wouldn't last more than 5 mins. I thought buying a new battery would help, but it didn't. When I sent it in to Samsung they said they would have to replace the entire motherboard...
I think it's got something to do with the motherboard not being able to correctly sense the battery voltage/whatever/%. The phone reboots automatically because it thinks the battery is flat (even though it isn't).
If you're under warranty I suggest sending it in soon... Hopefully it's not the same as what I had heh.
Click to expand...
Click to collapse
Well *#!$
I'll observate it for the next few days and see if it's getting worse...

If your phone is rebooting as opposed to just powering off, then I suspect it is hardware related (motherboard) as already mentioned.
I do hope I'm wrong though.
Maybe try using it for extended periods while plugged into a charger and see what happens. If it doesn't reboot then it may just be the battery.

Right as OP I'm suffering the same exact problem or there abouts. I've flashed back to stock rom, fully charged to 100% drained to 0% back to 100% yet still phone keeps shutting off randomly and the only way it works properly is with the charger plugged in. It's escalated quite badly with now after a few mins of YouTube turning itself off and not rebooting. I've requested a repair by o2 who I'm in contract with and see what will happen. I've heard crap stories about their repairs before taking it to Samsung.

I9500 owner. Had this exact same problem when using older firmware. After updating to the latest one, never had this issue again. Its been two months now, even more.
Try this. Flash the latest available firmware for you phone, not talking about OTA but the downloadable one from any region (whichever is latest for i9505). I guess it may have something to do with the kernel too.
Edit: wait a minute, why is your battery level going up when it isn't even charging in the second screenshot. Middle of the battery timeline. That's weird. I guess you should send the phone back
Sent from my GT-I9500 using xda premium

Its a hardware issue(motherboard).I hope your under warranty.Best of luck .

i have something strange like that also on my device ..
http://forum.xda-developers.com/showthread.php?t=2409284

Thank you guys :good:
In the last few days the problem occurred more often. But now it is just shutting down (no reboot after vibrate) and after plugging it to the charger and restarting it sometimes I haven't lost any battery. Strange!
I fear there is nothing else to do than turning it in (warranty)

E_Cartman said:
Thank you guys :good:
In the last few days the problem occurred more often. But now it is just shutting down (no reboot after vibrate) and after plugging it to the charger and restarting it sometimes I haven't lost any battery. Strange!
I fear there is nothing else to do than turning it in (warranty)
Click to expand...
Click to collapse
Same problem here. It started three days ago and today I'm barely able to use it... I'm still on warraty and I even have insurance, but it's a major inconvenience anyway.

Mines gone in for repair back to my carrier still no movement despite them having it for 2 days now really should have sent it back to Samsung directly. Will keep you guys posted.
Sent from my Nexus 4 using Tapatalk 2

Will send it in tomorrow. Lady on the hotline told me apparently the motherboard is defect and I'll get a new S4. Exchange, no repair. I'm fine with that...
Sent from my GT-I9100 using Tapatalk 4

That's good to hear, just inconvenience but at least you won't have to pay for it (or have the defect materialize a year later or something)

E_Cartman said:
Since last week I am experiencing a really strange behavior of my battery.
Sometimes my phone (in a random app) just vibrates, the screen goes black and then it reboots. After the reboot I have lost 40-50% battery life. Sometimes the phones isn't even able to complete the reboot because it spontaneously has too little power left. See attached screenshots.
Has anybody had similar problems? Or knows a solution?
About my setup: The problem seems to be not rom or kernel related. It occurs no matter what rom or kernel setting I am using. Currently I am running coool boy's 4.3 GE witch KT's kernel (no OC or UV).
Is it possible that the battery is physically damaged? I have NO IDEA...
Click to expand...
Click to collapse
nikzDHD said:
Experiencing the same problem. I've flashed back to stock and still experiencing this. Phone randomly turning off, not starting, sudden battery drops. Driving me crazy.
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
nikzDHD said:
Right as OP I'm suffering the same exact problem or there abouts. I've flashed back to stock rom, fully charged to 100% drained to 0% back to 100% yet still phone keeps shutting off randomly and the only way it works properly is with the charger plugged in. It's escalated quite badly with now after a few mins of YouTube turning itself off and not rebooting. I've requested a repair by o2 who I'm in contract with and see what will happen. I've heard crap stories about their repairs before taking it to Samsung.
Click to expand...
Click to collapse
im4eversmart said:
Its a hardware issue(motherboard).I hope your under warranty.Best of luck .
Click to expand...
Click to collapse
Hey
I am new here.
but i was looking for information becuase my s4 9505i has the same problem
shuts of almost everytime i open apps too quickly or stream youtube or some other high usage apps etc.
battery drops up to 50 percent then back 40 percent then to 0 percent, the fact it that the phone never seems to know where the battery is.
by the way my phone is not rooted and i have done the factory reset a few times.
samsung... hmmm.. they seem to be real hard to talk to on the phone, i have had to call them 4 times already about the s4 i ahve had since june, and they just play me off like i am some kind of idiot etc. and deny that there is possibly any reason for random shutdowns, phone freezing, and now this battery/motherboard issue.
next bit is kinda stupid, the phone has a few internal scratches on it from when i ahve stupidly had the phone next to keys and all that. im sure they are going to try and void my warranty and say i have mistreated the phone...
had many phones before, maybe close to 50 and never, never, never have had to ring up a company to try and complain etc.....
any ideas.
I am in Australia,
I am thinking of trying the CONSUMER AFFAIRS kind of threats, but i have to word it the right way...