I really like the feel of aosp on my s3, it feels smoother and alot more responsive. However I'm having a problem with each version I'm trying.
10.1.3
The voice typing keeps turning itself on, I'll keep turning it off and voila 10-15 mins later it turns itself back on. Usually after the display turns off. I have no idea how to permenatly keep it off.
10.2
The elusive RILJ problem. When his occurred I did read up on it, its not the location settings as they're all turned off and maps isn't the culprit cause I don't even have it installed. Whenever I check BBS it says RILJ (phone) and it literally drains my battery at the rate of 1% every 2 minutes with the 15 minute bus journey to work resulting in over 300 wakeups.
As I said I would love to use cyanogenmod full time but can't without these problems being solved. Ideas anyone?
I should mention that this on both the stable versions
Can you freeze voice typing in titanium backup or with another app from the play store. Can't check at the moment but im sure I have frozen it for this reason
Related
Hi there,
I've had my Galaxy Player 5.0 for over a month now, and it's been exhibiting a weird battery drain problem. I have everything set up to drain as little battery as possible when the device is sleeping. I've got auto-sync off, Juice Defender Plus to automatically disable Wi-Fi... it's working beautifully most of the time. I can go for days without the battery draining at all when I'm not using it. But then it inevitably hits a point where I turn it on and lo, like half the battery charge is gone. I check BetterBatteryStats often to monitor this problem, and it usually shows about the same awake time as screen on time, which is what you'd expect. When the problem kicks in however, the device shows hours and hours of extra awake time.
Two new kernel wakelock entries appear at the top:
gpsd-interface
GPS
Those account for pretty much all the extra awake time. I can break these wakelocks by turning on the GPS, starting Google Maps, letting it read my location, closing Google Maps and finally turning off GPS again. I never use Google Maps or GPS the rest of the time, but these wakelocks keep coming back every few days. I've searched everywhere for any mention of "gpsd-interface" and I found nothing.
Any idea how I might be able to fix this?
Thanks, Nir
I love Android.
I think the customization is great, and since v4 it's smoother and feels more responsive.
There are LOTS of apps and it's better than iOS.
But i'm sick of the battery issues.
I've always loved trying new features, ROMs, apps, hacks and whatever.
I now have SGS3 and it's my third android device, and i've installed ROMs dozens of times, even on my friends' devices.
One thing that always kept me alert is the battery life - the maximum I can get from my battery is around 30 hours with my usage - 1/5-2 hours of screen, ~45 minutes talk, lots of standby.
But every now and then, my girlfriend, my dad, my aunt or my friend ask me 'why does my battery drain so fast?'
Sometimes its google maps.
Sometimes its mediaserver/media scanner
Sometimes - and only I can see it cause they are not familiar with tools like BBS, it's gsf (Google Services Framework).
The point is, when you have an Android device, you need to check the battery stats every now and then to make sure nothing is unusually heavy on the battery.
I am currently experimenting with ParanoidAndroid and AOKP, which are faster and more responsive than omega/stock.
Yesterday i went to sleep (6 hours) with 25% battery (after it lasted 15 hours) and I turned off the data connection and the wireless connection.
I woke up after 6 hours (lucky..) and I saw my phone if off. after I connected it to the charger and turned it on I saw mediaserver decided to wake up in the middle of the night, after It almost did nothing during the day, and worked for 5.5 hours until the battery died!
Today I unplugged my phone and in 1 hour of standby 10% of the battery were gone, I checked what happened using BBS and saw gsf again (that GTALK_SYNC whatever wakelock) was draining battery, after I thought I fixed it yesterday when I disabled app data and browser sync in the google account sync options). I rebooted and now it seems ok again, the phone is back to ~70-80-% sleep.
I want to emphasize that I don't like all the stupid battery tips that tell me to castrate my phone:
turn off wifi when it's not needed, turn down the brightness, lower the screen timeout, disable sync (wtf? but its a smart phone, I WANT push notifications!) and that sort of things.
I KNOW I can get >24hours of battery without disabling the basic features of my phone.
And the draining battery processes that I mentioned earlier can suddenly appear even in a stock ROM, so I don't think it's PA or AOKP's fault.
What I want is that google will finally build a supervisor entity that will check what causes an unusual battery drain, check if it makes sense, and disable that cause!
It's absurd that google maps application comes with default 'enable location reporting' that constantly drains your battery and for what?? google maps doesn't run in the foreground, why the hell will I want that background location reporting draining my battery? and if so, why do you put this option enabled BY DEFAULT? The average user doesn't know this sort of stuff, and get only 10 hours of battery out of a device that should ideally provide ~30 hours!!!
Just wanted to let it out of my system...
And to get useful battery tips if any...
The elusive RILJ problem. When his occurred I did read up on it, its not the location settings as they're all turned off and maps isn't the culprit cause I don't even have it installed. Whenever I check BBS it says RILJ (phone) and it literally drains my battery at the rate of 1% every 2 minutes with the 15 minute bus journey to work resulting in over 300 wakeups. I would love to use cyanogen permanently but I can't until my battery works for longer than a few hours at a time
yusuo said:
The elusive RILJ problem. When his occurred I did read up on it, its not the location settings as they're all turned off and maps isn't the culprit cause I don't even have it installed. Whenever I check BBS it says RILJ (phone) and it literally drains my battery at the rate of 1% every 2 minutes with the 15 minute bus journey to work resulting in over 300 wakeups. I would love to use cyanogen permanently but I can't until my battery works for longer than a few hours at a time
Click to expand...
Click to collapse
It's not related to your location settings but I think the issue is with your radio. Couple of things you can do. Try the fastdormancy app from the playstore and disable fast dormancy. Also try switching to Edge. That should help too. Overall some amount of RILJ wakelock will be there.
P.S If its cynogenmod then try disabling emergency broadcasts. Its either in the message settings or in the dialer app settings. I'm not sure if there is a correlation but it did work in my case.
Hey guys,
I have a "little" problem with my S2. Whenever I leave wifi on and let the screen go off, my phone will get into SoD (sleep of death) and I can't wake it up. This will happen sooner or later.
I have this problem with every ROM I can think of. It's been a long time since I used a stock ROM, so I don't know if this only happens on Custom-ROMs.
Finding out that wifi (or my data connection) was causing those problems was a long process with a lot of frustration and trial and error (catlog won't work or doesn't show anything regarding the problem).
I tried to get rid of this problem with the APP "PNF - Push Notification Fixer" by reducing the heartbeat intervall of the wifi and mobile to 5 and 6 minutes (15 and 28 before) this seemed to reduce the frequency of the SoDs, but they are still happening.
I can get rid of the problem almost all the times with deactivating wifi when I let the screen go off or lock the phone myself. I get the same result when I turn off "Wifi optimization" in advanced wifi setting, but this is draining my battery pretty fast.
So basically I can use my wifi only when the phone is on the charger (no deep sleep at all) or if I turn it off when I lock the phone (something like 30 seconds can sometimes be enough to get the phone into SoD).
With data on and the screen locked I only experienced one SoD and this seemed to happen when I lost my signal at all.
So my conclusion is, that whenever I lose my data connection (might it be wifi or mobile) my phone does seem to get stuck in deep sleep at that moment or the moment it tries to reestablish the connection (the problem most propably got less after using PNF, because my router would kick my phones connection after a few minutes (10 would be my guess) of inactivity and this prevented a long enough inactivity. But they still happen (SoDs)). When I turn both wifi and mobile off and let it go into deep sleep this is no problem and no SoDs happen.
The SoDs were less but also happened when I were on CM11 M11 official, but got really frequent when I switched to Markox89's version of CM.
This is no rant or anything, I just want to get to the core of this problem and wanted to see/ask if there is something different in the Wifi module or wifi settings in this build and what could cause this very annoying problem.
Maybe someone else has this problem, too. Maybe my hardware is just faulty and I have to live with this :/
If it wasn't for this problem this ROM would run pretty smooth and flawless.
Does anybody else have the same problem or somehow knows how to get rid of it? This would get a lot of frustration out of my everday life :victory:
My setup right now:
- Markox89's CM11 Mod (22.11) (4.4.4)
- Lanchon's TRIM Kernel for CM 22.11 (same problem before using TRIM)
- Lanchon's Music bug fix (same problem before using Music bug fix)
- Modem: XXMS4
EDIT:
- XPosed with Xprivacy
- common apps like Threema, Telegram, whatsapp...
Tl;dr: my phone gets stuck in deep-sleep (SoD) if I leave wifi on when my screen turns off. no problem with mobile on or both data connections off. Halp?
@xhoster try to clean flash a rom and try it without all those apps you are using and then you can see or its app related or rom related. If it's rom related then I think some people already posted before there.
Also maybe try a custom kernel.
Try these things, I can't help you further then this atm.
Also mybe logcat the issue so you can read where it goes wrong.
FINAL EDIT: The problem seems to be the wifi driver all along!
Flashed the Apolo Kernel and this solved my SOD problem only had two since then and those seemed to be APP related!
Happy right now
It's seems to be the xposed framework! Tried it with a fresh installation after RomNuke and the phone was sleeping for 45 minutes and nothing happened, installed xposed and 10 minutes later I got a SoD. Tried it with the 2.7 beta 1 and the 2.6.1 stable version. Both gave me a SoD when I left wifi on...
Is this a known problem or has anybody ever had this problem?
When I tried it, I didn't even installed any modules, just the framework.
EDIT: I am going to test a bit more to see if it really is xposed or just the phone hanging whenever a connection is lost.
Hello! I've been trying to investigate battery drain issues on my Z5C (with nougat) for the last week. It's been quite the annoying experience, to be frank.
Here is a screenshot from Wakelock detector LITE: http://imgur.com/a/2Ljyv
As you can see, for about 13-14 hours, with 30 minute of screen time, these wakelocks have built up to numbers like 20,000, or 70,000, etc. I am not sure if this is normal, but to be fair it seems like it absolutely isn't normal.
I have only used the screen to browse google wakelock searches in these 30 mins, more or less, and to check the wakelock app itself.
Furthermore, I tried using Greenify and it did slow my screen turn-on time considerably. I uninstalled it. My delay with screen wake-up remained... It was a huge mistake to try this app as it seems to have broken my OS and introduced unexplained OS lag at random times, which I did NOT have before at all.
Do you think a factory reset can solve this?
I am starting to think about rolling back to 6.0.1 and staying there forever with root and xposed. This type of erratic phone behavior really plays a number on my nerves.
thanks for reading!
go back and just restrict every non-system sony/xperia and as much of the google things as you can without restricting play service/store or framework