yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] PeterFdeVries:
I found a way tot fix this for the WiFi part (and strangely also mobile). Go to WiFi settings, go to advanced and than choose WiFi region and set it right. Getting much faster speeds after this... Try it :)
[ONE Original Android Development] benthomp85:
WiFi is at the top of my battery usage for the last few days.

I have just turned off wifi and bluetooth scanning in location settings. Hope this helps.
[ONE Original Android Development] chipyy94:
It works, thank you very much ;)
[ONE Original Android Development] georgek_gr:
Ok, here's MY opinion regarding doze and its results on MY device.

I have used this ROM as my daily driver since early December and it was good enough then already. I haven't had any notification issues with previous builds (been on sultan's ROM since the first versions), neither have I had any battery issues, draining processes etc.

I can only say that on the Jan. 17th build my phone would lose a mere 0,3% - 0,4% per hour over night with "aggressive doze on" when using Naptime and 0,5% - 0,7% without Naptime (WiFi always on, location in battery saving mode, a few processes disabled following some recommendations in this thread, using e-mail, whatsapp, viber, FB messenger etc.).

With the Jan. 24th build, it's 1,2% - 1,4% per hour. Nothing to compare for me, but like I said I never had any notification issues in the first place.

Therefore I would be happy to see a doze on-off toggle like Sultan said and everyone can decide for themselves to use it or not.

[MENTION=4800121]Sultanxda[/MENTION] thank you for all your hard work and time put into this project!
[ONE Original Android Development] david72262:
Is this why USB otg storage has been hit and miss lately previous build worked sometimes, last build haven't been able to use at all have to use backup of 12.1 to transfer files to otg storage.
[ONE Original Android Development] 69gm:
Interesting how Doze is the subject of this inquiry...and the timing of Sultan's tests...

http://www.xda-developers.com/what-do-you-think-of-marshmallows-doze/

Remember folks...like anything when it comes to custom ROMs...YMMV!
[ONE Original Android Development] Lucaman89:
I have two issues.

I don't have volume regolation sound, when you move up or down the volume.

Also I can't change music track with the volume keys, even if it is select do to so.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] GraddySK:
Guys what about Mi Band with newest 24th build? Its working? I running on some 14th and there is not

Odoslané z OnePlus One
[ONE Original Android Development] York_21:
The notification Headsup are WIDER in the latest build (24/01).

In landscape they look awful
[ONE Original Android Development] PhillyFlyer:
Apologies if mentioned earlier, or anywhere else in thread, but I am getting some "screen burn" on the left and right sides of the screen on latest, and previous build.

Does anyone know if there is a setting that I can adjust to diminish or remove this issue? It looks like white burn along the sides of the display from top to bottom. Was hoping there was a fix...

*please see attached pic, I tried to capture it the best I could, but its very visible at all times and it is ONLY with this ROM. I have tried several. BUT I WANT TO BE HERE!!!

[IMG="imgur of OPO screen burn on sultans build"]http://i.imgur.com/zuirANA.jpg[/IMG]
[ONE Original Android Development] xeeee:
Yes, working fine on the 24th build.
[ONE Original Android Development] lynxboy:
Finally! Someone else has noticed it. I've been seeing the same thing. If I'm in 'Alarms Only' mode and reboot, sounds play until I toggle 'Priority Mode' and then 'Alarms Only' again. That's all I'm doing for the now. It's not a deal breaker; I'm just hoping I remember to do it before I head into meetings at work!

Regards.
[ONE Original Android Development] madsponge26:
The yellowish thing.. Change the rom and check if still there maybe hardware problem.
[ONE Original Android Development] ming3r:
Isn't that light bleed?

Screen burn would be that the image would be retained on the screen semi-permanently, very much like my old Galaxy Nexus
[ONE Original Android Development] PhillyFlyer:
Not the yellowish thing, the bright white vertical light burned into the sides of the screen (looks like something from burn tool from photoshop)

YES - light bleed. SORRY! It ONLY happens on this ROM and I can't understand it. Is there anything I can do to investigate and resolve?? I love this ROM.
[ONE Original Android Development] hermit911:
Bluetooth issues, cannot connect pebblebee
[ONE Original Android Development] KnightGalahad:
CAF RAW?

Sorry if this has already been asked on this thread, but does the CAF camera support RAW (Is there any way to turn it on)? I love the app, but it would be nice to know if it does or not. :D

