[Q] Phone switches off in standby. - Captivate Q&A, Help & Troubleshooting

My captivate shuts itself down randomly on standby. Does anyone else have this problem and is there a known solution?

Are you overclocking your phone? That is one possibility. The other could be a dying battery. Does that happen even if phone is connected to charger? If yes then your battery might be okay.
What rom are you using? Is it a stock or a custom one? If you are running any not so stable version of custom rom then that could be another possibility.

uhm said:
Are you overclocking your phone? That is one possibility. The other could be a dying battery. Does that happen even if phone is connected to charger? If yes then your battery might be okay.
What rom are you using? Is it a stock or a custom one? If you are running any not so stable version of custom rom then that could be another possibility.
Click to expand...
Click to collapse
Firstly, thanks for your reply.. It was happening with the stock rom as well.. I custom flashed a Jelly Bean ROM.. Same result.. Never happened with phone connected to charger and it happens like one in 2-3 days or something..

I'm not sure if all the JB ROMs offer this in the same way, but I'm on SlimBean 2.7 with Semaphore kernel, and it allows you to change the minimum clock speed of the processor when it's in standby and the voltages it uses at different speeds. These are under the main settings->performance. Others have reported that setting the minimum clock speed to 200MHz rather than 100, or slightly upping the voltage when it's in sleep mode, can cure these sleep death issues. I've never had the problem, but search the development forum and you should find other people's recommended settings.

Captivate shuts down in standby
My phone does the same thing. It's a Captivate running Jelly Bean 4.2.1 (Slim-4.2.1.Beta.1-OFFICIAL) on a Semaphore kernel. It works perfectly when it's plugged into a computer through USB. Otherwise, it shuts down, or restarts, every single time it goes into standby, even when it's on a charger. I've tried raising the CPU speed, uninstalling SetCPU, re flashing the ROM, and nothing helps.
Is this a hardware issue, app issues, or does it have to do with the ROM or kernel? I had CyanogenMod 10.0 with a devil kernel running on it previously, and it did the same thing.

Related

[Q] Battery Life on Froyo (Dream/Sapphire)

