yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Murphy7523:
I have seen this. To resolve I had to go back

to a factory reset. Currently on modem 0 1 3, no significant issues.
[ONE Original Android Development] zBear:
[MENTION=4800121]Sultanxda[/MENTION]

I am ready to report about some issues with latest rom/kernel combination

wifi/bluetooth problem

when phone connects to a bluetooth speaker, wifi drops off for a 3-4 seconds and then reconnects

and in general wifi doesn't work good with the bluetooth on

displaying battery %

it's is ok only if phone was charged in off state

if it was on and left in charger for more than 30 minutes after reaching 100%, that data becomes inaccurate (and if I make a restart after that kind of charging, things becomes even worse)

don't know why is t so, but I tested it 3 times with the same result

in the rest this ROM is the best for the OPO
[ONE Original Android Development] rashsalmn:
Hey! Just installed the ROM. Gotta little issue, when I try to open camera app, It force closes. Can anyone help me fix this?
[ONE Original Android Development] gfinockio:
Try a different gapps package?
[ONE Original Android Development] Khizar:
Try clearing camera's data. If that doesn't work, grab a log, we'd only be guessing without one.
[ONE Original Android Development] fradbari:
Hi, anyone can help me?!

I mount the 20151220 build and have this huge battery drain [emoji29]

Inviato dal mio A0001
[ONE Original Android Development] pSyLiquid:
http://xdaforums.com/showpost.php?p=64124030&postcount=7940 read this. As I see Google play services try to wake up your phone, so need to put some restrictions in the settings
[ONE Original Android Development] fradbari:
Thanks but I think that can been stopped some Google service... Can you help to find the correct service/process to stop?!

So also in latest build occurred this problems?

Inviato dal mio A0001
[ONE Original Android Development] zBear:
no

and didn't saw that on this ROM in latest (2 months for sure) builds

I guess it's your gapps to blame
[ONE Original Android Development] fradbari:
Probably are a gapp problem, so what's gapp are battery drain free?

Microg gsmcore is the only gapp that could be free from this type of problems, but are not stable, right?

Inviato dal mio A0001
[ONE Original Android Development] zBear:
I use TK GApps micro modular package and after installing it I also flash a Google WebView Addon Module from the same topic