Cheers,

KnightGalahad
[ONE Original Android Development] Elvecio:
Nope, it doesn't.
[ONE Original Android Development] ming3r:
[MENTION=4800121]Sultanxda[/MENTION] I don't know if its placebo effect or not but my battery is about the same without Doze and I think my Hangouts notifications are more consistent. Disa is about the same but I was getting those before.
[ONE Original Android Development] _Raziel666:
So, what has been the general consensus? Should we or should we not flash the latest (December 30th) H2O firmware?
[ONE Original Android Development] aliffaminuddin:
guys, i need help. im trying to flash this rom but it still stays that error in updating binary in zip, ive already flash cm13 nightly first then wipe system then flash this rom but still had the same error.
[ONE Original Android Development] bleached:
Hi there! This seems to be a known problem with some panels. look some pages back. Or search for "white patch". IIRC sultanxda said that he had tried in the past to solve this but he didn't make it, and that it seems to be kernel related.

I think all CAF ROMs have this problem too, but I might be wrong.
[ONE Original Android Development] Sultanxda:
Test this ROM: http://xdaforums.com/devdb/project/dl/?id=13820

Yes, that's CM12.1. Test it thoroughly (turn the screen on and off, play with it for an hour, etc.). If you still see your light bleed with that build then it's something I can't fix without having an affected OPO.
[ONE Original Android Development] DD9200:
Hi guys, I still have the battery optimisation part of doze in my settings, is that redundant or does that mean doze isn't off for some reason?
[ONE Original Android Development] hasnol143:
So on 24/01 battery life has been the same for me. But now my notifications are coming in on time
[ONE Original Android Development] highdiver_2000:
YEMV better fit

---------- Post added at 08:27 AM ---------- Previous post was at 08:25 AM ----------

I am on the H2O modem and it is great in SG
[ONE Original Android Development] ketplunk:
Hi, I'm getting "Unfortunately, Settings has stopped" when I try and open Battery in the settings, couldn't find anything when I searched the thread, so sorry if it's been asked already!
[ONE Original Android Development] RashidD:
Guys I have a bit of an unrelated question. Has anyone found significant gains by undervolting?
[ONE Original Android Development] renaltosonylevi:
It may be helpful to know what display panel your phone has. My phone has a JDI panel and I have managed to avoid any display issues. As far as I know there are at least 3 variants.

---------- Post added at 01:14 AM ---------- Previous post was at 01:04 AM ----------

Not on my phone. But I won't rule out that someone else may have gained something.

I tried it hoping to have a cooler running cpu, thus better benchmark results. Instead the reverse happened. After that I reluctantly decided may be snapdragon knows best.
[ONE Original Android Development] aliffaminuddin:
help guys :(
[ONE Original Android Development] 69gm:
LOL!:good:
[ONE Original Android Development] debsahu:
It is not a ROM issue, it is a theme issue. Just revert your theme to system default and now you can open the battery app.
[ONE Original Android Development] ketplunk:
That did the job, thanks a million!
[ONE Original Android Development] o0vampire0o:
First of all you need TWRP 2.8.6.0, not later. You can use TWRP materialized too if you want.

If you have this recover in order

-flash cm13 nightly

-flash sultan's cm13

-eventually flash opengapps

Reboot.

You don't need to wipe system just flash
[ONE Original Android Development] mubharad:
Awesome battery performance so far. Only 30% drained in 24 hrs since the last charge with about 2 hrs SOT in the same time period. Memory usage is high though, 2GB used inspite of greenifying heavy apps. Not necessarily a ROM issue, just my observation.
[ONE Original Android Development] aliffaminuddin:
yes im using the exact twrp you said, and already done what you said. still getting the error. error executing updater binary :(
[ONE Original Android Development] o0vampire0o:
Do you have this error when you flash cm13 nightly or sultan's rom?

Edit: have you tried a factory reset from recovery?
[ONE Original Android Development] aliffaminuddin:
i dont have any error when flashing cm13 nightly, just sultans cm13 and i already did, wipe cache, data, system
[ONE Original Android Development] ks_manish:
Flashed 24012016 build over oxygen os 2.1.4, now my baseband is showing as .4.0.1.c7-00013-M8974AAAAANAZM-1. Can someone confirm if it is latest baseband or I need to flash h2os firmware?
[ONE Original Android Development] Medvosteri:
Did you flash CM13 and RIGHT AFTER that flash sultans rom?

If you wipe system after flashing cm13 you'll just remove the reason why you just flashed cm13 anyway, you'll remove the needed firmwares (if i'm correct).

In this order:

Wipe System, Cache, Dalvik.

Flash latest CM13

Wipe only system (advanced wipe, check system only)

Flash Sultan

Flash supported GApps

Reboot system

Hopefully this helps you further :)!

Edit: Corrected process to match official instructions.
[ONE Original Android Development] aliffaminuddin:
i will try this out and tell you if its working :) thanks btw

edit: now i finally have this awesome rom running on my one, thanks :)
[ONE Original Android Development] Khizar:
The latest is 00011, CM downgraded it in the newer nightlys.

