Related
Ok I have this one issue when running AOKP and I have back Burton set to kill tasks for no apparent reason tasks well be killed without back button any ideas
Sent from my SCH-I500 using XDA App
It's the phantom button issue. Just another form of it because you gave the phantom more power
Sent from my SCH-I500 using xda premium
Any fix for this been found......I guess it can join my phantom ring
Sent from my SCH-I500 using XDA App
The problem is mainly cause by hardware interference, but it can be bandaged a little bit. If you search the old glitch thread you could read a fair amount about phantom press issue. Glitch 13.1 (for gingerbread) has "fixes" for the issue in place that drastically reduced the amount of phantom presses I experienced. Those weren't added to v14 though, because for others it apparently didn't work or actually exacerbated the issue. I asked tk-glitch about it and I think he said he's at least looking at implementing it into v14 though.
You can also turn off the long-press back to kill feature too, I've kept it off because I had issues with it closing apps by itself when it was enabled.
k_nivesout said:
The problem is mainly cause by hardware interference, but it can be bandaged a little bit. If you search the old glitch thread you could read a fair amount about phantom press issue. Glitch 13.1 (for gingerbread) has "fixes" for the issue in place that drastically reduced the amount of phantom presses I experienced. Those weren't added to v14 though, because for others it apparently didn't work or actually exacerbated the issue. I asked tk-glitch about it and I think he said he's at least looking at implementing it into v14 though.
You can also turn off the long-press back to kill feature too, I've kept it off because I had issues with it closing apps by itself when it was enabled.
Click to expand...
Click to collapse
Hey I tried to search that thread just now and I couldn't find anything on it. what would you suggest I search for to find the posts?
tacofox said:
Hey I tried to search that thread just now and I couldn't find anything on it. what would you suggest I search for to find the posts?
Click to expand...
Click to collapse
go to the dev section and look up the glitch v13 thread...read thru the last 20-30pages.
There's no real "fix". I've coded a band-aid to make it happen far less often. Here's the thread: https://github.com/Efpophis/Glitch/issues/9
I'm running kgb kernel with the "fix". I think Bill was going to code it into glitch...
update 16 Mar 2012:
there is a real fix but it involves taking your phone apart and modifying it. See this thread:
http://forum.xda-developers.com/showthread.php?t=1328670
electric bill said:
There's no real "fix". I've coded a band-aid to make it happen far less often. Here's the thread: https://github.com/Efpophis/Glitch/issues/9
I'm running kgb kernel with the "fix". I think Bill was going to code it into glitch...
Click to expand...
Click to collapse
thanks for taking your phone apart. That "bandaid" has made a world of difference.
Sent from my SCH-I500 using xda premium
After experiencing extremely bad battery life and searching everywhere around the web for answers i have found a solution for wakelock problems that solved all my battery woes.
Thanks goes to the people that originally found these fixes.
This step stops the AudioOut_1 partial wakelock bug from keeping device in awake mode:
0.go to settings > sound and turn off touch sounds and screen lock sounds
These steps stop the kernel wakelock 100% problem:
1.turn on aeroplane mode
2.turn off device
3.take out battery for 10 seconds
4.turn on device
5.wait for everything to load
6.turn off aeroplane mode
Sent from my GT-I9100 using Tapatalk
Hi!
Can you describe, please, how did you find that this exactly steps (and no other) solved your battery life problems?
Thanks.
Regards.
Good to know. Thanks
Sent from my GT-I9100 using Tapatalk
For starters,I tried everything else I could and this is the only thing that helped.
I found the fixes all around different forums for GS2,GNote and GNexus.
I tried it for myself yesterday and my battery life has doubled.
Install BetterBatteryStats from the thread on XDA and you can see if you have these wakelock problems,look under Partial Wakelock and Kernel Wakelock.
I just wanted to share these dead simple steps to spare some people from the agony that is 7h battery life :banghead:
Sent from my GT-I9100 using Tapatalk
Nice info. Might come in handy someday. Thanks for sharing.
sent from my fingers to your face.
there is another trick to disable apps sync or the famous ! CALENDAR sync wake ups go in "account and sync'' and click on your account and uncheck what you want to stop sync!
for facebook wake ups the only thing I found is freezing it with titanium and make sure your disconnected from it every time you quit this app
HOP FOR A FIX FROM FACEBOOK SOON !
for the rest I don't think we can make something unless sammy release the source and finally an official ICS !
Mister Jozo said:
For starters,I tried everything else I could and this is the only thing that helped.
I found the fixes all around different forums for GS2,GNote and GNexus.
I tried it for myself yesterday and my battery life has doubled.
Install BetterBatteryStats from the thread on XDA and you can see if you have these wakelock problems,look under Partial Wakelock and Kernel Wakelock.
I just wanted to share these dead simple steps to spare some people from the agony that is 7h battery life :banghead:
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I asked how did you find those steps because in my old days of Motorola Motoronga MotoFAIL Milestone (TM) there were a bunch of Black Magic Recipes like this in order to save battery and none of them worked, unsurprisingly, of course.
Please, don't get me wrong, I'm not here to troll you or your thread, but just to know how people find these "steps".
Anyway, very interesting.
Thanks.
Regards.
These fixes will help your battery only if you have wakelock problems,they don't do anything otherwise.
I also resent black magic recipes. Some time ago I read that many common battery saving apps and tips don't help the battery,sometimes even causing more battery drain.It was an independent research where they regularly tested the battery itself with ampermeters.
Sent from my GT-I9100 using Tapatalk
usually turning off touch sounds and screen lock sounds should solve the "AudioOut_1" problem, at least it worked for me
---------- Post added at 07:31 PM ---------- Previous post was at 07:27 PM ----------
zamana said:
I asked how did you find those steps because in my old days of Motorola Motoronga MotoFAIL Milestone (TM) there were a bunch of Black Magic Recipes like this in order to save battery and none of them worked, unsurprisingly, of course.
Please, don't get me wrong, I'm not here to troll you or your thread, but just to know how people find these "steps".
Anyway, very interesting.
Thanks.
Regards.
Click to expand...
Click to collapse
You neet to find out which wakelock are draining your battery when the screen is off before you trying out some "Black Magic Recipes".For instance ,if you installed some instant message app which keeps pulling something from the server and prevent your phone from going to deep sleep, disabling sound will not help you get better battery life.
Mister Jozo said:
After experiencing extremely bad battery life and searching everywhere around the web for answers i have found a solution for wakelock problems that solved all my battery woes.
Thanks goes to the people that originally found these fixes.
This step stops the AudioOut_1 partial wakelock bug from keeping device in awake mode:
0.go to settings > sound and turn off touch sounds and screen lock sounds
These steps stop the kernel wakelock 100% problem:
1.turn on aeroplane mode
2.turn off device
3.take out battery for 10 seconds
4.turn on device
5.wait for everything to load
6.turn off aeroplane mode
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Thanks, worked perfectly for my ICS Galaxy note !!
Originally Posted by Vaddy23
Can someone help me out with a proper wiping technique or if a full wipe is even neccesary before/after I update to ICS. I'm on the latest stock firmware Gingerbread 2.3.6 with a unlocked UK Note that has never been rooted. Do I even have to wipe? I don't want any issues with battery life so on and so forth. Or do I wipe after I perform the update to ICS? Along with a factory reset? Someone please help, thanks..
Click to expand...
Click to collapse
I had issues with reboots and poor battery life after upgrade. I went back to gingerbread and done factory reset. Once booted I immediately went to kies and upgraded to uk ics. I have no issues now with reboots or battery. Very happy now and speed is great. Remember to factory reset in gingerbread and not ics. Just reinstall apps from the play store after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sent from my GT-N7000 using xda premium
Mister Jozo said:
After experiencing extremely bad battery life and searching everywhere around the web for answers i have found a solution for wakelock problems that solved all my battery woes.
Thanks goes to the people that originally found these fixes.
This step stops the AudioOut_1 partial wakelock bug from keeping device in awake mode:
0.go to settings > sound and turn off touch sounds and screen lock sounds
These steps stop the kernel wakelock 100% problem:
1.turn on aeroplane mode
2.turn off device
3.take out battery for 10 seconds
4.turn on device
5.wait for everything to load
6.turn off aeroplane mode
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Thanks!! It worked for me when my Galaxy Note was running ICS and now again when I have downgraded to GB.
CPU Spy showed 200 Hz to be the lowest state touched and there was no Deep Sleep. After these steps, it goes to Deep Sleep when not used.
So I spent about four hours researching this. From flashing kernels removing apps and installing modems nothing worked. EXCEPT putting phone in airplane mode, rebooting, then disabling airplane mode. Phone enters deep sleep quickly and consistently after performing this. I encourage anyone with this issue to try the steps above and report back. Note to devs if this is in fact a fix, can you incorporate some kind of script that places phone in airplane mode on reboot and automatically disables on boot? I believe a lot more people are affected by this than we know. Does anyone NOT have this issue? if you know for a fact your phone spends a lot of time in deep sleep please identify which modem you are using. Supposedly this occurs due to a lack of response from modem to os.
from chewable on ics forums:
Bad battery drain due to a wakelock being held for an unspecified length of time. BetterBatteryStats shows it to be RILJ holding the wakelock. I've narrowed it down to a RIL request named RIL_REQUEST_SET_TTY_MODE. I dumped out RILJ.mRequestsList during the held wakelock and I see this request staying around and waiting for a response from the RIL. It's as if the RIL is not responding to this request and I don't see RILReceiver processing a response to this request.
anyone know what tty is?
Sent from my SGH-I777 using xda app-developers app
topiratiko said:
So I spent about four hours researching this. From flashing kernels removing apps and installing modems nothing worked. EXCEPT putting phone in airplane mode, rebooting, then disabling airplane mode. Phone enters deep sleep quickly and consistently after performing this. I encourage anyone with this issue to try the steps above and report back. Note to devs if this is in fact a fix, can you incorporate some kind of script that places phone in airplane mode on reboot and automatically disables on boot? I believe a lot more people are affected by this than we know. Does anyone NOT have this issue? if you know for a fact your phone spends a lot of time in deep sleep please identify which modem you are using. Supposedly this occurs due to a lack of response from modem to os.
from chewable on ics forums:
Bad battery drain due to a wakelock being held for an unspecified length of time. BetterBatteryStats shows it to be RILJ holding the wakelock. I've narrowed it down to a RIL request named RIL_REQUEST_SET_TTY_MODE. I dumped out RILJ.mRequestsList during the held wakelock and I see this request staying around and waiting for a response from the RIL. It's as if the RIL is not responding to this request and I don't see RILReceiver processing a response to this request.
anyone know what tty is?
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Dunno how to fix it besides the airplane mode. Have you tried another kernel?
All siyah fluxxi and dream. All have shown the issue at some point
Sent from my SGH-I777 using xda app-developers app
topiratiko said:
All siyah fluxxi and dream. All have shown the issue at some point
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
What rom are you running?
I am having the same issue. Task's AOKP from 7/3, fluxxi kernel from 7/17.
Modem: UCPLC5.
Strangely, I've been unable to replicate it for the past 2 hours - phone sleeps fine. W T F.
jthatch12 said:
What rom are you running?
Click to expand...
Click to collapse
AOKP 7-3
Seems like rebooting with airplane mode is the only option
topiratiko said:
Seems like rebooting with airplane mode is the only option
Click to expand...
Click to collapse
I remember I had similar issue - RILJ wakelock after using headphones to listen music. It's disappeared by itself a couple of months ago (I'm on a latest CM9).
But, at the time I was able to get off RILJ wake lock by unplugging headphones, turning airplane mode on, screen off, wait a couple of mins and turn airplane mode off. This should get rid of RILJ wakelock.
hope this helps.
-- vlad
Well, I don't know if the OP's issues had to do with unplugging headphones but it doesn't seem to be. I'm glad this was posted as I couldn't figure out why I was only getting 85% deep sleep in CPUSpy and the phone would keep showing 10%-11% as 200Mhz in the background. Kernel Wakelocks didn't show any issues and I didn't see anything in Partial Wakelocks at first...then I charged up my phone and saw RILJ showing as 59.8%!!!!!
In fact, RILJ was showing up very high every single time I would charge my phone - even if I rebooted my phone after a full charge.
Eventually, after several hours, it would drop and show about 3.7% or lower depending on how long the phone was sitting on standby without being used. But this explains why I was losing about 4%-5% an hour.
I tried the Airplane Mode on > Reboot > Airplaine Mode off and my phone is now entering Deep Sleep at 94%!
No apps removed or frozen. Just followed OP's instructions!
I'm on AOKP 7-03 (running the stock task650 kernel but switching kernels didn't improve or worsen battery life).
This RILJ may have been fixed in the latest CM9 nightlies.
(Yes, I know taskt650 is currently working on an AOKP JB build so I'm pretty certain that this will be fixed in that build.)
Did this before going to bed and drained 4 points in 6 hours!
Sent from my Samsung Galaxy S II
Aokp/Team Skyfire
I too am having this problem using task & ktoonsez's AOKP 7/3. For me, it mainly occurs with headphone use. I switched to Semi v16c and the problem went away, but I really want to go back to AOKP! I just got tired of obsessing about this wakelock and switched....
Hopefully JB will bring a final cure.
Sent from my Nexus 7 using xda app-developers app
h3lluvaninjuhneer said:
I too am having this problem using task & ktoonsez's AOKP 7/3. For me, it mainly occurs with headphone use. I switched to Semi v16c and the problem went away, but I really want to go back to AOKP! I just got tired of obsessing about this wakelock and switched....
Hopefully JB will bring a final cure.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
There is no escape from RILJ on JB(as of now). Blame Samsung RIL, its complete horsebleep.
Ahh, I have been seeing this on my wife's skyrocket so I'm gonna try this on her phone.
Sent from my SGH-I777 using Tapatalk 2
Sunuva **%&$ muther %&%$## I HATE RILJ!!!!
Sent from my Samsung Galaxy S II
Aokp/Team Skyfire
I have tried several kernels (with task's AOKP), full wipe and reflash, etc., but the only solution was to go to a Samsung based ROM. I noticed the following over on the international GS2 cm9 development thread, but don't see any evidence this was chased to ground: http://forum.xda-developers.com/showthread.php?p=25047473
At this point, I'm just hoping one of the devs figures out a solution....
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
I've got the same problem using the 3g turbocharger from zeppelinrox and setting the experimental 1 values; try it with every other settings to see if it works I think it's a problem with some ROM settings!
In the Unix world tty is teletype, or another word to describe a terminal / console session.
Sent from my SGH-I777 using xda app-developers app
So any way to get a script for this? Since the airplane mode > reboot > airplane mode seems to be the only fix... can we get a script that will run this automatically somehow? It's not a big deal if we can't... after all it only takes a few second to turn airplane mode on but sometimes I forget...
I'm definitely having the issue with headphones on the latest builds of AOKP and Fluxi.
Could our RILJ partial wakelock issue be related to TTY (specifically: RIL_REQUEST_SET_TTY_MODE)? It appears to have been fixed in CM9 - see here:
http://review.cyanogenmod.com/#/c/16190/
Also, post #3028 on this page seems to exactly describe how & when I get the RILJ partial wakelock:
http://forum.xda-developers.com/show...10400&page=303
lmarr28 said:
I'm definitely having the issue with headphones on the latest builds of AOKP and Fluxi.
Could our RILJ partial wakelock issue be related to TTY (specifically: RIL_REQUEST_SET_TTY_MODE)? It appears to have been fixed in CM9 - see here:
http://review.cyanogenmod.com/#/c/16190/
Also, post #3028 on this page seems to exactly describe how & when I get the RILJ partial wakelock:
http://forum.xda-developers.com/show...10400&page=303
Click to expand...
Click to collapse
From what I have read regarding TTY on cellular, it requires a special cable for the headphone jack, so that makes sense it has something to do with the headphones.
Is anyone else getting Android OS around 50-60% battery use?
I have tried every ROM included going back to stock. I have ran the phone with nothing but Stock and no apps installed for a day and still get the same drain so I can only assume its a kernel issue.
I am not familiar with LG products in the slightest, but I had a yellow screen of death the other day...something I have never seen in my years with samsung android products. Anyone have any idea what this is maybe it is pointing to a hardware issue?
LG made a great phone, but I don't think I will keep it much longer. Locked boot loaders, no sources, and history of terrible updates have me regretting purchasing this phone. I tried my hand at building a working jb release when I first got the phone and it is going to take a skill set I do not have and I hate waiting on a company to do what they've never done in the past..
jivy26 said:
Is anyone else getting Android OS around 50-60% battery use?
I have tried every ROM included going back to stock. I have ran the phone with nothing but Stock and no apps installed for a day and still get the same drain so I can only assume its a kernel issue.
I am not familiar with LG products in the slightest, but I had a yellow screen of death the other day...something I have never seen in my years with samsung android products. Anyone have any idea what this is maybe it is pointing to a hardware issue?
LG made a great phone, but I don't think I will keep it much longer. Locked boot loaders, no sources, and history of terrible updates have me regretting purchasing this phone. I tried my hand at building a working jb release when I first got the phone and it is going to take a skill set I do not have and I hate waiting on a company to do what they've never done in the past..
Click to expand...
Click to collapse
Easy, brother. I have only had one of my apps/utilities run higher than AndroidOS ever on this phone; however, that said, I think there is a problem with the way it's being calculated. I'm getting really good battery life with good sleep and still AndroidOS shows the highest by far. I know that's abnormal for it to be so high and still get good battery life, but it is what it is.
Edit: you've installed the fast dormancy toggle, right? As for the yellow screen, I've seen it once in my two months with the phone, just rebooted and carried on. Forgot what they said it was...but it is here in this forum somewhere.
Sent from my LG-E970 using xda app-developers app
I was just about to post something similar. Andriod OS being high kind of makes sense if nothing else is using the battery, although you would expect that number to fall significantly with increased screen on time and heavy app usage, which it doesn't ever seem to.
I've been having horrible battery drain lately. I'm currently traveling for business, and just use my OG for web surfing and stuff when I'm in my hotel. I leave the phone in airplane mode, with WiFi on. About two weeks ago, when I was on The Base 0.4 in that same configuration, my battery would drain maybe 1% an hour while I was sleeping.
Recently I've been on The Base 0.7.3, and my battery drains over 5% an hour while I'm sleeping. This means no screen on, no apps running, and even turning WiFi off! How does it use that much battery when it's not doing anything? Now, I'm not entirely sure what kernel I'm running. The first time I installed The Base 0.7.3 I used sk8's kernel. After getting poor battery life, I reflashed 0.7 and 0.7.3, this time choosing the freegee kernel. I'm not actually sure if the kernel changed though.
Anyway, I think I'll post again tomorrow with some screenshots from Better Battery Stats+ and CPU Spy.
I'm wondering if this recent botched update had the battery fixes we need. Hopefully they'll re-release it soon.
Jank4AU said:
Easy, brother. I have only had one of my apps/utilities run higher than AndroidOS ever on this phone; however, that said, I think there is a problem with the way it's being calculated. I'm getting really good battery life with good sleep and still AndroidOS shows the highest by far. I know that's abnormal for it to be so high and still get good battery life, but it is what it is.
Edit: you've installed the fast dormancy toggle, right? As for the yellow screen, I've seen it once in my two months with the phone, just rebooted and carried on. Forgot what they said it was...but it is here in this forum somewhere.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Yea I've tried fdt but I think it has to be kernel related drain issues
Sent from my LG-E970 using Tapatalk 2
Digil said:
I was just about to post something similar. Andriod OS being high kind of makes sense if nothing else is using the battery, although you would expect that number to fall significantly with increased screen on time and heavy app usage, which it doesn't ever seem to.
I've been having horrible battery drain lately. I'm currently traveling for business, and just use my OG for web surfing and stuff when I'm in my hotel. I leave the phone in airplane mode, with WiFi on. About two weeks ago, when I was on The Base 0.4 in that same configuration, my battery would drain maybe 1% an hour while I was sleeping.
Recently I've been on The Base 0.7.3, and my battery drains over 5% an hour while I'm sleeping. This means no screen on, no apps running, and even turning WiFi off! How does it use that much battery when it's not doing anything? Now, I'm not entirely sure what kernel I'm running. The first time I installed The Base 0.7.3 I used sk8's kernel. After getting poor battery life, I reflashed 0.7 and 0.7.3, this time choosing the freegee kernel. I'm not actually sure if the kernel changed though.
Anyway, I think I'll post again tomorrow with some screenshots from BatteryStats+ and CPU Spy.
I'm wondering if this recent botched update had the battery fixes we need. Hopefully they'll re-release it soon.
Click to expand...
Click to collapse
When I would get bad drain, which has happened several times, I could narrow it down to a couple things in order to solve the problem.
In my case it would always happen after installing Google+. Uninstall and reboot would usually fix the issue. If I got drain on a fresh install without g+ installed, I found that if I installed the 2.2 kernel separately as a stand alone zip, that would fix it. Don't know why but it may work for you too.
I don't have screen shots, but today I recharged at 38% after 3:10 of phone use and 1:55 screen on time and about 15 hours off charger. That's with Wi-Fi on the whole time and Bluetooth for about 9 hours. I have my work exchange account on active sync with push notifications. Facebook and Twitterer to 4 hour intervals. I'm underclocked to 1350 and using powersave gov with deadline.
Sent from my LG-E970 using xda app-developers app
jivy26 said:
Yea I've tried fdt but I think it has to be kernel related drain issues
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
Believe you are correct. There were issues on the Samsung Infuse and even the international SGS3 for a while... it was referred to as 'memory leak.' Has been worked out by devs on XDA. You can put memory leak in the XDA search above... it's above my pay grade.
Edit: It's great to see another RD here... hope you will reconsider keeping the phone and stay !!
Jank4AU said:
When I would get bad drain, which has happened several times, I could narrow it down to a couple things in order to solve the problem.
In my case it would always happen after installing Google+. Uninstall and reboot would usually fix the issue. If I got drain on a fresh install without g+ installed, I found that if I installed the 2.2 kernel separately as a stand alone zip, that would fix it. Don't know why but it may work for you too.
I don't have screen shots, but today I recharged at 38% after 3:10 of phone use and 1:55 screen on time and about 15 hours off charger. That's with Wi-Fi on the whole time and Bluetooth for about 9 hours. I have my work exchange account on active sync with push notifications. Facebook and Twitterer to 4 hour intervals. I'm underclocked to 1350 and using powersave gov with deadline.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. I have Google+ uninstalled, but part of me thinks Google Now may be partially the culprit (although why that would be the case with all radios off, I don't know).
I'll try a fresh install of the 2.2 kernel and see if that helps. Thanks.
I can't speak for anyone else but FDT did wonders for my battery life. I was only able to go about 12 hours prior to disabling FD.
Sent from my Optimus G
Digil said:
Thanks for pointing me in the right direction. I have Google+ uninstalled, but part of me thinks Google Now may be partially the culprit (although why that would be the case with all radios off, I don't know).
I'll try a fresh install of the 2.2 kernel and see if that helps. Thanks.
Click to expand...
Click to collapse
I always install GNow, love the inverted version.
Sent from my LG-E970 using xda app-developers app
johnbyebye said:
I can't speak for anyone else but FDT did wonders for my battery life. I was only able to go about 12 hours prior to disabling FD.
Sent from my Optimus G
Click to expand...
Click to collapse
This is good for sure... it's just that compared to other phones, Android OS and Android System should not be that high.
Pony Express said:
This is good for sure... it's just that compared to other phones, Android OS and Android System should not be that high.
Click to expand...
Click to collapse
That's what leads me to believe it's a faulty measure...
Sent from my LG-E970 using xda app-developers app
Jank4AU said:
That's what leads me to believe it's a faulty measure...
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
^^^ This is indeed worth considering.... I think the question then becomes why is it consistent among the 3 roms we are using? Maybe when JB source is out and something is built from source all will be good.
Pony Express said:
^^^ This is indeed worth considering.... I think the question then becomes why is it consistent among the 3 roms we are using? Maybe when JB source is out and something is built from source all will be good.
Click to expand...
Click to collapse
I would be less inclined to believe it is a faulty measure if we had a different ROM not built off stock (AOKP/CM10) that could produce different values. However, I seriously doubt anything built into either of the two custom ROM's is geared toward normalizing that reading. That's why they are both the same as the stock AndroidOS percentages. Jivy is probably right that it's a kernel issue. With the size battery we have, imagine the potential if it is a true reading (androidOS out-of-control) and we can get it under control down the road. We're talking double the current best battery life you've ever had on this phone at the very least.
Sent from my LG-E970 using xda app-developers app
+1
LOL
v
v
v
+43
Get BetterBatteryStats, select Since unplugged and Alarms to see what is waking the device (making it not go into a deep sleep). eBay was a big culprit for me.
The wakelock that keeps the phone awake during background data transfer (screen off) lasts 6 seconds (I am guessing it does it in multiples of 6s) regardless of how long the sync takes. Everytime email, facebook, gmail, drive, picasa, twitter, g+, google maps, ebay, calendar, contacts.. whatever wakes the phone to check something, it will be a minimum of 6 seconds.. This adds up over the course of the day and it is counted in the Android OS. Shut down syncs you don't absolutely want/need and this number will go down. All phones with the Snapdragon S4 Pro has it, especially the Nexus4. It seems they've done some kernel work to fix/reduce it but I havent really looked into it since I don't have that phone. I've seen complaints in the Droid DNA forum as well.
snacsnoc said:
Get BetterBatteryStats, select Since unplugged and Alarms to see what is waking the device (making it not go into a deep sleep). eBay was a big culprit for me.
Click to expand...
Click to collapse
This. EBay for me too. BetterBatteryStats is your friend.
Anyone else experiencing scrolling lag or delay. Clearing cache and wiping dalvik fixes it but the issue returns after about two days.
Sent from my LG-E970 using Tapatalk 2
jivy26 said:
Anyone else experiencing scrolling lag or delay. Clearing cache and wiping dalvik fixes it but the issue returns after about two days.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1987032
This RILJ wakelock on the dialer seems to be impossible to remove. I've tried everything from disabling all apps, turning off the phone and turning it back on with airplane mode, TWO factory resets, turning off all GPS and location services, and even shutting off my mobile data. I even did all of those steps at once and to no avail. I'm running stock right now but I seriously can not use this phone when this wakelock is disrupting my phone every damn second. I don't know if this is the right section to post this, but is anyone else experiencing this issue? Is there even hope? I've tried what feels like everything. I feel like this will drive me crazy to the point where I will just exchange the phone and claim battery problems. Again, sorry if this is the wrong section to post this in.
coobot said:
This RILJ wakelock on the dialer seems to be impossible to remove. I've tried everything from disabling all apps, turning off the phone and turning it back on with airplane mode, TWO factory resets, turning off all GPS and location services, and even shutting off my mobile data. I even did all of those steps at once and to no avail. I'm running stock right now but I seriously can not use this phone when this wakelock is disrupting my phone every damn second. I don't know if this is the right section to post this, but is anyone else experiencing this issue? Is there even hope? I've tried what feels like everything. I feel like this will drive me crazy to the point where I will just exchange the phone and claim battery problems. Again, sorry if this is the wrong section to post this in.
Click to expand...
Click to collapse
Whats the count & percentage being used by the RILJ Wakelock?
coobot said:
This RILJ wakelock on the dialer seems to be impossible to remove. I've tried everything from disabling all apps, turning off the phone and turning it back on with airplane mode, TWO factory resets, turning off all GPS and location services, and even shutting off my mobile data. I even did all of those steps at once and to no avail. I'm running stock right now but I seriously can not use this phone when this wakelock is disrupting my phone every damn second. I don't know if this is the right section to post this, but is anyone else experiencing this issue? Is there even hope? I've tried what feels like everything. I feel like this will drive me crazy to the point where I will just exchange the phone and claim battery problems. Again, sorry if this is the wrong section to post this in.
Click to expand...
Click to collapse
I have the same issue.
Sent from my HTC One using xda premium
Lenunited said:
Whats the count & percentage being used by the RILJ Wakelock?
Click to expand...
Click to collapse
Percentage I am not sure. Count is 47 sec at x1136 (usually around 1000-2000).
Blue1k said:
I have the same issue.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I know that feel bro. Might exchange the phone soon at the AT&T device center.
I'm having the exact same issue. I really dislike HTC phones, I've been dealing with bull**** problems similar to this on my HTC Sensation XE and One X for the past few days and it's annoying the crap out of me.
Anyway, I'm having this problem on my HTC Sensation XE, I've tried several roms already (4.3, 4.2, 4.0.3) and even flashed RUU to get it to run stock ICS rom with Sense, and all of them have the exact same problems. They all have RIJL wakelocks caused by either the Phone or the Dialer. I did everything (same as you did) including disabling Google Service Framework services etc, none of them helped.
Even in airplane mode, the RILJ wakelock continues to run. It drains my battery and it pisses me off. I've tried asking for help by sharing my BetterBatteryStats dump and did everything that others have suggested, on ALL the roms I've tried. None of them helped.
I even tried flashing different firmware, radios and ril for my phone. None of them made the problem go away.
At this point, I'm thinking it's probably a hardware problem with my phone.
RILJ wakelock is because of Android not HTC
calanizzle said:
RILJ wakelock is because of Android not HTC
Click to expand...
Click to collapse
Well, yes it doesn't have anything to do with the brand of the phone itself. It's just that based on my experience, all the HTC phones I've used have had RILJ wakelock issues. I've tried different custom roms and they all shared the same problems. My Sensation XE and One X had RILJ wakelocks since day 1.
My Huawei U8800 and Xperia Z had no problem whatsoever. So it leads me to believe it's some sort of hardware issue with HTC phones, which isn't surprising considering there are many.