Simple Poll.
Have you seen a decrease or increase?
Someone can explain this battery drain?
in a lot of roms based on 2.2.1 there is a big battery drain, in some other there isn't.
nagash91 said:
Someone can explain this battery drain?
in a lot of roms based on 2.2.1 there is a big battery drain, in some other there isn't.
Click to expand...
Click to collapse
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
AndDiSa said:
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
Click to expand...
Click to collapse
OK I have done.. but the problem is that when I use it 3 o 4 minutes (for example I install an application using a file explorer, then I read a message and then I come back to home) m battery get 5% lower...
In standby I lose 10% in 6 - 7 hours (I think this is normal).
AndDiSa said:
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
Click to expand...
Click to collapse
I am currently without a computer therefore immune to this USB bug. I flashed CM6.1 to this and the other g1 and both suffered substaintial amounts of battery drain so I nandroid restored back to CSDIv4 and still the lowest frequencies and settings did little to combat the descending digits. So I tried this...
Recalibrated my battery
Flashed SuperWipe.zip
Reboot
Flashed SparksMod's latest
Reboot
Wiped battery stats
Unplugged...reboot
Battery lasted 23 hours the first day never seen anything like it.
Lifes great.
Sent from my HTC Grandaddy via XDA app
Sent from my HTC Grandaddy via XDA app
I'm using TMUS-G1-Froyo CM6 remix..
and I'm using the new radio with +14mb.
The rom flies but the battery go down too fast.
I'm using setCPU with 256 - 528 mhz while screen is on, 122 - 256 mhz while screen off.
If I go to battery use in settings I see
Cell standby 45%
display 28%
phone idle 22%
android system 3%
I don't think is normal... cell standby is the battery use by cell radio..
I wonder if the new radio give a big battery drain..
nagash91 said:
I'm using TMUS-G1-Froyo CM6 remix..
and I'm using the new radio with +14mb.
The rom flies but the battery go down too fast.
I'm using setCPU with 256 - 528 mhz while screen is on, 122 - 256 mhz while screen off.
If I go to battery use in settings I see
Cell standby 45%
display 28%
phone idle 22%
android system 3%
I don't think is normal... cell standby is the battery use by cell radio..
I wonder if the new radio give a big battery drain..
Click to expand...
Click to collapse
I got real excited when I heard about the new radio and hboot even thought that its exclusion was the source of the the battery issues. Haven't been able to try it as I'm without a up-to-date PC at the moment.
It would be real nice if I could find a seasoned dev who understands battery consumption. I thought the kernal was the main culprit but I've tried two different roms with the same kernal and one has notably better battery life than the other. So confusing.
Sent from my HTC Grandaddy via XDA app
I can't use my phone with this battery drain...
I will come back to official android OTA-AOSP 1.6.. with +14mb.
So I'll test if this kernel with 14mb is a cause of battery drain.
PS: I'm not a lover of rom customizations.. I think the official roms are the best.
The other are all too heavy. I'm not a fan of cm kernel, that is too heavy for g1.
I would see an official OTA 2.2 without customizations, so every one could customize as he want, and if he want.
PS: OK I flashed AOSP 1.6 using ezBiff_kernel to have 15mb (cause I have new radio and spl, so I can flash roms only using this kernel).
Result: my battery life is similar to froyo 2.2 roms... so the problem is:
1) Kernel? (ezBiff_kernel is based on cyanomod kernel... ... ... heavy as death)
2) New radio/spl?
3) My battery (I don't think so.. it's new battery. I buy it 2 weeks ago and in the beginning it works so well.. but then I flashed new radio/spl and new kernel for 15mb..)
nagash91 said:
1) Kernel? (ezBiff_kernel is based on cyanomod kernel... ... ... heavy as death)
Click to expand...
Click to collapse
Come now.. the cm pershoot kernels are super optimized so they don't collapse under the heavy as death rom that is usually on top of it..
I get mixed results with that kernel between testing and feedback.
A test phone can idle on wifi+2g for days on the stock g1 battery even after a usb unplug.. but on more common use with syncing services its not performing as well as I'd like..
Some of it is fixed with less swap/compcache or changing clock speeds 122/480 for most the speed but lower voltage levels. Also the interactive governor may work better.. I'm testing these ideas if results are good my next kernels defaults will use them.
Cm/pershoot have some interesting new power management code from other htc devices.. So hopefully soon all will be better. (I merged most of it to my kernel but there are some loose ends.. works well untill the phone locks up.. so no public release yet)
ezterry said:
Come now.. the cm pershoot kernels are super optimized so they don't collapse under the heavy as death rom that is usually on top of it..
I get mixed results with that kernel between testing and feedback.
A test phone can idle on wifi+2g for days on the stock g1 battery even after a usb unplug.. but on more common use with syncing services its not performing as well as I'd like..
Some of it is fixed with less swap/compcache or changing clock speeds 122/480 for most the speed but lower voltage levels. Also the interactive governor may work better.. I'm testing these ideas if results are good my next kernels defaults will use them.
Click to expand...
Click to collapse
Ok sorry I talk without knowledge. I really don't know the effect of the cm kernel. I only know that all roms based on cm release, with cm kernel, are so heavy and slow.
I like your rom (2.2.1 AOSP) and I love your new way to get 14mb.
But I have this orrible problem. My phone has a lot of battery drain when I use it. With screen off, no problems.
I have never used swap or compcache in this days, and I also try different clock speeds (not over 528mhz).
The result is that when I unlock my phone, I go to settings, I see for example 95% battery. Ok, I return to home, I open a message, I return to home, I open contacts and I scroll some contacts without make calls.
Then I come back to battery settings and I see that is 92-93%..
in 2 minutes of soft use.. I think this is impossible. If I open stupids 2D games... ahah in 5-10 minutes my battery lose 10 - 20%.
I remember 1 year ago, with 1.6 (no cyanomod) my battery was good.
Now it isn't (I have a new battery).
Today I flashed aosp 1.6 with your kernel for 14mb (I have new radio&spl) but nothing... I lose a lot of battery percent as in froyo.
So I think problem is or battery calibration, or something to wipe, or cm kernel, or new radio&spl + your new kernel...
Now I'm recalibrating battery (is at 1% from 2 hours, I'm not using it.. ) then I will recharge for 8 - 9 hours and then wipe battery state, but I have done this process a lot of time without a benefit.
I'll try to remove the new radio+spl (so also using standard kernel) if my battery continue to lose percents so fast.
I'll keep you update on my "story".
PS: Sorry for my bad english!! XD
OK.. after a day of low discharging and a night of 8 hour of recharging, I wiped battery states, I wiped data-cache-ext ecc... I flashed aosp 1.6 and ezbiff kernel..
"battery drain" continue...
I will try tomorrow to reflash death-spl and old radio..
BTW, is normal for hours battery 4v at 90%?
On the back of the battery sais 3.7v... I thought 3.7 was the voltage for 100%
Update
I know this thread is a little old, but I ran into this problem as well. What I found was that the official US radio (2.22.23.02) used considerably more battery than the international one (2.22.19.26i). The other thing I noticed is that switching to "use 2G networks only" in mobile networks settings and disabling data over mobile drastically improved battery life.
I also noticed that wifi used a fair bit of juice so my recommendation is to disable wifi if you're going to be on the go for a bit, and disable data/3g if you're just going to be hanging out in the local webcafe, your/a friend's house, or some other location with wifi access for a while.
If you wanted to be ambitious and cared enough you could write a script to use as a shortcut on the home screen to do the swap automatically (detect which setting(s) are enabled and swap them to the opposite).
With those changes, you should get much better battery life. My thoughts on different Froyo flavors is that possibly different builds have different settings by default. Cyanogen comes with data and 3g enabled by default so this will quickly suck out your battery if you're running your 3g, 2g and wifi antennas all at once.
The stock build (1.6) got about the same battery life as I'm getting now with those settings applied. With either build, having all antennas on all the time will drain your battery very rapidly. Being a little more cognizant of the settings (perhaps you also had it set to 2g only on the stock build) you're using will significantly improve your battery life. And when I say significantly, I mean night and day (but the antenna version definitely does also make a difference... at least in my case).