Wrong. Wiping system doesn't wipe FW. If it did, everyone that clean flashes updates would get errors.
[ONE Original Android Development] ks_manish:
CM downgraded from 00013 to 00011, it means 00013 has some problems. Right?
[ONE Original Android Development] bulletmark:
It sounds like he didn't flash CM13 but your instructions are wrong.

Guys, read Sultans short instructions in the OP here. He says literally "download and flash the latest official CM13.0 nightly. Then, without rebooting from recovery, wipe /system and flash my ROM".

Installing CM13 is done simply to update the firmware partitions which Sultan's ROM does not include. As I said just earlier here, even if you don't install CM13 you can just manually run those 8 fastboot commands I quoted at any later time to update the firmwares and you get the same result.
[ONE Original Android Development] Medvosteri:
You're correct, but i've never done that and always ended up with a perfectly working rom.

However, its indeed better to follow the official guidelines. (I'll edit my post just in case)

Then I can't explain why his install is failing.

Thx for the correction :)
[ONE Original Android Development] bulletmark:
FYI, I am an absolute stickler for following process. In fact, it got me an undesirable result as I followed Sultan's instructions EXACTLY as he stated, i.e. his 1st paragraph says literally "Next, try flashing the ROM and see if it installs; if it installs without any issues then congratulations! Now just flash a Google apps package, and then reboot." I had no issues so I thought my new Sultan install was perfect and proceeded to setup apps etc. Later on I learned that that procedure is deficient because it does not update the firmwares and you are left with whatever ancient firmwares you started with. In my case everything seemed to work ok but I researched the net and worked out that I could simply fastboot flash all the firmware files directly. That is actually good to know because it means I can update my firmwares easily at any later time if CM13 releases later firmware fixes/improvements.
[ONE Original Android Development] threetwentyfizzle:
Not trying to beat a dead horse with the Doze argument, but I thought it would be interesting to share my results for today, which I was TOTALLY UNAWARE of Doze being removed with yesterday's build until just now after reading up on several pages of missed discussion over the last couple days. So, this is about as unbiased results as you can possibly get. I have similar usage and drain patterns as the quoted post above to kind of put into context my typical phone usage.

Today: after unplugging and leaving the house I commuted almost an hour in the car to work with my phone synced via Bluetooth audio and when I got to work I was surprised to see my battery still at 100%. I proceeded to go about my day using my phone extensive enough, accessing Google spreadsheets, emails, texts, calls, etc and was surprised to see my battery level still at 80% near the end of the day about 4. A little better battery life (but fairly similar to last several builds)

Now the battery readings: Battery consumption seems about average to past builds, but I do show today's usage shows my phone being in more "awake" states for longer than what I typically see on previous builds, but less wakelock times on Google Play Services and Android System.

Hope any of my observations are found to be helpful in any way. Smooth, responsive, and snappy as always tho.

TLDR: not much of a noticeable difference in battery drain for me (at least right now, initially). Would like to see how a couple more charge cycles go to compare.
[ONE Original Android Development] Sultanxda:
The procedure is not deficient; I don't want everyone to update their firmware. New firmware doesn't work on some carriers, so the default installation instructions I provided avoid upgrading the firmware (as I intentionally allowed the use of Lollipop firmware).
[ONE Original Android Development] XBrav:
I've noticed with the latest nightly, far more apps are keeping the phone awake. I've gone through a couple of discharges today.
[ONE Original Android Development] PhillyFlyer:
Thank you sir - I will test this tomorrow morning and report back. [MENTION=4800121]Sultanxda[/MENTION]
[ONE Original Android Development] rednit:
A quick question befor flashing this rom.