for me it's the most stable combination with this ROM
[ONE Original Android Development] fradbari:
:( actually i mount the pico version, others app has been taken from play store..

So if you don't happen to you, could not be a gapp malfunctioning?

ps. last tk app update is the 2015/10 ? no more support?!
[ONE Original Android Development] pSyLiquid:
just go to the http://xdaforums.com/showpost.php?p=64124030&postcount=7940 and then switch off only wake up in Google play services. That's it
[ONE Original Android Development] fradbari:
But doing this notification like what's app are blocked?!
[ONE Original Android Development] pSyLiquid:
no
[ONE Original Android Development] zBear:
yes, in that case I think it could be other issue

fradbari, try that

I don't remember what causes the google play services error, but if it's "wake up" then enable it back and disable "keep awake"
[ONE Original Android Development] TaranQ:
How come this ROM doesn't have the flip to snooze Alarm options?
[ONE Original Android Development] pSyLiquid:
Error will be if u switch off exactly "keep awake", don't do it. U can off only "wake up"
[ONE Original Android Development] Valaran:
Hi ! I've got a strange issue this night ! As you can see in the pictures, huge drain of 30% in less than two hours. Phone on plane mode, no app un background switcher. Previous night was almost 0% in same condition. Dunno what happened. This is a random issue i faced sometimes with cm12 roms. Maybe a bug in plane mode ? You can see that phone is "active" during the drain but app list don't show anything spécial.
[ONE Original Android Development] NewKindOfWorld:
Running latest version with lightning caf kernel, was wondering if enabling phone encryption would cause any issue, or can be done safely?
[ONE Original Android Development] pSyLiquid:
read my previous messages (it's enough 2 last pages) ;) and then start searching which apps wake up phone.
[ONE Original Android Development] Valaran:
I've installed gsam battery monitor but i don't know if it will find what i'm looking for. I was using wakelock detector before but i can't get it work now.

I'm pretty sure about the fact that's a wakelock but damn i hate that so much !
[ONE Original Android Development] Flypants101010:
I am currently running the November 16 Build no mods etc, is it safe to dirty flash to the latest build or do i have to flash each incremental?
[ONE Original Android Development] djuliusl:
Just dirty flash the latest build.
[ONE Original Android Development] Bieniu:
I'm running Jan 7 build (clean flash) with no mods and my phone can't turn on mobile data when WiFi network loose internet connection. Any solution for that?
[ONE Original Android Development] zBear:
the december 20 build

AFAIK it all started after january 5 wifi firmware update
[ONE Original Android Development] geokilla:
Did some searching and I didn't find any updates since the last two months. It looks like F2FS is still not supported by the ROM or kernel? If so, are there going to be any plans to support F2FS?
[ONE Original Android Development] ikjadoon:
Has anybody ever had Cyanogen Recovery seemingly magically appear on their phone? I was rebooting to make a Nandroid and outta nowhere, Cyanogen Recovery pops up.
[ONE Original Android Development] Odysseus1962:
Yeah, it happens when you've been running the stock COS and have in settings under Developer Options - Update Cyanogen Recovery the radio button set to enable. Which is the default setting. Disable that setting if you use another recovery and it won't be overwritten.
[ONE Original Android Development] Sarabveer:
Anyone know if encryption works with the latest Jan7 build with Unofficial TWRP 2.8.7.0 build Jan11?
[ONE Original Android Development] ikjadoon:
I've been on Sultan's ROM since November, though, and installed TWRP then. I've already re-flashed TWRP. But, the setting was enabled--but I haven't used flashed any ROMs for months and TWRP was fine last week. You're not saying Sultan's OTAs can install Cyanogen Recovery, right, if that's left ticked?
[ONE Original Android Development] Odysseus1962:
Not that I'm unaware of. I've only seen this happen previously on Cyanogen OS and Cyanogenmod ROMs. If this happens on this ROM it's the first I've heard about it happening. It happened to me awhile back when I running COS, that's why I suggested it. Since it happened to you while running this one I guess that means that it happens here too. We both learned something.
[ONE Original Android Development] tamamma:
Hello, and thank you for this work. After few days i see that the battery percentage is not so accurate. From 10% the phone does the shutdown for very low battery. And it stays on 100% for a lot of time and then it drains fast.
[ONE Original Android Development] zBear:
[MENTION=4800121]Sultanxda[/MENTION] please take another look at this issue

besides unstable wifi/bluetooth/data connection in latest builds (after updating wifi firmware) it's the only bug that left
[ONE Original Android Development] mr.shme:
I have been running this rom for quite a while now and my battery has always been accurate. It only affects certain devices. What is the build date on your devices? Mine is July 11/2014.
[ONE Original Android Development] zBear:
it all started somewhere in autumn, I'm not sure when exactly

you can reproduce this issue if you'll discharge your phone to 15-10% and see how it goes from there

initial build was made may 28, 2015 ;)

I was on latest build and this issue was present

yesterday I've installed (again) the latest cyanogen snapshot 12.1 to be sure 100% that it's ROM-related problem
[ONE Original Android Development] Sarabveer:
Anything?
[ONE Original Android Development] jkmangang:
Sorry, this bug never affects in mine.. I usually discharge my battery till 5~10 %..
[ONE Original Android Development] zBear:
I think it's possible that we have some difference in hardware (something like different displays for our phone)
[ONE Original Android Development] gal_b:
What are the best Gapps that doesn't cause any kind of special battery drain?
[ONE Original Android Development] zBear:
I have no problems with TK GApps micro package
[ONE Original Android Development] bucketheadmjs:
http://xdaforums.com/showthread.php?t=3243307
[ONE Original Android Development] fradbari:
After the community help, I've updated, last day, my opo to latest cm build.

First I've do a full wipe (memory included) and than Flashed cm + gapp (tk) + ak kernel

Actually is the second days of battery, so is not reliable, but gapp drain persist! On airplane mod the consumption is 0.5%/h but on data raise to 2%/h. So if you can try other gapp, tell us if are better

On next days I'll tell you some screenshot

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] jkmangang:
Nano Tk Gapps, IMO
[ONE Original Android Development] zBear:
I used the same micro packege with SultanROM and latest snaphot, no drain was noted