[Q] Sleep/Charge of Death

I been wondering if the phone never had sleep/charge of death before can a kernel and/or ROM be the culprit to it? I been trying to look more into it and haven't found a definite answer to it so I ask you guys what is causing it. I've tried different kernels and ROMs and some do it other don't is there anyway to just know? Or a good way to narrow it down?
I was able to track mine down to a kernel that supported Overclocking. Once I switched to a ROM that had a kernel that wasn't OC supported (older version of same ROM) my charging death went away. I think it has to do with the OC settings, the idle clock speed is too slow, but no matter what settings I used I got sleeping death every other night until I swapped for the other version.
Sent from my Captivate running GR-12
Only time I have encountered the Sleep/Charge of death was when I was OCing the phone and UVing it also. Having too much of a variance in the UV was my problem. Wants I started to UV the same amount across the board or close to it my problems were solved. For instance the most I UV is 75 and the least is 25. if you had a gap like 150 to 0 that could be what is causing your problem. At least that is what I noticed for myself. Now I am perfectly fine for over a month.
The phone boots up to 1/2 way through the kernel when charging in off mode... IBL, PBL, SBL, Params, Kernel... If it hangs, then it's likely hung at a custom kernel.
If the ROM craps out it soft reboots and/or goes into a boot loop. I don't think that a ROM can cause your phone to randomly shut down.

Team ICSSGS RC4 problems, looking for solutions