i am currntly runing the new Oxygen rom V2.1.4 with root and recovery V 2.8.6

can i just wipe my current system and flash this rom, or should i flash CM13 nightly first and only then flash this ?

thank you
[ONE Original Android Development] Khizar:
I'd flash the CM nightly first. Not sure what FW/baseband oxygen has baked in.
[ONE Original Android Development] mikronac.ns:
[MENTION=4800121]Sultanxda[/MENTION] There is some ugly bug, both, in CM12.1 and CM13 when power button stops working and you can't lock/unlock phone. I am using volume rockers to wake it and status bar to unlock it. Long press also doesn't showing menu, so it isn't possible to reboot phone. I am doing that with terminal and after reboot everything is working again. And after some time is stops again.

Also, double pressing powerbutton starts camera but single pres will not wake up screen. Aaand double touch to wake also isn't working... Odd.
[ONE Original Android Development] P1f:
Also happened to me, power button stopped working but a restart always seemd to fix it.

I used an app for restart, there are plenty in the Play Store
[ONE Original Android Development] aliffaminuddin:
guys, i flashed the disable underlock but still the max cpu is 1574mhz is this true?
[ONE Original Android Development] mikronac.ns:
It's annoying, at least for me. It seems that it stops working when phone is running over 2 days without reboots.
[ONE Original Android Development] Al-Azraq:
Battery for me is far way worse than in previous builds, I do not why but I assume that is Doze deactivation.
[ONE Original Android Development] SubNoizey:
Battery life is horrible without doze, I've gone from 6hr SOT to 4 if I'm lucky.
[ONE Original Android Development] Dzhedaj:
Doze has nothing to do with SoT.
[ONE Original Android Development] Al-Azraq:
Not directly, but as it improves the stand by consumption it indirectly does improve SOT.
[ONE Original Android Development] Ne0x86:
battery for me stills same with or without doze :|
[ONE Original Android Development] EotT:
Battery life is a bit better for me in this build. Normally, I get 5h30m sot, but now it was 6h. I don't have apps that keeps my phone awake for a long time, so maybe I get some extra juice because no computations are done for doze?

But this is just my conclusion for the first day. Let's see if I get the same results in the next couple of days.
[ONE Original Android Development] binzianer:
Though it's not super bad, but for me battery life also decreased in the latest build, Spotify is suddenly keeping it awake longer more than I listen to music
[ONE Original Android Development] Notor1ouS-:
battery is exactly the same as before with doze.

some ppl have just major problems with their phone...
[ONE Original Android Development] gkillerx:
Fine here witouth finally gmail notifications arrive again.. keep it like this please.

Also I am trying to figure out if this is an phone issue or something else. Regarding AD2P bluetooth.

I have the following:

TomTom Rider

Scala Cardo Q1 (headset)

Oneplus One

ONEPLUS CONNECTED TO:

TOMTOM (for instrucations and calling)

RIDER Q1 (for music)

Rider Q1 (headset) connected to:

TOMTOM (for instrucations and calling)

PHONE (for music)

