[Q] Gingersnap v2.1 - Battery drain when Bluetooth is on standby - Optimus One, P500, V Q&A, Help & Troubleshooting

Hi all,
Need some help with my issue.
I am using Gingersnap v2.1 and am facing severe battery drain because of bluetooth ON. I terribly need bluetooth to be always on in my phone so that I can take calls on my bluetooth headset.
When I checked in betterbatterystats I found msm_serial_hs_dma kernel wakelock as the issue which is not allowing my phone to go to deepsleep mode when BT is on. Is there a fix for this? I really like Gingersnap and want to use this ROM.
Previously I was on Dynamite ROM v5.1 and this ROM did not have this issue with BT on. ie this ROM used to go to deepsleep even when BT was on.
So I am hoping that this issue can be fixed in Gingersnap too.
Thanks for your help

Jred420 said:
Hi all,
Need some help with my issue.
I am using Gingersnap v2.1 and am facing severe battery drain because of bluetooth ON. I terribly need bluetooth to be always on in my phone so that I can take calls on my bluetooth headset.
When I checked in betterbatterystats I found msm_serial_hs_dma kernel wakelock as the issue which is not allowing my phone to go to deepsleep mode when BT is on. Is there a fix for this? I really like Gingersnap and want to use this ROM.
Previously I was on Dynamite ROM v5.1 and this ROM did not have this issue with BT on. ie this ROM used to go to deepsleep even when BT was on.
So I am hoping that this issue can be fixed in Gingersnap too.
Thanks for your help
Click to expand...
Click to collapse
Try changing the kernel because this is most probably kernel problem. use djnoxd 2.5.6 kernel. its good

Souron29 said:
Try changing the kernel because this is most probably kernel problem. use djnoxd 2.5.6 kernel. its good
Click to expand...
Click to collapse
Thanks for the suggestion buddy, installed djnoxd 2.5.6 kernel.
But I find the battery drain is still there. :crying:

I am sorry but I m out of suggestions. Y don't u put up this question in gsnap thread. neko may help u der. Gud luck

Related

[Q] Black Screen After Calls... Fix anyone?

Device: LG G2X
Rom: MIUI 1.11.11 (2.3.7)
Issue: Black Screen After Phone Call
Failed Fix Attempts: Turning Off Proximity Sensor, Reflashing Rom
Question: Does anyone know how to fix this issue? The only way to turn the phone back on after some calls is to pull the battery and turn the phone back on. It's starting to get a little frustrating. Any help is appreciated.
Azuske said:
Device: LG G2X
Rom: MIUI 1.11.11 (2.3.7)
Issue: Black Screen After Phone Call
Failed Fix Attempts: Turning Off Proximity Sensor, Reflashing Rom
Question: Does anyone know how to fix this issue? The only way to turn the phone back on after some calls is to pull the battery and turn the phone back on. It's starting to get a little frustrating. Any help is appreciated.
Click to expand...
Click to collapse
Its more a kernel issue than a rom issue.
If your using Trinity kernel than that would be I'm guessing the reason why. I always had the call SOD when using Trinity kernel new or old. Ive used different kernels to see if it would help and that fixes it for me. Currently am running eagle blood with faux's 4.3 kernel and that resolved my call SOD. I could be wrong in your case but for me it worked switching kernels.
Sent from my LG-P999 using XDA App
gman87 said:
Its more a kernel issue than a rom issue.
If your using Trinity kernel than that would be I'm guessing the reason why. I always had the call SOD when using Trinity kernel new or old. Ive used different kernels to see if it would help and that fixes it for me. Currently am running eagle blood with faux's 4.3 kernel and that resolved my call SOD. I could be wrong in your case but for me it worked switching kernels.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
That would explain it because I actually was using Trinity. Now I am using Dragon-G2X and its working perfect (so far). Thanks for your input.

[Q] Promethiusrom charging problem

Hi there.
I have problems charging my optimus 3D with promethius rom 1.4. When i turn off the phone the phone starts to charge and when the screen is off suddenly stop charging and start to overheating. Only i can charge it if the phone is on. In fact i have this problem since i used this rom. With other roms i don't have this problem. Any solutions .
Try different Kernel like v1.3
or change the ROM to this one
http://www.htcspain.com/roms-lg-optimus-3d-384/mega-post-rom-acura3dmax-v2-53914/
i have the exact same problem kernal 1.4.5.1 rom 1.4
iqb043 said:
i have the exact same problem kernal 1.4.5.1 rom 1.4
Click to expand...
Click to collapse
Me too, using a long time bluetooth not work
Sent from my Kindle Fire using Tapatalk 2

viper 1.2.1 reboots?

