[Q] PA 4+ Battery drainage - Paranoid Android Q&A

[Q] PA 4+ Battery drainage - Paranoid Android Q&A

Hello
I've been running the latest BETA 3 paranoid android on my galaxy nexus. Im having the following issue..
In the night the cell phone would be charged 100% but when upon waking up the phone would be dead or almost dead. Theres some issue with the Google Keyboard.
Any help? Screen shots attached.

Rawfay said:
Hello
I've been running the latest BETA 3 paranoid android on my galaxy nexus. Im having the following issue..
In the night the cell phone would be charged 100% but when upon waking up the phone would be dead or almost dead. Theres some issue with the Google Keyboard.
Any help? Screen shots attached.
Click to expand...
Click to collapse
I advice you to reboot to recovery do a factory reset,wipe dalvik cache,format system partition and reinstall the rom and after that gapps.And boot again.I can assume that you may have dirty flashed without wiping coming from another rom?What gapps package did you use?

Related

[Q] Random unlocks

Hey there!
I am having a rather annoying and weird problem.
It started when I upgraded to 4.2 yesterday. I was running yakju 4.1.2 and then flashed the takju stock images.
That was when my phone randomly started waking up to show the lockscreen. I thought that maybe the upgrade
process broke something, however wiping the phone didn't make it go away.
I have saved about 4 logcats from when the phone woke up, but it is very inconclusive. There is nothing repetitive at all,
except for this message:
Code:
I/PowerManagerService( 382): Waking up from sleep...
I/WindowManager( 382): Lock screen displayed!
I did some research and it seems that some people have had similar problems (unrelated to 4.2) where it was related to the micro-USB port. It was suggested to bend the middlebar in the micro USB port upwards, which didn't fix my problem, though.
The ones who had this problem also said that sometimes the battery icon displayed that it was being charged (shortly).
That doesn't seem to happen over here, though, and nothing is being mentioned in the logcat about it, either. Also, this even happens with the USB cable plugged in..
Anyone have any ideas/suggestions? Is there a way to let me find out what initiated the phone wakeup to the lockscreen?
Cheers,
Henrik

Same here... running now on 4.2 jop40c after a comlete 4.2 stock flash: the device wakes up randomly, approx. once each hour. Shows the lockscreen and then goes to sleep again....

licht77 said:
Same here... running now on 4.2 jop40c after a comlete 4.2 stock flash: the device wakes up randomly, approx. once each hour. Shows the lockscreen and then goes to sleep again....
Click to expand...
Click to collapse
Good to know I'm not alone. I have re-flashed 4.1.2 to see if the problem persists. I am really hoping this is a software bug..

@licht77: May I ask what apps you are using?
For the record: it's been about 3 hours with 4.1.2 now and so far it did not wake up randomly.

hrkfdn said:
@licht77: May I ask what apps you are using?
For the record: it's been about 3 hours with 4.1.2 now and so far it did not wake up randomly.
Click to expand...
Click to collapse
I was in CNA3.8.8 and flash (making just dalvik wipe and cache wipe)
I had the same problem and i needed to make a full wipe and factory reset . so it works flawless.

Kleber Pereira said:
I was in CNA3.8.8 and flash (making just dalvik wipe and cache wipe)
I had the same problem and i needed to make a full wipe and factory reset . so it works flawless.
Click to expand...
Click to collapse
I *did* wipe my phone, though. As did licht77. Still the same.
Still no random wakeup on 4.1.2.

Went back to a 4.1.2 Nandroid... No Wakeups Full Wipe, stock 4.2 -> here we go waking up again

licht77 said:
Went back to a 4.1.2 Nandroid... No Wakeups Full Wipe, stock 4.2 -> here we go waking up again
Click to expand...
Click to collapse
http://code.google.com/p/android/is...en&colspec=ID Type Status Owner Summary Stars
We are not alone. Would you be so kind to star this report as to raise importance?

Did so...

[Q] Problem with Omega 12 + Perseus 33.3 start up screen lasts forever

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

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

back button does it's own thing

while using my phone, my back button will light up, vibrate, and just do its own thing. open multi window. take me out of apps. just goes crazy. anyone else have this issue?

What Rom are you running ? What Recovery ? Did you do a Clean install of the Rom ?

No matter what rom. It takes about 12 hours after install. Yesterday I woped everything, data, everything and no problem. Woke up this morning and it started doing it again.
galaxy s3 running supernova or goodness......

Try going back to stock unrooted...if the problem persists, unfortunately, it's probably hardware related
Sent from my S3 on Sense 5 (you jelly?)

duncakes said:
No matter what rom. It takes about 12 hours after install. Yesterday I woped everything, data, everything and no problem. Woke up this morning and it started doing it again.
galaxy s3 running supernova or goodness......
Click to expand...
Click to collapse
By wiped everything do you mean : system - data - dalvik cache - cache - factory reset ? If the answer is yes then I'd suggest trying what CNexus posted.
TEAM MiK
MikROMs Since 3/13/11

[Q] Problem with camera flash

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

[Q] What is wrong with my Gnex?

Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?

JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.

Are you sure it's the phone and not an app?

chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.

Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4

chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.

why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct

Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.

I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!

well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?

lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).

Develop Bugs

welcome