yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Khizar:
QS tiles are buggy on the latest build, they work some and don't for others. It's a CM issue, offical nightlys have the bug as well.

Don't have this issue.

Greenify the app.

It isn't that they can't fix it, they just don't care about android. Their ios app is a lot better.

Just for the record I haven't had any issues with fb for a while now, no battery drain and no freezes/crashes. Knock on wood.

Are you sure you didn't enable priority mode? That doesn't disable system sounds.

Which gapps?

Clean flash?

If dirty, did you flash gapps as well?

Do a clean flash and use open gapps.

If you have a perfect phone, no need to update.

Xposed module CM settings.

Is Gmail a system app? Try uninstalling and reinstalling from play.

If that doesn't help disable doze for Gmail.

Known CM bug. QS are buggy.

Either need to reset apn or network/sim issue. It isn't a rom issue.

Clean flash.

No issues on offical CM?

If you flashed latest CM offical, then you're on the latest modem.

Go into privacy guard and disable google play services keep awake and start on boot.

WHY ARE YOU SCREAMING?
[ONE Original Android Development] dendi:
SORRY ? can u help me out brother ?
[ONE Original Android Development] evanovici:
it's play services that's eating your battery, nothing to do with ROM. I don't see anything outstanding in your stats either (for MM anyway). Try and limit some services with Amplify or any other app
[ONE Original Android Development] PlayersHeaders:
I already tried with the setting data protection
[ONE Original Android Development] PlayersHeaders:
I'll try Amplify. Which Xposed zip i need?

http://xdaforums.com/showthread.php?t=3034811
[ONE Original Android Development] skeetzor:
Still having this problem. Using twrp 2.8.6 and I've clean flashed etc. Just randomly my phone calls cutout, as if I'm hanging up on them. Frustrating.
[ONE Original Android Development] evanovici:
Must remind you of XDA rule no. 1. You're cluttering the thread and finding the answer to your question involves but a simple google search

xposed-v79-sdk23-arm.zip - sdk 23 is MM, arm is for bacon
[ONE Original Android Development] Lamner:
Same here, very annoying
[ONE Original Android Development] benthomp85:
Get a new screen/phone ;)
[ONE Original Android Development] dendi:
dont you see that i mentioned happen only on sultan rom and darkbos rom ?
[ONE Original Android Development] benthomp85:
Don't you see the winking face....?!

I doubt you will get much help here as it isn't something affecting others and sounds hard to believe it's the ROM at fault.
[ONE Original Android Development] hmzuleta:
Ok, could you be more specific? Wipe everything, then flash latest nightly then the ROM + gapps, right?

Could I just backup my current data partition, do what I said just now, then restore data? Or do you recommend a fresh start and restore what I need with Titanium Backup?
[ONE Original Android Development] ryanmat:
Have either of you tried flashing a different modem? Looks like CM is switching back to the old modem as well: http://review.cyanogenmod.org/#/c/128876/ Try flashing the latest CM nightly with Unofficial TWRP or TWRP 2.8.6.0, then flash Sultan on top to go back to the old modem and see if that helps.

I think there might be one or two other people with the same washed out color issue. Sultan uses a different LCD display driver, which might be causing some issues on devices that have a flawed/older touchscreen. I don't notice it on mine, but my OPO is pretty new, and maybe I got a better touchscreen?

I think he's suggesting do a fresh start, don't restore your data partition. Use Titanium, or even Google to save and backup.
[ONE Original Android Development] legion2k6:
Is this right?
[ONE Original Android Development] renaltosonylevi:
Try and find out what type of display panel your phone has. There is at least 3 variations I know of. This problem might be specific to your device variation.

That would explain why some roms are good and some are not.

Sorry you will have to search for instructions as to find out your panel type.
[ONE Original Android Development] gaspolo:
i have DI3.0.c6-00241-M8974AAAAANAZM-1
[ONE Original Android Development] bleached:
Hi there! [MENTION=5104904]thepico[/MENTION] I also have the same problem! Check previous posts of mine in this thread.

I will also try to find my panel version.
[MENTION=6596304]benthomp85[/MENTION] It can be a ROM's fault, that only appears on specific panel revisions. I hope a solution can be found as this is the only thing preventing me from flashing this and similar ROMs.
[ONE Original Android Development] androizers:
Cuz u using lollipop baseband.!

