Hi all !
I have a big problem and I need help ,four days ago I was listening music on my arc and power amp told me that my licence expired ,when I was looking in setting I realised that the time and date was from the day before at 6 am and all my calls made or recived since that date were missing .I was on firmware 62 ,I flashed 42 and the clock is o.k now but battery drains in 4h ,flashed 58 (root) same problem in service tests menu battery o.k. internal clock o.k. everything o.k. I tried in recovery wipe cache ,dalvin ,sd ,system everything I tried without sd because I feel some heat above the sd slot all the time even when idle .I need help ,It s hardware or something that I don t know ,please help
Thx in advance !
Flash a complete stock firmware without mods and wipe data and see what happens.
If it still happens, I'd buy a new battery and test it.
Sent from my iPad 2 using Tapatalk
done LT18i_4.0.2.A.0.58(2.3.4)_HK ,same problem
From your post I guess you have a LT15, if so, flash that firmware.
If the fw is right, a new battery might fix it.
Sent from my iPad 2 using Tapatalk
Related
Hi Guys,
I have a very weird issue with my play.
It gets switch off automatically at 30-25% battery remaining.
I am not able to use my battery for even 1 single day.
This issue got started after I flashed XPACman-zeus-v3 ROM.
After that i tried ICS roms and also GB roms but same issue going on.
Please help me out with this.
Thanks.
You shoulds calibrate the battery see if that helps
Sent from my R800i using xda app-developers app
hardikgala said:
Hi Guys,
I have a very weird issue with my play.
It gets switch off automatically at 30-25% battery remaining.
I am not able to use my battery for even 1 single day.
This issue got started after I flashed XPACman-zeus-v3 ROM.
After that i tried ICS roms and also GB roms but same issue going on.
Please help me out with this.
Thanks.
Click to expand...
Click to collapse
Root (if not already) & download Battery Calibration from the market.
Follow on screen directions. If then the problems is still present, flash stock ftf files. It shouldn't have to come to that but just in case...
If you have CWM recovery boot into it and go to advanced then wipe battery stats
Sent from my GBTweaked v7.1 r800x using Tapatalk 2
HI Guys
I'm an old iOS user but switched to android 2 months ago with a wonderful Note 2 International running android 4.1.1
after one month of use I decided to root my device for VPN service and custom ROM benefits
Everything went fine. First rooted with odin 3.07, then decided as most of users recommended to flash ARHD 11.2
After using my device for 2 weeks I noticed poorer battery performance. 4 days ago, After a lot of searching online I decided to flash Omega 12 then Perseus 33.3 for better battery performance and better control of my CPU.
That's what I did. First, wiped all data through CWM then installed Omega 12 ---> Perseus 33.3 ---> clean cached data ----> restored my apps through titanium ----> fixed permissions ---> charged my mobile to 100% then wiped battery stats ---> set gpu to 440mhz and cpu scaling --> frequency responsiveness to 600mhz === every thing went very good with wonderful performance and battery life with 40 hours battery life ,more than 7 hours onscreen and also did couple of successful restarts to change SIM card .I thought that's it "I will stick with this system forever no matter what."
:highfive::highfive::highfive::highfive:
As I said, after 40 hours of battery life my battery died so I put my note 2 with the recharger while off because it was night time. Next morning, I unplugged my phone then turned it on but my startup screen keep showing the big robot walking with no ending for 30 minutes. Tried to restart the phone couple times, searched online for a similar issue but nothing related to omega and Perseus, wiped cache, dalvik but still the same.
:crying::crying::crying::crying:
Finally, I restored an image through CMV contains my 4.1.1 old stoke ROM + factory kernel just after rooting. My smartphone now is working fine.
My question now is "Why did it happened? Did this happen with anybody before with the same circumstances? and what is the possibility of this happening again if I tried to flash a custom ROM or a new kernel?
I'm ready for any questions
haniwilliam7 said:
HI Guys
I'm an old iOS user but switched to android 2 months ago with a wonderful Note 2 International running android 4.1.1
after one month of use I decided to root my device for VPN service and custom ROM benefits
Everything went fine. First rooted with odin 3.07, then decided as most of users recommended to flash ARHD 11.2
After using my device for 2 weeks I noticed poorer battery performance. 4 days ago, After a lot of searching online I decided to flash Omega 12 then Perseus 33.3 for better battery performance and better control of my CPU.
That's what I did. First, wiped all data through CWM then installed Omega 12 ---> Perseus 33.3 ---> clean cached data ----> restored my apps through titanium ----> fixed permissions ---> charged my mobile to 100% then wiped battery stats ---> set gpu to 440mhz and cpu scaling --> frequency responsiveness to 600mhz === every thing went very good with wonderful performance and battery life with 40 hours battery life ,more than 7 hours onscreen and also did couple of successful restarts to change SIM card .I thought that's it "I will stick with this system forever no matter what."
:highfive::highfive::highfive::highfive:
As I said, after 40 hours of battery life my battery died so I put my note 2 with the recharger while off because it was night time. Next morning, I unplugged my phone then turned it on but my startup screen keep showing the big robot walking with no ending for 30 minutes. Tried to restart the phone couple times, searched online for a similar issue but nothing related to omega and Perseus, wiped cache, dalvik but still the same.
:crying::crying::crying::crying:
Finally, I restored an image through CMV contains my 4.1.1 old stoke ROM + factory kernel just after rooting. My smartphone now is working fine.
My question now is "Why did it happened? Did this happen with anybody before with the same circumstances? and what is the possibility of this happening again if I tried to flash a custom ROM or a new kernel?
I'm ready for any questions
Click to expand...
Click to collapse
Firstly, NEVER let you battery die completly, it is not good for the overall life of the battery.
Secondly if that ever happens boot to recovery and clear dalvik cache and fix permissions. This will usually help.
It's hard to say exactly what cause this issue without a log.
Also, please keep regular backups through your preferred recovery, as this will help if you need to go back.
Cheers,
Evil.
Thanks for the tips.... really appreciated
Sent from my GT-N7100 using xda app-developers app
same
same thing happened to me exactly .
same rom same kernel
i couldnt even restore a previous backup of omega from a week ago - it just wouldnt restore without rebooting !!
also, for my note 2 to work again i had to reflash my recovery (twrp) via odin and reinstall my rom.
i had a whole load of other issues and in all honesty im almost thinking i may have a broken NAND chip - sudden death - not quite, but im patched for that, but may be a small fail on the chip had caused this event , i really dont know.
im back to normal now but im stll very worried about the next few days - please read my other post where i explained this fault at the time it happened.
http://forum.xda-developers.com/showthread.php?p=38697185#post38697185
thanks.
.
I will look at it... but I think in the mean time I will stick with my original stock and kernel for a while till I have the courage for another rom/kernel trial
Sent from my GT-N7100 using xda app-developers app
Hello everyone,
I have a problem with my Desire HD running ViperDHD 2.3.0 ROM.
When I take a picture using flash with low battery, the phone shutdown and stuck on boot after restarting.
I've tried wiping battery stat, cache and Dalvik cache and none of this fixed the issue but the only way to get phone running is to flash again the rom.
Is there a way to fix this or is a battery problem?
Thank you all!
antanigoni said:
Hello everyone,
I have a problem with my Desire HD running ViperDHD 2.3.0 ROM.
When I take a picture using flash with low battery, the phone shutdown and stuck on boot after restarting.
I've tried wiping battery stat, cache and Dalvik cache and none of this fixed the issue but the only way to get phone running is to flash again the rom.
Is there a way to fix this or is a battery problem?
Thank you all!
Click to expand...
Click to collapse
Sounds like your battery needs replacing, you might want to replace it and see if the problem still occurs
Sent from my Desire HD using Tapatalk 4 Beta
Thanks, I'll try that when i get a new battery!
I had a similar problem on Viper DVD 2.x. If the battery was under let's say 70% when taking photo with flash, the phone turned off. The only way to turn it back on was connecting the charger. I replaced the battery for the new one, original HTC, but situation is the same .
antanigoni said:
Hello everyone,
I have a problem with my Desire HD running ViperDHD 2.3.0 ROM.
When I take a picture using flash with low battery, the phone shutdown and stuck on boot after restarting.
I've tried wiping battery stat, cache and Dalvik cache and none of this fixed the issue but the only way to get phone running is to flash again the rom.
Is there a way to fix this or is a battery problem?
Thank you all!
Click to expand...
Click to collapse
Changing the battery fixed the issue... Thanks a lot!
paaja said:
I had a similar problem on Viper DVD 2.x. If the battery was under let's say 70% when taking photo with flash, the phone turned off. The only way to turn it back on was connecting the charger. I replaced the battery for the new one, original HTC, but situation is the same .
Click to expand...
Click to collapse
Charge full battery for your phone. Reboot to recovery and try wipe battery stat. If the problem not fix. Change to another rom. .
I cleared battery stats and caches, charged to full but the situation is the same . I will have to live with that
paaja said:
I cleared battery stats and caches, charged to full but the situation is the same . I will have to live with that
Click to expand...
Click to collapse
Oke. Read around DHD forum and i think your answer is change another new battery. :laugh:
I'm considering the same thing . But it's really weird that new, original battery would be faulty
Odesláno z mého Desire HD pomocí Tapatalk 4
Hi everyone,
I have :
Samsung Galaxy Note 2 N7100 32GB
Omega ROM v14 4.1.2
Stock kernel
which I got 7 months ago . I rooted it few days after I got it and installed latest Omega ROM at that time and some later versions of Omega ROMs and stayed on v14 for long time with stock kernel . The device was running normally and smoothly till a week ago when the device suddenly started to lags and freezes and overheats with late response to touch and typing and opening apps .
During this week I installed cool tool and system tuner to monitor the CPU load and temperature I noticed that the CPU load is between 90 - 98% almost all the time with fast battery drain and the device freezes when the load reach 100 % ( not always ) even if I'm not running any app and sometimes the screen does't turn on after turning off till I force restart or remove the battery and put it back . Then I installed latest Omega ROM v16 with stock kernel with wiping cache and dalvik cache without full/factory wipe but the problem still there .
I Installed latest Perseus kernel to have some contol over the CPU and tried to change the max frequency up and down with no benefit !! .
I was thinking about Note 2 sudden death syndrome ( SDS ) but my device is internal 32GB version which means it is unlikely to get SDS and eMMC check showed No. Sane chip .
So, I hope to find a solution as I like my Note 2 and I have no interest to change it .
Thank you all
AZZoZiTTi said:
Hi everyone,
I have :
Samsung Galaxy Note 2 N7100 32GB
Omega ROM v14 4.1.2
Stock kernel
which I got 7 months ago . I rooted it few days after I got it and installed latest Omega ROM at that time and some later versions of Omega ROMs and stayed on v14 for long time with stock kernel . The device was running normally and smoothly till a week ago when the device suddenly started to lags and freezes and overheats with late response to touch and typing and opening apps .
During this week I installed cool tool and system tuner to monitor the CPU load and temperature I noticed that the CPU load is between 90 - 98% almost all the time with fast battery drain and the device freezes when the load reach 100 % ( not always ) even if I'm not running any app and sometimes the screen does't turn on after turning off till I force restart or remove the battery and put it back . Then I installed latest Omega ROM v16 with stock kernel with wiping cache and dalvik cache without full/factory wipe but the problem still there .
I Installed latest Perseus kernel to have some contol over the CPU and tried to change the max frequency up and down with no benefit !! .
I was thinking about Note 2 sudden death syndrome ( SDS ) but my device is internal 32GB version which means it is unlikely to get SDS and eMMC check showed No. Sane chip .
So, I hope to find a solution as I like my Note 2 and I have no interest to change it .
Thank you all
Click to expand...
Click to collapse
I suggest to go back to stock (rooted if you want). I was in a similar situation as you are now. I was about to sold my Note 2. I did a factory reset, rooted and installed applications one by one just to see which one misbehaves. I have the perfect phone now
Use it without an sd card....
Thank you both
I started with the easiest solution so I tried to you use without sd card but didn't work.
I gonna try ludovicianul solution and inform you .
Solved !!
I flashed the stock ROM and full wipe/factory reset without unroot then flashed Revolution HD ROM .
The problem was solved in that time .
Then I started to restore my apps by titanium backup one by one and dicovered that A.I.Type keyboard is the reason because when I restored and used it, the CPU usage raised again and the problem returned .
Finally, I opened application manager in the settings and chosed A.I.Type keyboard and did "clear data" and now my mobile runs fast and smooth .
Thank you ludovicianul and Aayush_goel for the help
Glad you got a resolution.
most cooks would advise against a dirty flash and reinstalling apps with tb for the reasons you stated.
Sent from my GT-N7105 using xda app-developers app
3vo3d said:
Glad you got a resolution.
most cooks would advise against a dirty flash and reinstalling apps with tb for the reasons you stated.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Yes, you are right !!
but thank god everything is OK now .
i got my phone repaired few days ago and discovered that i was facing a battery issue..
my phone is showing 100 % battery its nt even changing.. :/ then suddenly after a time duration battery drains down and switch off suddenly.
Things i have tried.
1. i m using xperia ultimate HD rom . so i have reflashed it once again.
2. switched to stock and then to other rom..
3. brought new battery (original sony ericsson one) still nothing happens
any help is appreciated..
Thank you.
axatjpr said:
i got my phone repaired few days ago and discovered that i was facing a battery issue..
my phone is showing 100 % battery its nt even changing.. :/ then suddenly after a time duration battery drains down and switch off suddenly.
Things i have tried.
1. i m using xperia ultimate HD rom . so i have reflashed it once again.
2. switched to stock and then to other rom..
3. brought new battery (original sony ericsson one) still nothing happens
any help is appreciated..
Thank you.
Click to expand...
Click to collapse
I had the same problem too; the only solution I found out to solve the problem was switching to lupus kernel ( on stock ics ). Try wiping everything flash the latest official firmware with flash tool and then flash lupus kernel for stock ics and see if your battery return to work properly:good:
flash lupus kernel if you are on the stock kernel
Just flash any kernel difrernt from stock.
LuPuS v16 for example if you on 4.1.B.0.587 based firmware.
it worked..
Thanks everyone.. i reflashed the kernal again and it started working.. normally again.:laugh::laugh:
*cheers*