I´ve noticed a few bugs, problems in this new version of ICS. If anyone knows how to solve them I would appreciate your advice
So, here is what´s bugging me:
1. Screen sometimes go greenish for a second or two when there is a lot of apps running and when I quickly turn off and turn on the screen (it happens when the screen goes on, that moment)
2. Overclocking seems very unstable!! ..when I OC my phone (with NStools) and do some things..after a while, it freezes and reboots. On RC3.1 version I could overclock to 1.46GHz and play games and it was very stable!
(I think they changed voltage and because of that it´s unstable, but I´m not sure)
3. When system reboots (after crash), it reboots in clock work mode -.-" ..why can´t it reboot normally, into system?
4. It´s not really a problem but, does anyone know how to remove unnecessary home screens or add them back? Is it possible?
5. .apk files can´t be sent trough bluetooth .. (message: This Bluetooth device or computer cannot process files of this type. )
Other than that I would say this version is almost perfect, flash works in browser, effects in camera, USB mass storage ..works very well.
I was on Doc´s ICS teamhackungs based rom before this one (and after RC3.1 )..and I noticed that battery life was terrible even with juice saver apps running.
I hope this one is better.
Actually RC4 has been pulled because of a Wifi issue
I flashed it last night before it was pulled, I flashed over Onecosmics 2.11 no wipe, and my wifi its working normal.
sokre988 said:
I´ve noticed a few bugs, problems in this new version of ICS. If anyone knows how to solve them I would appreciate your advice
So, here is what´s bugging me:
1. Screen sometimes go greenish for a second or two when there is a lot of apps running and when I quickly turn off and turn on the screen (it happens when the screen goes on, that moment)
Click to expand...
Click to collapse
Mine does it too
sokre988 said:
2. Overclocking seems very unstable!! ..when I OC my phone (with NStools) and do some things..after a while, it freezes and reboots. On RC3.1 version I could overclock to 1.46GHz and play games and it was very stable!
(I think they changed voltage and because of that it´s unstable, but I´m not sure)
Click to expand...
Click to collapse
no OC here
sokre988 said:
3. When system reboots (after crash), it reboots in clock work mode -.-" ..why can´t it reboot normally, into system?
Click to expand...
Click to collapse
No crashes yet
sokre988 said:
4. It´s not really a problem but, does anyone know how to remove unnecessary home screens or add them back? Is it possible?
Click to expand...
Click to collapse
I don't think it is possible since it is ASOP rom
sokre988 said:
5. .apk files can´t be sent trough bluetooth .. (message: This Bluetooth device or computer cannot process files of this type. )
Click to expand...
Click to collapse
I will try that later.
sokre988 said:
Other than that I would say this version is almost perfect, flash works in browser, effects in camera, USB mass storage ..works very well.
I was on Doc´s ICS teamhackungs based rom before this one (and after RC3.1 )..and I noticed that battery life was terrible even with juice saver apps running.
I hope this one is better.
Click to expand...
Click to collapse
It is a great rom, I hope they can fix those minor issues.
Battery life for me has been just OK on 2.11, I have to give RC4 the 3 charge cycles before any judgement.
I've just noticed that battery life was reduced constantly in last 3 days, now battery doesn't last 12 hours, but it's the first time that happens!
Giuku said:
I've just noticed that battery life was reduced constantly in last 3 days, now battery doesn't last 12 hours, but it's the first time that happens!
Click to expand...
Click to collapse
Battery degradation due to age ?
ricarducho said:
Actually RC4 has been pulled because of a Wifi issue
I flashed it last night before it was pulled, I flashed over Onecosmics 2.11 no wipe, and my wifi its working normal.
Mine does it too
no OC here
No crashes yet
I don't think it is possible since it is ASOP rom
I will try that later.
It is a great rom, I hope they can fix those minor issues.
Battery life for me has been just OK on 2.11, I have to give RC4 the 3 charge cycles before any judgement.
Click to expand...
Click to collapse
Yes, so did I ..just before they pulled I downloaded the rom...I was on Doc´s ICS..but I flashed with Odin JVT 2.3.5. GB ..rooted with CF-root and then in CWM flashed RC4 ..my wi-fi was having problems but when I updated WiFix manager it was ok then.
Yea, I couldn´t agree more, if they fix those issues it could be it..the final version (without any bugs). Lets hope they do it soon so we don´t have to wait too long
btw. I was thinking, could we solve these or at least some this issues by flashing another kernel??
@Giuku :I´ve noticed that too..even though I´m not OC now it still drains a lot..or my battery become weak (It´s 1year old) . But that is not without a reason..I did put her to her limits (and my phone) by playing games so much that my smartphone reached max temperature of 60°C and then cooling it in 1min to 30°C and less.

[Q] Phone Shuts Down when Chargıng after Flashıng CM9 & CM10