Marshmallow's baseband from CM is 0011. But since, they have now revert it, don't know what will b the revision number now!
[ONE Original Android Development] gaspolo:
so what is the best solution ;)
[ONE Original Android Development] androizers:
If there ain't any issue for u, then stay. Else, move on with CM latest commits and flash the old modem. Simple. ?
[ONE Original Android Development] gaspolo:
i have changeit now with

0.1c1.1-000004 m8974aaaaaanazm 1 :) give a try ;)
[ONE Original Android Development] rspkt:
Nobody has any insight on my boot up phone encryption issue? I haven't been able to find a solution yet and I've been searching for hours.
[ONE Original Android Development] 2384315154:
What's the problem?
[ONE Original Android Development] P1f:
You failed to mention what recovery are you on? As far as I know for encrypted devices the materialized twrp 2.8.7.0.5 should be used.

Official twrp 2860 is the last official version that flashes firmware correctly but I read it has issues with encryption and there is an unnoficial materialized version here on XDA that should be able to work both with firmware and encryption.
[ONE Original Android Development] ryanmat:
Same thing happened to me the other day when I was trying to flash some Kit Kat modems to compare to the current modem, seems like the new firmware doesn't play nice with the old modems. The only other thing I can think is that you are currently encrypted on CM12.1, I had to flash my phone to bone stock with fastboot, then did the upgrade to 13 and had to encrypt again. I remember reading that CM13 and CM12.1 don't read each other's encryption correctly. Lastly, make sure you're following the steps in the OP for clean flashing and you're using the right TWRP versions.
[ONE Original Android Development] rspkt:
Boot encryption issue

Apologies. TWRP 2.8.6.0 as recommended in OP. I tried 2.8.7.0 also just for the hell of it. Both recoveries yield the same results. As I said stock works fine but both Sultan CM12.1/13 yield that boot encryption issue.
[ONE Original Android Development] stranac79:
Still poor battery even I uncheck all this things
[ONE Original Android Development] donk165:
If I wanted to downgrade from CM13 to CM12.1, what would be the best way, while keeping as much app data as I can? I was going to use titanium backup to backup all my app data and user apps.

Any tips would be great!

Thanks
[ONE Original Android Development] palmenmichiel:
Make a backup of only your user apps, not system apps, after that use the titanium backup option to make a flashable zip, this makes a flashable zip file from your backup. then just wipe your OS, install 5.1.1, let it boot up till home screen, go to twrp again and flash the update.zip file now , reboot and all your apps are there again. I recommend making the flashable zip file as I had troubles with titanium backup going from 5.1.1 to 6.0.0 which didn't recognize my backup location anymore, if you just have a flashable zip you won't have this problem.
[ONE Original Android Development] Mr hOaX:
It's because of your background running apps and you cannot control their behavior to get real time notifications

You can try out below threads to minimize Play Services battery drain(it may or may not work for you, but it is working for me always)

Thread 1

Thread 2

Thread 3

Thread 4 (I had learn above tweaking from this thread few years ago)
[ONE Original Android Development] ming3r:
The main culprit for Play Services for me is if I have it doing wifi scanning. If I set it to GPS only then the phone isn't kept awake the whole time for me.
[ONE Original Android Development] Evermind10:
It's hard to imagine that it's the developer's fault for random faint lines to appear on your screen. Most of the time it's either a flawed flash, or its a hardware issue. No developer codes the colour on the screen pixel by pixel.
[ONE Original Android Development] hamma:
I have the same problem, but only on Sultan´s ROM. Now i´m running Mokee and there are absolutely no problems with the screen.
[ONE Original Android Development] PoisonWolf:
Is it fair to say that there is absolutely no way to shoot slow shutter pictures in this ROM due to the limitations of the Oxygen OS camera libraries? Even with a 3rd party camera app it would not be possible, correct?

I ask because I absolutely love shooting slow shutter shots on a tripod with this phone but it appears that 2 seconds is the absolute limit allowed on this ROM. Just wanted to double check if this is indeed the case.
[ONE Original Android Development] sindahouse:
low mic issue with this rom.. 6.0.1 .. I'd normally modify the build.prop file to appear like this

mm.enable.smoothstreaming=true

mm.enable.qcom_parser=3310129