may be it's ak kernel to blame?
[ONE Original Android Development] Odysseus1962:
To those having battery monitoring related issues, have you tried flashing Sultanxda's updated kernel that he posted a few pages back? Though I've never really had monitoring issues on my two OPO's with this ROM, I've been using it and it works great for me.

Another possibility for you folks to consider is that your battery could be getting worn. These devices have been out now for some time and the constant charge and discharge cycles may be showing effects as a normal sign of aging.
[ONE Original Android Development] Sultanxda:
No, I will not look at the battery issue again. See: http://xdaforums.com/showpost.php?p=64951228&postcount=7764

Try and solve this riddle: if you can't trust the only piece of hardware in the phone that supplies battery measurements, then where will you get your battery measurements from?

It does not matter if you "do not see this issue on a different ROM". I've seen this battery issue reported on even COS by several users, and if you still experience it with my new battery driver, then that is the last solid piece of evidence that this is a hardware issue and not a software issue that I can simply fix by pulling code out of thin air and adding it to the kernel.

Also, regardless of how you charge your phone, the fuel-gauge chip is supposed to provide accurate battery measurements, so it isn't valid to say this is a charging issue.

1. WiFi and Bluetooth operate on the same base frequency. I can neither fix physics nor physical design flaws. I tested 3 different Android devices, and they all suffered from even worse WiFi-Bluetooth coexistence issues than the OPO.

2. This is old news to me. I fixed the % rising after unplugging from the charger in a newer version of my rewritten battery driver. Everything else with the new driver was perfectly fine (% reported when the battery was actually draining was not inaccurate, at least as far as the kernel driver is concerned).

Here is the newest version of my battery driver: View attachment Sultan-kernel-CM12.1-New-Fuelgauge-Final_2016-01-26.zip

It does not have any known bugs at this time. Here's how it works: it asks the fuel-gauge chip for battery measurements, and reports whatever the fuel-gauge chip decides to give, while ensuring some things for a better user experience (but these things do not affect the accuracy of the reported battery percentage).
[ONE Original Android Development] fradbari:
I don't thinks, because on my oldest post, when I'm talking about a battery drain, I was on stock kernel.

This time I've flashed ak can kernel precisely for reduce kernel battery drain influence

So I need only to flash this zip or have to do a clean installation?

However the battery drain is grater on mobile data, maybe with a 3g-2g switcher the drain decrease. Any suggested app for this?

See this screenshot; most of the drain is caused by Google play service, that mark radio signal active!

How you see on idle period battery decrease 2-3%/h, so is only a report battery bug? Is is true, when my statistic show 5% of remaining battery?

Ps. My opo was replaced under warranty 2 month ago [emoji12]

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] zBear:
first I want to say that I understand all that and really appreciate all the hard work you made to make this phone even better

I'll not bother you again with this issue, this is the last time, may be it'll help:

yesterday I installed the latest snapshot (again) and when phone shuts down at 0%, I managed to turn it on several times and right after boot it shuts down

with your ROM, if I'll try to power on the phone like this, right away it shows "low power" image and doesn't boot

that's it

thank you once again for everything

thank you, I'll try that
[ONE Original Android Development] Odysseus1962:
[MENTION=4800121]Sultanxda[/MENTION] I've been using your new kernel for several hours with no issues, though I haven't experienced issues with previous kernels.

However, I've got a couple of questions; this ROM has been very stable for me and I've been using it for awhile. I use my handset extensively for work so I can't afford any hiccups, which is why I'm running this instead of your marshmallow ROM, which is still too immature for my purposes. My question involves the recent linix security bugs and CM. Are you planning on continuing to update this ROM as security fixes are added upstream or is this the final version we'll see?

Second do your recent kernels include the fixes Google recently released for the kernel or will they be incorporated in a future release?

I know SE Linix provides some additional security for the affected kernels, however, I've read that the added protection is somewhat compromised on rooted devices. TIA and thank you so much for your dedicated work on this still wonderful device.
[ONE Original Android Development] Sultanxda:
All OPO kernels are too old to be affected by this.

Install Ampere from the Play Store and see what the voltage is when your battery is at 100%, and then check it again right after your phone dies (you can just plug in a charger to make it turn on after it dies, and then check Ampere).

