Database Users

[Q]Odd problem

When my battery dies overnight while I'm not using it and I attempt to turn my Xoom on after charging it for a about 30 mins, it never makes it past the Dual Core Technology screen (doesn't even make it to the pulsing logo).
So I have to reflash my ROM and then it boots fine. Anyone know why this might be?
Running Tiamat 2.2.2

Yeah, that is odd! I'm not sure why you're getting this issue as I don't but just thought I'd chip in with a little tip. You should try to not let your Xoom lose all of it's power, the lithium ion batteries don't like it. If possible try to charge the Xoom before it reaches zero percent battery.
As to your issue though, I'm stumped. Did this happen with stock?

Never tried with stock. I used stock for about 30 mins.
Sent from my Xoom using xda premium

i kknow that a number of people were having a similar problem with bootloader version 1.45 on the 4g upgraded Xoom's. The 1.5 upgrade seemed to solve the problem.
Do you you know what version bootloader you have?

Well its not my battery that is dying and causing it to not boot. I'm thinking its either the kernel (using Rouge's 1.4.1) or my undervolting because it just crashed on me and won't boot anymore.

REHolt218 said:
i kknow that a number of people were having a similar problem with bootloader version 1.45 on the 4g upgraded Xoom's. The 1.5 upgrade seemed to solve the problem.
Do you you know what version bootloader you have?
Click to expand...
Click to collapse
How do you find out?