I purchased my Captivate in July 2010, used it for a year without rooting, flashing, etc. Had no problems with random shut off.
After moving overseas, I had to flash a ROM, long story. Used Serendepity ROM for a year with no problems.
At the end of July this year I flashed CM9. At this point, I begin to have problems with the phone shutting off while charging. This did not happen except when charging. In order to turn the phone back on I have to disconnect it from the power cable. This happened rather frequently at first, but gradually began to happen every night.
A couple of days ago I flashed CM10 and it still happens. Two days ago I downloaded SetCPU and set the minimum speed to 200 Mhz when charging. However, this did not solve the problem.
Any ideas on a fix?
Thank you in advance for any help.
jchadana said:
I purchased my Captivate in July 2010, used it for a year without rooting, flashing, etc. Had no problems with random shut off.
After moving overseas, I had to flash a ROM, long story. Used Serendepity ROM for a year with no problems.
At the end of July this year I flashed CM9. At this point, I begin to have problems with the phone shutting off while charging. This did not happen except when charging. In order to turn the phone back on I have to disconnect it from the power cable. This happened rather frequently at first, but gradually began to happen every night.
A couple of days ago I flashed CM10 and it still happens. Two days ago I downloaded SetCPU and set the minimum speed to 200 Mhz when charging. However, this did not solve the problem.
Any ideas on a fix?
Thank you in advance for any help.
Click to expand...
Click to collapse
Did you make any mods or change any settings?
Also, did you try using a different kernel? (Devil / Semaphore)
You might also flash back to Serendipity and see if the problem persists. If it doesn't then of course it's an issue with CM but if it continues I would say its a hardware problem or potentially a bad charger. Personally I've never used either CM9 or 10 but nearly every rom I've used is based off of them and I've never had this issue. So unless you've done something weird with the settings as BWolf suggested then I would lean towards hardware.
Thank you for the suggestions. I've flashed a couple of kernels (Devil and Semaphore) and the problem continues. I'll test the battery and charger next.
I tried a different battery and charger as well as a couple of other ROMs, with no change. The phone still shut off at night. So, I flashed back to stock 2.1 and the phone did not shut off. I then tried CM10.1 again, but the phone shut off again last night.
So, I've determined that it's not a hardware issue, but so far all Android 4.x ROMs I've flashed have resulted in the phone shutting down at night while charging.
Anyone have any ideas or suggestions?
jchadana said:
I tried a different battery and charger as well as a couple of other ROMs, with no change. The phone still shut off at night. So, I flashed back to stock 2.1 and the phone did not shut off. I then tried CM10.1 again, but the phone shut off again last night.
So, I've determined that it's not a hardware issue, but so far all Android 4.x ROMs I've flashed have resulted in the phone shutting down at night while charging.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
co-ask.
i got the same problem with cm9 and cm10.
thanks in advance.
jchadana said:
I tried a different battery and charger as well as a couple of other ROMs, with no change. The phone still shut off at night. So, I flashed back to stock 2.1 and the phone did not shut off. I then tried CM10.1 again, but the phone shut off again last night.
So, I've determined that it's not a hardware issue, but so far all Android 4.x ROMs I've flashed have resulted in the phone shutting down at night while charging.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
yqren said:
co-ask.
i got the same problem with cm9 and cm10.
thanks in advance.
Click to expand...
Click to collapse
Try upping your minimum voltage to 200Mhz.
BWolf56 said:
Try upping your minimum voltage to 200Mhz.
Click to expand...
Click to collapse
tried it, but it doesn't work.
thanks
Same problem here. CM9 had been doing it fairly regularly. I wiped everything and did a fresh CM10 install before bed without installing any other apps or changing settings and it shut off over night. I'm flashing back to stock now too confirm whether that fixes the issue

[Q] Cynogenmod Shuts Down after Installation