For me, I got 4.26V at 100% and 3.525V at 1% (healthy battery).
[ONE Original Android Development] ikjadoon:
OK, right, that's where my line of thinking was, too. Whatever...we'll chalk it up to random glitch. Safely back on TWRP, heh.

Thanks for the confirmation.

Seems like every few weeks, someone asks this, so I'll give a 1/27/2015 update: Xposed is working great on this ROM. I installed the v79 framework + Xposed Installer app last week (you want the sdk 22 + arm). Added a few modules, no issues. No bugs AFAIK: I'm surprised how easy it was, especially since others had had so many issues when Lollipop first launched.
[ONE Original Android Development] Odysseus1962:
Thanks for your quick and timely response. However are you sure this is the case? My research online indicates that the 3.4.0 kernel being a long-term stable branch has had the feature causing the issue back ported into the tree for some time.

Now I'm unfamiliar with when the CAF branch was forked from the mainline tree. If it was forked before its inclusion then it definitely won't have the bug, but if it was forked after inclusion it would contain it.

So am I correct in assuming by your response that the CAF sources on which you base your kernel was forked before its inclusion and therefore safe? TIA

And once again, thanks for all of your efforts in producing this outstanding ROM.
[ONE Original Android Development] ikjadoon:
I'm not Sultan and I don't know much, but a few other people have looked at the OPO kernels and they're missing the key lines of code that are needed for the exploits to run.
[ONE Original Android Development] Odysseus1962:
Thanks that's reassuring and greatly appreciated.
[ONE Original Android Development] Felgnon:
I have a bug that has been going for some months. I'm not english native, i'll try to make it understandable.

If i make a phone call, if i change it to speakers and then back to "normal mode", the microphone will stop working. I need to remake the call for the microphone to work again. It happens everytime.

If it's hard to understand i'll try to explain it again.

Thank you for this excellent ROM :)
[ONE Original Android Development] gfinockio:
That is completely understandable - if you switch from speakerphone back to regular mode, you lose your microphone.

I just tested that myself and I needed to go from normal-speakerphone-normal to replicate it, but yes - it is an issue. Wow, that sucks.
[ONE Original Android Development] m@++:
I've been experiencing that bug myself lately. I chalked it up to being a side effect of an auto call recorder app I've been using, but maybe it's not to blame.
[ONE Original Android Development] zBear:
I can't reproduce it

tried to switch to speaker before the call and back during the call, then switched to speaker and back during the call - everything works great
[ONE Original Android Development] atakanyildiz:
Music player have some bugs for me : Sometimes gestures, earphone remote and long press on volume buttons to change song doesn't work. I'm on latest version.
[ONE Original Android Development] real_sl4cker:
On my side it's even worse. Phone shuts down automatically when below 30%. Few days ago it did it below ~23%. After plugging it in in my car and drove home it was at 33%, after a few minutes idle I picked it up and it was off again. Plugging it in and waiting for it to boot (after the low battery screen it showed 30%). Seems battery measurement in Android isn't accurate.

EDIT: Should have read the rest of posts before replying. Sorry, will try the new battery driver

(mobil gesendet / sent from mobile)
[ONE Original Android Development] zBear:
phone was shutting down at 2% so I didn't manage to obtain the minimum voltage:

100% - 4.276V

50% - 3.802V

2% - 3.236V
[ONE Original Android Development] Felgnon:
Actually, this could be it. I also have a call recorder installed. I'm going to test again without the app after i leave work.
[ONE Original Android Development] naufaldroid:
[MENTION=4800121]Sultanxda[/MENTION] I flashed the ROM today. No probs so far. But I found GPS issue. Its not showing my location on Google maps. Any thoughts?
[ONE Original Android Development] samaritan16:
[MENTION=4800121]Sultanxda[/MENTION]

By any chance will you be updating the camera libraries as oxygen 2.1.4 for the one has released? Just curious.
[ONE Original Android Development] ReWoP1:
Hi, i've not testes the new battery driver but i had exactly the same issue as you, my solution was install Battery Doctor app by Cheetah Mobile Inc and do a full charge, after that all was ok.

Hope it helps.
[ONE Original Android Development] zBear:
I only had one discharge, but phone shut down at 2%, which I consider much better than shutting down at 15-30% unexpectedly