my viper Rom keeps keeps rebooting itself at times AMD then there's a huge battery drain , especially when I'm on on demand governor ..
I even tried changing my kernel to SebastianFM but still the same problem, even with the mod for Sebastian fm..
can someone help me figure out the might be causing this? plus my battery's less awesome then 1.1 ,
so can someone help me figure out the problem?
and if any other person could help me with which kernel works best for you guys with viper 1.2.1 ?
I'd really appreciate help, thank you
Hi there, this is best posted on the viper development site. Everyone there is using the same Rom and perhaps more people even have your issue and know of a fix for it. So it is really best to post this on viper development where you can get Rom specific help. I use viper also and have not experienced you're issue. Have you considered doing a fresh download and full wipe and reinstallation of the Rom? This might help. But do post on viper site and hopefully someone knows of a fix if above doesn't solve the issue. Best wishes.
Sent from my HTC Sensation 4G using xda premium
Rhishabm said:
my viper Rom keeps keeps rebooting itself at times AMD then there's a huge battery drain , especially when I'm on on demand governor ..
I even tried changing my kernel to SebastianFM but still the same problem, even with the mod for Sebastian fm..
can someone help me figure out the might be causing this? plus my battery's less awesome then 1.1 ,
so can someone help me figure out the problem?
and if any other person could help me with which kernel works best for you guys with viper 1.2.1 ?
I'd really appreciate help, thank you
Click to expand...
Click to collapse
I use Faux's kernel with intelidemand governor and it's perfect (performance and battery)
I don't know aboot reboots... wait for other answers.
The kernel I use is yank version 2.5. I just downloaded it caused many viper users use it and like it. I thought I'd give it a try. So far so good.
Sent from my HTC Sensation 4G using xda premium
Yank 2.52 works well for me. I had constant reboots when I was undervolted by 100, but now that I'm not undervolted at all it doesn't reboot anymore. So it may not necessarily be kernel but kernel settings that can give you bootloop.
Sent from my HTC Sensation 4G using xda app-developers app
What firmwire are you using 3.32 or is it 3.33 and also are you s off and Fyi sebastien's kernel there's two mods you need in order to get the correct settings if not thats all you will get is battery drain i've been using it for a week now and its awsome
Sent From My Viper S 1.2.1with true s off by alpha revolutionary

Help with WIFI fix- Ayone

Hi
i dont know if anyone out there can help fix a wifi issue on the rom below
http://forum.xda-developers.com/showthread.php?t=1943745
What is your issue?
Try flashing a custom kernel, like Matr1x kernel.
jacob66 said:
What is your issue?
Try flashing a custom kernel, like Matr1x kernel.
Click to expand...
Click to collapse
WIFI wont turn on
thats just the thing i dont know what it is, everything on the rom works except the WIFI, it was ported by glaxyuser, we tried different kernels and still no joy

CM-11 nightly sleep of death

Hello everyone, you will encounter CM11 "sleep death" problem? I think it is a kernel issue. Someone can tell me why? I'm sorry my English is poor.
Hi,
It's best that you ask ROM/Kernel related problems in the ROM/kernel thread itself. By doing so, you will get much quicker reply from people who are already using CM11 :cyclops:
Did you change your kernel? Using stock CM one? CAF?
please provide more information.
are you overclocking/undervolting?
what kernel do you use?
what about lockscreens/widgets/notification apps?
yxwzyyk said:
Hello everyone, you will encounter CM11 "sleep death" problem? I think it is a kernel issue. Someone can tell me why? I'm sorry my English is poor.
Click to expand...
Click to collapse
If you aren't overclocking or undervolting, it's probably a bug. Kernel issue for sure.
Thank you for your help, ROM I'm using my own build CM11, no modifications to the kernel, and no overclocking or reduced frequency, probably from the beginning of last week, the "sleep of death" problem,
Now I'm using "Chaos-Kernel_v11.0-[03-13] - [05-51]" no problem, but yesterday updated the "Chaos-Kernel_v11.0-[03-19] - [12-21]" again "sleep of death" problem occurs, but the frequency is much smaller.
I do not know whether the expression of clear, I want to know what causes CM kernel will "sleep of death"
Thank you for your help again
Aerowinder said:
If you aren't overclocking or undervolting, it's probably a bug. Kernel issue for sure.
Click to expand...
Click to collapse
I do not have overclocking or undervolting
yxwzyyk said:
I do not have overclocking or undervolting
Click to expand...
Click to collapse
It's a kernel problem almost certainly. Changing from CM kernel to another kernel wouldn't necessarily fix anything, since they are pulling from the same source. Might I recommend you try either stock or Slim for a few days, to see if you can reproduce the issue?
Aerowinder said:
It's a kernel problem almost certainly. Changing from CM kernel to another kernel wouldn't necessarily fix anything, since they are pulling from the same source. Might I recommend you try either stock or Slim for a few days, to see if you can reproduce the issue?
Click to expand...
Click to collapse
CM11 February 28 to build my own is normal.
Now CM11 March 17 with the use of Chaos-Kernel_v11.0-[03-13] - [05-51] Up to now it is still normal
I think it might be CyanogenMod / android_kernel_lge_hammerhead Mar 05 after Commits cause this problem

Categories

Resources