Heys Guys Im having an issue with my Captivate, its was working fine for the past week. It started giving me problems like battery temps too high, cant charge, had to charge it manually, removing battery & charging it all night. All this happened when im with stock rom latest with leaked 2.3.5
& i did unlock this with changing the 01 digit to 00 in efs file.
From the past 2 days im trying to install CM10,9, 10.1..... after installation it shuts down itself. Not able to use it.
Is there any way around to make this work. If pics are needed i can provide that too.
Thanks
No reply... :/
Some one should have had an issue.
vivek90 said:
Heys Guys Im having an issue with my Captivate, its was working fine for the past week. It started giving me problems like battery temps too high, cant charge, had to charge it manually, removing battery & charging it all night. All this happened when im with stock rom latest with leaked 2.3.5
& i did unlock this with changing the 01 digit to 00 in efs file.
From the past 2 days im trying to install CM10,9, 10.1..... after installation it shuts down itself. Not able to use it.
Is there any way around to make this work. If pics are needed i can provide that too.
Thanks
Click to expand...
Click to collapse
When/how does it happen?
What are the changes/mods you made?
Did you restore anything?
Did you try different kernel settings?
Did you try flashing a different kernel (like Semaphore?) or flashing a different ROM?
I could be asking more questions but really, I dunno what causes it, I can only guess. Also a search in the CM10.1 thread might give you an answer to your SoD <-- Should've been your first step*
BWolf56 said:
When/how does it happen?
What are the changes/mods you made?
Did you restore anything?
Did you try different kernel settings?
Did you try flashing a different kernel (like Semaphore?) or flashing a different ROM?
I could be asking more questions but really, I dunno what causes it, I can only guess. Also a search in the CM10.1 thread might give you an answer to your SoD <-- Should've been your first step*
Click to expand...
Click to collapse
It just happened, battery temp too high errors, thought flashing CM9 would solve this, was bored of Stock Gingerbread, flashed corn kernel & flashed cm9 rom. I did mod anything else. That all
vivek90 said:
It just happened, battery temp too high errors, thought flashing CM9 would solve this, was bored of Stock Gingerbread, flashed corn kernel & flashed cm9 rom. I did mod anything else. That all
Click to expand...
Click to collapse
Battery temp to high is a big problem. Did you overcloak? Have you running bunch of stuff at the same time?
When it shuts down, does it reboot by itself or you have to do it manually?
Sent from my SGH-I747 using xda app-developers app
Sounds like Battery health status does not equal healthy. That forces an immediate shutdown, whether due to temperature or excessive internal resistance. That's because once a Li ion battery reaches critical temperature, it combusts and destroys your phone, burns you and anything around it, etc.
GET ANOTHER BATTERY ASAP.
Stop trying to circumvent high temperature shut down.
.........
BWolf56 said:
Battery temp to high is a big problem. Did you overcloak? Have you running bunch of stuff at the same time?
When it shuts down, does it reboot by itself or you have to do it manually?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Recently i bought a new battery, original samsung make, it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high". No overclocking here, just used to call, receive & wifi hotspot. Currently i charge battery in a battery charger & use it in phone.
U pointed out something right, sometimes screen just goes blank, i have to manually switch it on.
laughingT said:
Sounds like Battery health status does not equal healthy. That forces an immediate shutdown, whether due to temperature or excessive internal resistance. That's because once a Li ion battery reaches critical temperature, it combusts and destroys your phone, burns you and anything around it, etc.
GET ANOTHER BATTERY ASAP.
Stop trying to circumvent high temperature shut down..........
Click to expand...
Click to collapse
I bought a new battery & it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high".
But im not able to under stand, why is Cynogenmod shuts down itself after installation, can i just stop shutting down ?
vivek90 said:
Recently i bought a new battery, original samsung make, it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high". No overclocking here, just used to call, receive & wifi hotspot. Currently i charge battery in a battery charger & use it in phone.
U pointed out something right, sometimes screen just goes blank, i have to manually switch it on.
I bought a new battery & it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high".
But im not able to under stand, why is Cynogenmod shuts down itself after installation, can i just stop shutting down ?
Click to expand...
Click to collapse
I think it's not CM related but hardware related. Does this happen when not using the wifi hotspot too?
I'm thinking your battery is bad (even if new), charger is bad, connection is bad (maybe from water/humidity) or that your usb port is bad. No easy way of finding it other than testing.
BWolf56 said:
I think it's not CM related but hardware related. Does this happen when not using the wifi hotspot too?
I'm thinking your battery is bad (even if new), charger is bad, connection is bad (maybe from water/humidity) or that your usb port is bad. No easy way of finding it other than testing.
Click to expand...
Click to collapse
May be yes, the phone some times just goes blank, i have to manually switch ON. The same battery works well in my frnds phone quite well.
Port dont know, i can copy files no errors even now when i plug it in on stock gingerbread the battery doesnt charge but can copy files as before.
Since the batt works well in other phone, a couple of ideas. Perhaps silly to ask, but just checking:
did you wipe battery stats in cwm after flashing?
did you clean the phone's battery terminals with a bit of alcohol?
what's the battery health,temperature and voltage history look like, if you can get it. you can log it with battery monitor widget or similar app. set to short 1 minute interval for testing.
.........

Categories

Resources