P.S. the second time phone shut down right after showing 15% alert :(
[ONE Original Android Development] parvesh:
he has already explained, plz use search from next time for now below is link ...:)

http://xdaforums.com/showpost.php?p=65013900&postcount=122
[ONE Original Android Development] bebybee:
It work on me

No gps issue
[ONE Original Android Development] fradbari:
Hi, it's normal this consumption on idle state?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] easy_mac:
1-1.5% per hour on standby is normal for me
[ONE Original Android Development] samaritan16:
Thanks for the reply, but you do realize that the thread you're quoting is an entirely different thread (though it is related to the camera hal).. Anyways, my question is answered, so thanks!
[ONE Original Android Development] fradbari:
So less than 1.5% of battery drain on mobile data is impossible on lollipop?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] dralways:
I'm on lollipop and see 0-1% drain per every night of standby while I sleep (6-10 hours) so 1% per hour would make me crazy. I'm on an official cm12.1 ROM though.
[ONE Original Android Development] TaranQ:
No I have the same problem although I have set a tile for the torch in the notification panel it doesn't appear!
[ONE Original Android Development] fradbari:
I know, so on mobile data the battery drain grows to 1-2%...my question is why!

Generally CAF Rom have less battery drain than others, so if you are on official cm12.1, typically, this sultan cm12.1 Rom should consume less than yours official; it's not true?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] Oneplus#:
hi whit this build (cm-12.1-YOG7D-20160107-STABLE-Sultan-bacon.zip) it remain in boot loop is only a my problem ? whit the previos version it work
[ONE Original Android Development] fradbari:
Have you done a full wipe? Or are you updating previous version?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] bhanuteja200bc:
can any one tell me a way to make settings app to have dual paned(two coloumns) ..i have seen that on darkobas rom..is there a xposed module to do that..i did try to search ..but couldnt find the answers?...
[ONE Original Android Development] easy_mac:
Not impossible, I just checked my battery and lost 4% over 8 hours last night so it's more like .5% per hour. I do have snapchat and some other apps like that though so depending on your apps it will vary.
[ONE Original Android Development] AndreIrawan97:
Anyway, i'm using OOS 2.1.4 now, the battery life is superb !
[ONE Original Android Development] naufaldroid:
Did you install it via twrp? Or any other methods?
[ONE Original Android Development] Sultanxda:
4.276V at 100% is healthy.

3.802V at 50% is healthy.

3.236V at 2% while discharging at 450 mA is not healthy. Voltage readings can drop if your device suddenly starts consuming a lot of energy (e.g. turning on the flashlight, setting screen brightness to max, etc.), but we could notice that by looking at the discharge rate. Just like you, I took my voltage measurements while my battery was discharging at ~400 mA, so if your battery were healthy, then your voltage readings at 2% should be much closer to mine (~3.5V).

Your battery looked healthy until the percentage started getting low, so there's no reliable way to work around this in the kernel. If a good kernel workaround were implemented (which I can't do), the only difference would be that instead of your phone shutting off at 20%, it would suddenly drain from 20% to 0% very quickly. This could be a bug in the fuel-gauge firmware (maybe it reports that your battery has a usable charge remaining, when it should say that it's dead), but we'll never know.

Maybe it's time to get a new battery?
[ONE Original Android Development] Bobbi lim:
There's something call MRA - Mobile Radio Active bug present in any ROM that's 5.x and above.

Read about MRA here: https://code.google.com/p/android/issues/detail?id=190396
[ONE Original Android Development] fradbari:
So MRA was not solved, but i don't understand if it's a gapp problem, an android system problem o both :mad:

Seems that some people don't have this problem, and consume 0-1% of battery on mobile idle

Do you have the MRA bug with OS?
[ONE Original Android Development] AndreIrawan97:
Yes via materialized twrp
[ONE Original Android Development] zBear:
I agree, but please explain this data:

100% - 4.259V

50% - 3.832V

1% - 3.604V

same apps, same settings, same everything, only the ROM is latest snaphot from 17 november

I understand all that and I already bought the new battery, but I am still not sure if it's the battery causing all the trouble
[ONE Original Android Development] Quasar:
AFAIK PA is more or less CM based for non Nexus devices.

By CM based, I mean that they do what CM did. Take vanilla CAF sources and mess around with those.