Deadly Issue ;( !! (UPDATE: occurs with the stock kernel)

Hello everyone...
I have 2 issues with my Transformer
the first one is that whenever i leave my Transformer for couple hours it shuts down !! doesn't occur when charging but it does when it's not.. even when the battery is around 80% !! i had this problem with ALL kernels except the stock kernel which i don't wanna use !! also had this problem for around 2 months...
the second one happened today when i left my Transformer "Charged" at 100%.. and after couple of hours i found it shut down but when i powered it on again i found the battery 27% !!
i went to the battery stats and found that battery was decreasing slowly and there was a gap (which means that it turned off) and after the gap it shows the battery low !! it happened within 6 hours !!
Please help me if you can... !! I'm using Revolver ROM 3.9.5 and "Blades Kernel 3" that comes in the Revolver Parts...
UPDATE : The problem occurs with the stock kernel !!

This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?

The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.

Cernunnoz said:
This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?
Click to expand...
Click to collapse
I never heard of this app... Just like i said it doesn't happen with the stock kernel !!
But the reason I'm using other kernels is because i wanna Overclock !!

a.mcdear said:
The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.
Click to expand...
Click to collapse
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !

sounds like a silly question but i have seen it alot. Are you charging through a computer(USB) or wall?

It could be related to setCPU and the according profiles. Just recently I saw that my profiles were messed up after updating ROM and kernel. Might be worth a shot.

Reinstall stock kernel Issue #1 fixed.
Issue 2 sounds like charger shut off and left TF on not charging.

You've pretty much explained to yourself why the thing is shutting down.. It works fine on the stock kernel but not one that is letting you overclock.. Sounds to me like you are either overclocking more than it can handle or undervolting to much or both.
I can almost bet that its not shutting down completely and its just going into a state that the screen is off but the OS is hung up, so its not responding to you turning the screen on.. This would explain why the battery seems to be dieing when its sitting idle.
Not sure about it dieing while its plugged in other than maybe a fluke.

I don't wanna use the stock kernel.. it's really slow !!
and i over clock to 1.4 ghz only since i can't overclock more than that because it restarts itself endlessly if i overclocked more than 1.4 ghz !! i undervolted about -25 or -50.. not much !!
Yes i charge it on a wall or anything but NOT on my computer...
How can i change profiles in setcpu ??

xMini said:
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !
Click to expand...
Click to collapse
No no you misunderstood! DONT let the battery hit 0.

First, you need to use more exclamation points !!!!
sounds like you are suffering from deep sleep issues. What rom are you running? also, have you tried running a custom kernel and not overclock it? You have several variables that can be influencing your issues, start isolating what may be causing your problems. the kernel seems the must likely of culprits, I would clear the overclock and install setcpu and run it for a but and see if you can replicate your issue.
Sent from my GT-I9000 using XDA App

Just try the non stock kernel, oc it but dont uv it, not all devices can handle uv, even if it is only a little bit. Even take it back too 1000mhz and try to increase the uv and oc by little bits at a time to see exactly what your transformer can handle. I think its the uv thats causing the problems. Experiment a bit and youll find the sweet spot.

I'm using Revolver ROM and i mentioned that...
I've never undervolted till yestersay.. maybe it caused the second problem
I set the clock speed at 1ghz and i'm waiting to see if anything changes..

Yeah... the problem still occurs even after setting the clock speed at 1ghz and default voltage !! using clemsyn kernel ver 22...

Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk

colonel187 said:
Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I'm guessing my device is bad and it's Asus' problem ! i tried setting the clock speed at normal 1Ghz but the problem still occurs !! the reason i overclock is that because with the stock kernel i get slower web browsing and slower flash playback and slower overall performance!! however I'm back on the stock kernel to check out if the problem is gone or not...
I doubted my device couple months ago... because I've seen everyone overclock their devices at 1.6 GHz Without any issues !! but when i try to overclock a little bit more than 1.4 GHz it restarts itself endlessly !!

Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App

ropaisoft said:
Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
What do you exactly mean by "for now" ??
and how can i even send it to ASUS ??! i don't live in the USA

xMini said:
I'm guessing my device is bad and it's Asus' problem !!!
Click to expand...
Click to collapse
You stated in an earlier post that the problem does not show up in the stock ASUS setup, but only with a custom ROM and Kernel. How does that make it ASUS' problem. If you buy a car that says it runs on 87 octane fuel and you put 100% nitro methane in the tank and it blows up it is not the manufacturers fault.

[Q] Freezing issues

Hi i have flashed many nand roms to my hd2 the end result is always the same. phone works fine until i try to play games anywhere between 30s to 10 min and the phone freezes up and is unresponsive. only way to fix is to remove battery. any ideas on what this is why it happens and how to fix it.

what is your ROM? what's your magldr version? what is your HTC HD2 type EU or TMOUS? What is the name of your games? i need more information sir..

psypix said:
Hi i have flashed many nand roms to my hd2 the end result is always the same. phone works fine until i try to play games anywhere between 30s to 10 min and the phone freezes up and is unresponsive. only way to fix is to remove battery. any ideas on what this is why it happens and how to fix it.
Click to expand...
Click to collapse
I'd hazard a guess at it being an overheating problem. Do you overclock on the ROMs you use? Does the phone get extremely hot? If yes to these, try not overclocking and see if it works.

magldr version is 1.13 and it a tmous hd2 running nexus h2 ics 4.0.4 cm9 hwa v1.2 by tytung. not overclocking running at the standard max of 998Mhz min somewhere around 200. the only option i have used is in the performance settings under memory management i ticked the kenel samepage merging which seems to have reduced the amout of freezing i am experiencing. tried playing the game called drag racing think is by creative mobile. phone on its own works great but even playing angry birds anywhere between 5 to 15min it freezes. noticed yesterday my battery was low so the charge light was flashing and when the screen frooze the light still continued to blink but the phone was totally unresponsive. Any ideas

Nigeldg said:
I'd hazard a guess at it being an overheating problem. Do you overclock on the ROMs you use? Does the phone get extremely hot? If yes to these, try not overclocking and see if it works.
Click to expand...
Click to collapse
not overclocking running at the standard max of 998Mhz min somewhere around 200
Click to expand...
Click to collapse
I have similar problem. But not so often. He is not overclocking, neither do I.
I also use zRam 26%.
This often happens when the phone is under load, so I think that maybe this is due to lack of memory. The phone heats up when the screen freezes.
Any tips?

OK, this might sound stupid but try putting the phone in the fridge for a while to cool it down, then play. Obviously don't do it for too long, it is after all a phone, but I read somewhere that this had helped someone with overheating. I doubt it is a RAM issue cos that wouldn't cause a freeze, it would probably result in the launcher being killed to free up RAM.
Sent from my NexusHD2 using XDA

not sure putting it in the fridge every time want to play will be quite the fix i am looking for. Might prove the theory that the phone is overheating but then there must be a setting somewhere that can be envoked to get this to stop happening

psypix said:
not sure putting it in the fridge every time want to play will be quite the fix i am looking for. Might prove the theory that the phone is overheating but then there must be a setting somewhere that can be envoked to get this to stop happening
Click to expand...
Click to collapse
Yeah I know it isn't a practical solution, I just meant it to test my overheating theory. Perhaps there is a fix, but to be honest if you aren't OCing then I really don't know why it should be heating up so much. Sure, mine gets warm but even when I've played for around an hour on Contract Killer: Zombies (fairly graphically intense and a very fun game) it doesn't shut down or anything. There IS a hardware fix but it's quite dangerous and requires a lot of expertise and the right equipment, neither of which I have Should you wish to try it, just make sure you're very careful

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

Please help.....my phone keeps rebooting

HI EVERYBODY
I HAVE A PROBLEM WITH MY GALAXY S5 G900F
IT KEEPS REBOOTING SO I TRIED A SOFTWARE AND IT DIDN'T WORK
SO I FLASHED A CUSTOM ROM THEN IT WORKED FOR A WEEK AND THE PROBLEM SHOWED UP AGAIN
SO NOW EVERYTIME I FLASH A CUSTOM ROM THE PHONE WORKS FOR COUPLE OF DAYS AND THEN THE SAME PROBLEM KEEPS COMING BACK
..
..
..
ANY IDEAS

Hi there,
Can you please define what "a software" means? What custom ROM did you install? Have you tried reflashing stock ROM and try isolating the problem (so, don't install you're usually apps, test them one by one) whether it is an app caused issue or hardware (happens regardless of app/ROM install)? Have you considered getting a new battery? Apologies for the vague questions but the level of detail provided is not sufficient for us users to effectively help.
Regards, Saber

HEY.....thanks for reply
Saber said:
Hi there,
Can you please define what "a software" means? What custom ROM did you install? Have you tried reflashing stock ROM and try isolating the problem (so, don't install you're usually apps, test them one by one) whether it is an app caused issue or hardware (happens regardless of app/ROM install)? Have you considered getting a new battery? Apologies for the vague questions but the level of detail provided is not sufficient for us users to effectively help.
Regards, Saber
Click to expand...
Click to collapse
A SOFTWARE:Installing firmware by odin :good:
I tried lots of custom rom like lineage os 14.1 , cm 13 and flyme os
The only apps i use are social media apps, nothing needs root access or may be harmful
Yes i tried a new battery and it didn't work
Sorry for bad English

tareq at&t said:
A SOFTWARE:Installing firmware by odin :good:
I tried lots of custom rom like lineage os 14.1 , cm 13 and flyme os
The only apps i use are social media apps, nothing needs root access or may be harmful
Yes i tried a new battery and it didn't work
Sorry for bad English
Click to expand...
Click to collapse
i think we have the same problem, does your phone turn off vibrate twice then reboots?

rusherrrx said:
i think we have the same problem, does your phone turn off vibrate twice then reboots?
Click to expand...
Click to collapse
Yes ?

tareq at&t said:
Yes
Click to expand...
Click to collapse
You mentioned changing the battery? Is it a Samsung original battery replacement? Cos I think mine was caused by overheating up to 70C and rebooting. I'm planning to under clock in a while.

rusherrrx said:
You mentioned changing the battery? Is it a Samsung original battery replacement? Cos I think mine was caused by overheating up to 70C and rebooting. I'm planning to under clock in a while.
Click to expand...
Click to collapse
Nope, it's not original but i'll try that
But why it takes couple of days to brick even when the phone is not in use
Again sorry for bad English

tareq at&t said:
Nope, it's not original but i'll try that
But why it takes couple of days to brick even when the phone is not in use
Again sorry for bad English
Click to expand...
Click to collapse
I dont think it's a battery issue

tareq at&t said:
I dont think it's a battery issue
Click to expand...
Click to collapse
me either, but since i can conclude that it is a battery issue since, i was on 6.0.1 stock rom and still experience this issues. now i am on custom rom, still do. does your phone get really hot? or it just really reboot randomly?

rusherrrx said:
me either, but since i can conclude that it is a battery issue since, i was on 6.0.1 stock rom and still experience this issues. now i am on custom rom, still do. does your phone get really hot? or it just really reboot randomly?
Click to expand...
Click to collapse
Yes it gets really hot ..... but without making the phone restart
Oh...I didn't mention that it restarts continuously not in random times

tareq at&t said:
Yes it gets really hot ..... but without making the phone restart
Oh...I didn't mention that it restarts continuously not in random times
Click to expand...
Click to collapse
hmm same issue we are having. what are your thoughts?

rusherrrx said:
hmm same issue we are having. what are your thoughts?
Click to expand...
Click to collapse
I think it may be a hardware issue
But what parts could force the system to restart

tareq at&t said:
I think it may be a hardware issue
But what parts could force the system to restart
Click to expand...
Click to collapse
is your phone also not turning on for some reason? even though u keep on pressing the power button?

rusherrrx said:
is your phone also not turning on for some reason? even though u keep on pressing the power button?
Click to expand...
Click to collapse
Nope

tareq at&t said:
Nope
Click to expand...
Click to collapse
I think mine has its sweet spot where everything works flawlessly. But then till the next reboot or so. It acts dumb again.

rusherrrx said:
I think mine has its sweet spot where everything works flawlessly. But then till the next reboot or so. It acts dumb again.
Click to expand...
Click to collapse
Are you using xpoasde installer?

tareq at&t said:
Are you using xpoasde installer?
Click to expand...
Click to collapse
nope im using the nemesis n7 rom all stock, didnt modify as soon as i installed it.

tareq at&t said:
Are you using xpoasde installer?
Click to expand...
Click to collapse
i think the main problem here is the part that detect the battery percentage, or atleast the battery itself. Since i plugged in my phone then it hanged so i had to pull out the battery then put it back on while still plugged in, then my batter percentage increased from 24% to 45% by just doing that.
thoughts?

rusherrrx said:
i think the main problem here is the part that detect the battery percentage, or atleast the battery itself. Since i plugged in my phone then it hanged so i had to pull out the battery then put it back on while still plugged in, then my batter percentage increased from 24% to 45% by just doing that.
thoughts?
Click to expand...
Click to collapse
I tried a new battery and that didn't work so i don't think that it is a battery issue
But if the part that detect the battery percentage is broken,that's mean we have to replace the entire motherboard

tareq at&t said:
I tried a new battery and that didn't work so i don't think that it is a battery issue
But if the part that detect the battery percentage is broken,that's mean we have to replace the entire motherboard
Click to expand...
Click to collapse
yep too bad. havent done replacing the battery yet tho. plans on getting a new phone?