for some reason, the audio is really really bad when calling (could be because it's routed trough the tomtom Rider....) but I thought, why not ask if someone else perhapse has also a bit of bluetooth audio issues.

Tested with an Galaxy S4 same setup (no CM13 or any custom rom, STOCK) and it's noticeable better.
[ONE Original Android Development] rajesheber:
With this new build Wifi thetering seems to be broken. The portable wifi keeps dropping every alternate minute. Any solution to this.
[ONE Original Android Development] extrem0:
Working fine here. I had this issue when doze was enabled, so I had to keep screen on, but now it's working good.
[ONE Original Android Development] FSadino:
What was the idea by disabling doze? In my case, it does not affect me because I'm in constant move on my work but why disable that feature?
[ONE Original Android Development] SanOne+1:
On 24 build even if doze is disabled, still I missed Alarm
[ONE Original Android Development] binzianer:
Didn't notice / have this issue so far since I wasn't on cellular data. But I can't receive or send messages in WhatsApp with mobile data.

I'm on the c7-00011 modem from the 20160104 official nightly, sultan 24 jan built. Anyone else facing this?

E: just to stress that it's not about notifications, i can't send messages even though I have working network
[ONE Original Android Development] ChefChaudart:
it has been explained. Do read.
[ONE Original Android Development] FSadino:
*Disabled doze and app standby (time to grab your pitchforks and torches)

You are talking about this?
[ONE Original Android Development] benthomp85:
No, read the thread where it has been discussed and explained by Sultan
[ONE Original Android Development] easy_mac:
http://xdaforums.com/showthread.php?p=64966819
[ONE Original Android Development] Elvecio:
I dedided to stay on the latest version that includes Doze. And I have to say: I never missed a single notification. Even alarms work without issues. But... phone calls sometimes don't produce any sound. The last time happened a minute ago. I was lucky to see the display turning on with the incoming call, but no sound was reproduced. As I said a lot of pages ago, the problem might be linked to another one: most of the times, there's no sound preview when you choose the call ringtone in the settings.

It's an issue that persists from update to update, since the first time i flashed the Sultan CM13. And I know that it's not related on the latest build, but I think it's important. If it persists, I'll be sadly forced to return stock.
[ONE Original Android Development] Overdose1986:
Hello, Im new to this rom, everything works fine for me, but the washed out screen really bothers me

Does anyone knows a kernel compatible with this rom that supports screen color calibrations? I mean saturation and contrast
[ONE Original Android Development] TxdAndroid:
Use Kernel Auditor and adjust Intensity and saturation
[ONE Original Android Development] runderekrun:
Or people just use their phone differently? My phone is basically on standby for 8 hours while at work. In this instance Doze will help immensely with idle time.
[ONE Original Android Development] WarlockSyno:
Does any one else get choppy video during recording and playback on 1080P for the Google Camera? I think it does the same thing on the Snapdragon Camera.

[YOUTUBE]DZ7RzUCOiJM[/YOUTUBE]
[ONE Original Android Development] mcgrabowski:
FWIW - My experience with the Doze saga here.

I had been noticing missing notifications. I primarily noticed them in hangouts, but I feel it was probably elsewhere as well. Just wouldn't have been as noticeable to me other than in hangouts. The removal of Doze I think has corrected that. And honestly hasn't seemed to impact my battery life at all so far. It almost seems that my battery life might have gotten better in the latest build without doze. But I don't know why that would be attributable to doze being removed. Maybe there was something else changed in the latest build that helped that.

On another note, does anyone else notice that when first opening recents (as in first opening it after some time since the last you've opened recents) that it doesn't show the correct most recently used apps, but then closing it and opening it again shows the correct apps? I'm pretty certain this is not at all exclusive to Sultans rom here, as I'm positive I had this same thing in stock CMOS as well, in lollipop. Just wondering cause I don't think I've ever seen anyone else mention it, which I thought was odd.
[ONE Original Android Development] expiredd:
Same here, lot of Spotify wakelocks.
[ONE Original Android Development] RRuszczyk:
I haven't installed the latest update, but my experience with missing notifications (hangouts being the worst offender) was because for some reason when hangouts and other gapps are installed as system apps, it won't kick out of doze, even if you have it exempted. By switching my gapps install to one that didn't include hangouts and installing hangouts from the play store and then exempting it, I suddenly had notifications again.
[ONE Original Android Development] debsahu:
For the people on Jan 24th ROM with the need to use the file manger can flash the zip from http://xdaforums.com/android/apps-games/app-cyanogenmod-file-manager-apk-v1-0-2-t3058506 [MENTION=4800121]Sultanxda[/MENTION] has mentioned its a bug arising from CM changes and will be fixed in the next build. For those who cant wait, they can flash the above file manager (v3) zip.
[ONE Original Android Development] mikronac.ns:
[MENTION=4800121]Sultanxda[/MENTION] also, WiFi connection is very unstable. I am getting disconnections and switching to data connection. Several seconds after, I have WiFi connection again.
[ONE Original Android Development] mcgrabowski:
What firmware are you using?
[ONE Original Android Development] mikronac.ns:
Latest.
[ONE Original Android Development] mcgrabowski:
Latest CM? Oxygen or Hydrogen?
[ONE Original Android Development] mikronac.ns:
Latest CM.
[ONE Original Android Development] mcgrabowski:
A lot of folks seem to have good luck, myself included, with the Hydrogen firmware linked in this post.

http://xdaforums.com/showpost.php?p=64285972&postcount=4816

Whoops, that link looks dead now.

This link still looks good yet.

https://www.androidfilehost.com/?fid=24352994023703384