ro.qc.sdk.audio.fluencetype=none

persist.audio.fluence.voicecall=true

audio.offload.buffer.size.kb=32

But this build.prop script is different. Can you help me out. Can't use the phone like this, it's useless
[ONE Original Android Development] stranac79:
thank you

will try all of this :)
[ONE Original Android Development] mojna37:
i have the mic problem too.
[ONE Original Android Development] dendi:
yeah bro tahts what im trying to say ! i wanted to agree on hardware issue but flashing other roms rule that ! :( only sultans rom causing me this issue on display bro !

---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------

[MENTION=4800121]Sultanxda[/MENTION] please bro ! any professional advice ?
[ONE Original Android Development] 2384315154:
Go to the format data option in TWRP, it will completely remove this weird nonexistent encryption
[ONE Original Android Development] zairmalik:
is this ROM supports F2FS?
[ONE Original Android Development] anubis.genix:
I'm noticing phone shutdowns at 20% remaining battery power. It's running on the latest 17th build with stock kernel. Any ideas on this weird bahavior?
[ONE Original Android Development] DerRomtester:
No this rom does not support f2fs. But you can get it working if you know how. ?
[ONE Original Android Development] ks_manish:
Battery issue I guess. Time to replace!
[ONE Original Android Development] 2384315154:
Cannot for the life of me, figure out why my WiFi barely works anymore

Tried rebooting phone, forgetting router, toggling wifi, rebooting router

It's saying it's connected but it refuses to work - anyone got any suggestions?
[ONE Original Android Development] Lobster$:
Same, frequent wifi disconnects since November.
[ONE Original Android Development] CeeeJaaay:
Same here, wifi is pretty much unusable. Is it something that can be fixed by Sultan or does it happen with other CM13 roms too?
[ONE Original Android Development] Mr hOaX:
You can see in those results in latest battery stats

http://imgur.com/a/xgptD

0-1% Google Play Services battery drain.

Over 7 Hrs SOT!
[ONE Original Android Development] blackbird91:
Try turning off the bluetooth. I have the same problem, wifi speed is very very low when I have the Bluetooth on.
[ONE Original Android Development] david72262:
I use a lot of different Wi-Fi networks and never have a problem with Wi-Fi even with bluetooth on constantly I did a completely clean flash even wiping internal storage

because of another problem and no issues at all I know a lot of people will say internal storage doesn't matter but over the years of flashing different stuff even on my older phones sometimes there's something stored in your storage a bad corrupted picture or anything can make other problems
[ONE Original Android Development] o-l-a-v:
Anyone tried to dirty flash from this ROM to official Nightlies? I'd really like to try f2fs and more recent updates, as SultanXDA has announced that jobs and studies will take up most of his time. Which off course is fully understandable :)
[ONE Original Android Development] bleached:
[MENTION=5104904]thepico[/MENTION] Do you also have the screen problem with jgcaap ROM?

http://xdaforums.com/oneplus-one/development/rom-cm-12-builds-t3045053

(Don't be fooled by the link, it is a cm13 ROM).
[ONE Original Android Development] dendi:
never tried this rom before bro ! ill do and get back to you ! might take some time as im at work
[ONE Original Android Development] runderekrun:
Yes. Go back to CM12.1 if you need stability. CM13 is still very much in beta. Things are going to be broke. Most things won't be fixed until Cyanogen gets around to fixing them.
[ONE Original Android Development] rspkt:
I tried that already multiple times and it didn't work at all using TWRP 2.8.6.0 or 2.8.7.0. I don't believe those versions of TWRP work properly to address this encryption issue.
[ONE Original Android Development] 2384315154:
Did you try 2.8.6.1? Encryption doesn't work on 2.8.6.0.

If that doesn't work you can find the "Unofficial TWRP" thread in Android Development and go to the last page or so, there's a new version of TWRP linked by someone called "tiny".

If that doesn't work then I'm out of ideas.

---------- Post added at 10:30 PM ---------- Previous post was at 10:27 PM ----------

I'm well aware CM13 is not in a stable phase yet.

I'm just asking if anyone has a fix for this particular issue besides Sultans builds are daily driver material anyway.
[ONE Original Android Development] rspkt:
I downloaded TWRP 2.8.7.0.5 materialized and am going to try that one per a previous member's suggestion. Hopefully that will address this strange encryption issue. I will definitely report back with results and whether it solved the problem or not. I read over the TWRP thread pretty thoroughly and it sounds like any TWRP version 2.8.7.0.1 and above should have this encryption issue fixed. Sounds like it will be part of the new release whenever that happens. Either way, I will report back with my findings.
[ONE Original Android Development] 2384315154:
The one I mentioned is the very latest so try that if 2.8.7.0.5 doesn't work

Also you may want to try flashing the new TWRP via TWRP instead of fastboot if that's what you're doing

It's unconfirmed (but has previously been the case) and may be unrelated but it seems there may be a bug with TWRP decrypting partitions if it was installed via fastboot
[ONE Original Android Development] bobwya:
Just idly wondering if anyone else is stuck on cm-13.0-2016.01.01-UNOFFICIAL-Sultan?

I'm happy enough with this version (I haven't found anything that doesn't work and the ROM is stable for me.) - but hey who doesn't want to upgrade!! Any attempt to update to a newer version and the SIM card is unrecognised and the phone goes into an unstable reboot loop cycle. I've tried many both recommended version of TWRP. I've tried flashing the nightly ROMs first, etc. But I keep having to revert back to the 2016.01.01 build... Any thoughts?

My Oneplus One is encrypted btw.
[ONE Original Android Development] xzjn9p:
Try turning off bluetooth
[ONE Original Android Development] FloorFox:
Not a hardware problem. It's a cm nasty bug
[ONE Original Android Development] thefraggle:
Nope, pure software issue, not hardware.

I clean flashed an official nightly with TWPR (the appropriate version than can flash modems and firmware) and Sultans ROM afterward - battery issues fully gone.
[ONE Original Android Development] lynxboy:
Still finding Do Not Disturb mode to be a bit flaky on the latest build.

Clean install - set Do Not Disturb mode to Alarms Only, reboot phone, Alarms Only still set however system sounds (touch sounds and screen lock sounds etc) are still coming through. Toggling Priority Mode and then Alarms Only mode fixes the issue, however on a couple of occasions the bug represents itself during normal use i.e. no reboot.

Strange, not a deal breaker and the ROM is perfect otherwise. Can provide logs if necessary, but just wondered if anyone else has noticed the same thing?

Regards.
[ONE Original Android Development] GirishSharma:
If you are developer then use CM 13 else use CM 12.1 (piece of mind). After all this is a tiny device (smartphone) which is not a super computer! I think if we do not encounter call cut, slow internet problem and good camera (yes, it is used rare though), one day battery cycle and other general functionality; then its enough for a common man.
[ONE Original Android Development] Mathorlaz:
To everyone having encryption problems: this is a TWRP issue caused by CM changing how the encryption is done.

I've had this issue, and the recovery in the post below fixes it. Try it out and you may not need to format data and remove encryption.

http://xdaforums.com/showpost.php?p=64891191&postcount=926

TWRP should be updated soon, but since this thread is for Sultan's ROM, maybe this discussion should go somewhere else.

Cheers
[ONE Original Android Development] Gawd:
Don't know what's causing this. Anyone with the same issues? Plus, my upload speed does not support this amount of data to be uploaded in a single day as you can see in the screenshot. On the build of 14/01. Thanks in advance.
[ONE Original Android Development] dvgrhl:
I was having the same issues consistently, but unfortunately deleting and resetting the APN's didn't resolve it for me. I've tried a few different things, but the only thing that keeps the issue from happening for me is to turn off wifi. Even when I'm not connected to a wifi network, just having it enabled causes the issue. I haven't used GPS yet, but if I experience the issue on GPS then I'm going to try disabling wifi scanning under location settings.
[ONE Original Android Development] -iHackerz-:
I have the same problem and it's annoying as hell sometimes! Also noticed it happens more frequently in cold areas? Since I was taking shots this winter outside, the white patch was almost fully visible. Also only happens on this rom and COS for some reason.
[ONE Original Android Development] DerRomtester:
LTE has nothing to do with the kernel.
[ONE Original Android Development] GeneFitz23:
Volume adjustment sounds doesn't work as well.
[ONE Original Android Development] themanuelperson:
So I'm really sorry if this is a dumb question but I've been trying to v4a working and after following everything everyone has said the only way I've gotten it to work is by setting selinux to permissive, which some people have said is bad, is it really problematic to run my phone this way? Also in case anyone is wondering I installed the apk as a user app and am running the power saver drivers.
[ONE Original Android Development] bobwya:
So any discussion about a very common fix for flashing the Sultan ROM should go somewhere else? Probably not!! :confused:

Cough, did this work with a fastboot flash of the unofficial TWRP version you linked to?
[ONE Original Android Development] jerpd3rp:
deleted
[ONE Original Android Development] abhibnl:
Hi [MENTION=4800121]Sultanxda[/MENTION]

I know u have tried to fix battery %age from your side but this issue still persists. The phone stays at 100% for hours even when it's awake. I guess i won't be able to use this rom anymore due to the various issues introduced by the latest builds. One more issue that i have started noticing from last two builds is that e phone stays constantly awake without any rogue app notification in BBS. But bbs confirms that there is no deep sleep. The phone shuts own randomly even at 35% sometimes. Not a daily driver anymore i believe. I'm completely stock, no xposed, no custom kernel. Only gpu is underclocked to 389mhz, that's all. Here are some ss. I would wait for next 2-3 builds and hope things will settle down.

Sent from OnePlus One
[ONE Original Android Development] Mathorlaz:
There are 2 issues with TWRP:

- Firmware flashing not working, resulting in SIM cards not recognized and no cel signal;

- In the event of the user encrypting the personal files using Android's built-in function, it not being able to be mounted in TWRP, making it difficult to upgrade to another ROM version without wiping data and starting over.

The recovery version in the link (2.8.7.1) seems to fix both these issues, even though it really isn't a release of "unnoficial twrp" but just the work of a helpful developer, which did it on his own.

Both these issues though still have nothing to do with the Sultan's ROM itself, but with the means you use to install it. That is why I said this discussion should maybe head to a TWRP related thread.

About your question, I did flash it via fastboot yes, since mounting the data partition wasn't possible with my previous recovery.
[ONE Original Android Development] Sultanxda:
I wasted several hours trying to fix this in the past, and I was not successful. I don't own an affected piece of hardware, so I will not spend any more time on this issue.

I spent 3 days rewriting the battery driver specifically for people like you who think that your battery issues are magically caused by the ROM/kernel, and somehow expect me to fix them.

With

every kernel for the OPO in existence, all battery measurements come directly from the hardware

. It does not matter if you "don't experience this issue with COS", or you "don't experience this issue with an older build". Every single build, for any OPO ROM, uses the

same technique to retrieve battery measurements, and that technique is to ask the hardware (fuel-gauge chip) itself

.

Your battery is bad (voltage output drops below the minimum operating threshold at 35% reported charge remaining). I can't fix your battery, and I will not waste any more time trying to fix an issue that cannot be fixed with software. The only way left to "fix" your issue with software would be to manually recalibrate the fuel-gauge chip in your phone, which can only be done by the OEM.

I never said this ROM was supposed to be a daily driver; I only said that I'm using it as my daily driver. Use a different ROM if you don't like it.
[ONE Original Android Development] runeazn:
props to u dude it's a great rom, people shouldn't phrase their sentence like this, like they are blaming you.

Last time I bricked my device with the rom and no hard feelings were made.

Great rom keep the good work coming bro.
[ONE Original Android Development] k2r79:
Hi,

First of all, you've done an awesome job on this ROM and am proudly using it as a daily driver !

I have noticed that my NFC doesn't seem to work anymore (I use TagInfo to test it) and have done some research about it. I found this thread (forum.cyanogenmod.org/topic/118757-cm13-nfc-problem/) which mentions this problem and seemingly a guy found a solution in Post #17. This solution consists in replacing system libs but I can't seem to locate them on my device.

Did you encounter such a problem with the NFC ? Do you think this fix can work and is implementable in your next release ?

I think this problem comes from CyanogenMod but I thought your feedback would be very helpful to me.

Thanks for the great job !
[ONE Original Android Development] madsponge26:
Waiting for this https://streamable.com/iiiw
[ONE Original Android Development] mikronac.ns:
[MENTION=4800121]Sultanxda[/MENTION] Can you help me with this error? I got it on the end of packaging zip file while compiling CM13 from your sources?

Solved:

http://review.cyanogenmod.org/#/c/100826/3