yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] erdal67:
Hello,

This rom is awesome and I know its in alpha stage but please fix this time bug, it makes the phone unreliable! It's like the third or forth time this happened time in statusbar shows 23:32, in notification area 23:33 and the screenshot shows it's actually 00:06 right now [MENTION=4800121]Sultanxda[/MENTION]

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] Brian325:
I don't have this issue. Time is correct here.
[ONE Original Android Development] palmenmichiel:
Only issue I seem to have is after a while, unlocking the phone becomes really slow/laggy, a simple reboot fixes this. Great rom!
[ONE Original Android Development] highdiver_2000:
I am on c.7.00011 I keep getting black triangle in areas that I know have cell signals. Irritating going to be annoying.

I tried fastboot flash an older Lollipop modem and got a no SIM error. Guess I need to find something newer.
[ONE Original Android Development] panxe:
Damn my network.

After I flashed 01, my modem was 11. Then I flashed 04 my modem is now 13, now 06 my modem is still 13.

Real issue - when someone calls me , even though the phone is idle its saying busy. Also poor reception. I'm irritated.

Modem 11 was better it seems. How to get back now.

Why did it changed to 13 after 04?
[ONE Original Android Development] nathan-96:
If I dirty flash from 01 to 04 or 06, have random reboots. It's since the modem is nog included anymore. I have twrp 2.8.7.0

You're sure it had tot do with twrp? Or do i manually need tot flash modem? (Build 4&6 also doesn't recognize my sim)
[ONE Original Android Development] highdiver_2000:
I downloaded the latest cM13 nightly, extracted NON-HLOS.bin

Fastboot flash modem NON-HLOS.bin
[ONE Original Android Development] panxe:
Thanks mate, will h2os modem work with cm13?
[ONE Original Android Development] MrTeejay619:
Dude like you should scroll through the old postS, STOP USING TWRP 2.8.7.0!
[ONE Original Android Development] se7enlyn:
I've noticed that it only happens during charging. Sultanxda did ask if we used system profiles, and yes i've always used system profiles when it happens.
[ONE Original Android Development] novren:
For me it used to happen when rebooting the phone while on wi-fi because I had a profile that would turn off lockscreen on wi-fi. I removed said profile and it fixed itself. It's happened to me on cm12, and on my mom's redmi 1s too. On cm12 it was fixed after a while. On the meantime I just don't use system profiles, until it's been fixed again.
[ONE Original Android Development] hmzuleta:
Does anyone else here have problems taking logcats? Every time I try, no matter which app, the logs are empty. Googled for an hour, no relevant answers. I'm using SuperSU 2.66 beta. Could that be the culprit? Thanks.
[ONE Original Android Development] highdiver_2000:
No idea. I am too lazy for modem driver testing. I managed to flash c6-00241 hopefully I get less drop out than c7-00011
[ONE Original Android Development] eunique:
Upper right corner...SEARCH

It's been discussed tons of times.

At the very least, read the OP and instructions!

?
[ONE Original Android Development] Mr hOaX:
Is encryption working on this ROM?

I want to enable it for some testing work
[ONE Original Android Development] metalelf0:
Thanks a lot! This worked perfectly! I guess my problem was a wrong TWRP version. Thanks!
[ONE Original Android Development] firenxe:
had this problem once, fixed it by wiping data of google play services under applications.
[ONE Original Android Development] mexiro:
Hello, I have been dirtyflashing since November, and no issues. The rom is stable ...
[ONE Original Android Development] TareqA:
Is it me or does turning the screen on doesn't have an animation of glowing up instead of just turn on like the one on official cm13
[ONE Original Android Development] thefraggle:
I had exactly the same problems before. It even got worse after another update with no baseband/modem and no detected sim... I think it was caused with using a TWRP recovery version that was not able to update everything correctly.

I reverted back to an original stock rom (clean flash) and started over again with flashing an official CM13.1 nightly and then Sultan's rom, as stated multiple times in this thread.

Baseband / modem is working now and actually never had any problems with my battery again.

Maybe you don't need to wipe and clean flash, but I assume you should check your modem / baseband as well.
[ONE Original Android Development] guacko:
Hi all!

Where is the option to administrate root permissions?

I denied root permissions to Nova Launcher and I'd like to modify the decision but I can't find the way to change it.

Regards!!
[ONE Original Android Development] hamma:
Dev Options
[ONE Original Android Development] guacko:
Can you be more specific please?

In Dev Options I can activate root access but not manage app permissions.

Thanks!
[ONE Original Android Development] hamma:
Sorry i misread. Don´t know.
[ONE Original Android Development] se7enlyn:
don't wipe is partially true...

1. for a clean flash, wipe everything except internal storage and otg drive

2. flash official cm 13 nightly

3. without wiping system and etc, just flash sultanxda's rom

4. flash gapps

5. wipe cache+dalvik

6. reboot

done
[ONE Original Android Development] Genericxx:
Settings -> Privacy -> Privacy

Tap and hold on Nova Launcher for 2 seconds and enable Root Access again.
[ONE Original Android Development] thefraggle:
Is there actually any need or benefit to flash an official CM13 nightly from time to time before updating Sultan's rom?

Would this do any more good than bad?
[ONE Original Android Development] se7enlyn:
sultanxda's rom does not come with a modem. you either flash cm 13 official for the modem or download your own modem and flash it if you don't want to flash cm 13 official first.
[ONE Original Android Development] thefraggle:
Thank you. But I mean if everything is working. Is there any need or benefit to flash an official CM13 let's say once a month or so? Or no need at all?
[ONE Original Android Development] droidzeus:
I am having almost 20% overnight battery drain on 6th Jan built due to wifi. I already disabled the WiFi scanning
[ONE Original Android Development] nathan-96:
Search did not work yesterday :p, but reading OP is nog a bad suggestion ;)
[ONE Original Android Development] se7enlyn:
only if you want to reinstall the rom after a clean wipe/install.

if you are just updating sultanxda's rom , you do not need to flash cm 13 official prior to flashing the updated sultanxda rom.
[ONE Original Android Development] Cissiboy:
App info
[ONE Original Android Development] GirishSharma:
If you have flashed xposed zip and installed xposed installer alpha, then there are couple of xposed mods by which we can control per app permissions.
[ONE Original Android Development] tkruijer:
Search didn't work indeed. I have had this problem in the past, but I didn't thought of it because I didn't touch TWRP. OP suggested to downgrade TWRP when having an error in the installation progress, that wasn't the case up here ;). Glad to be back on track with this rom, it's performance is once again outstanding!
[ONE Original Android Development] hmzuleta:
Anyone? :(
[ONE Original Android Development] Notor1ouS-:
3% drain overnight on wifi.

works for me. o0
[ONE Original Android Development] tkruijer:
Maybe the stats are wrong. Use it for a couple of days and see if the 'wifi battery drain' still persists
[ONE Original Android Development] Prodromodinverno:
It would be great to have an updated thread with new and updated modems
[ONE Original Android Development] NickosD:
Quick question just to be sure. I have flashed cm13 nightly using twrp 2.8.6.0. If I flash latest sultan version, my baseband will not change. Am I right? I will stay with the latest?

Sent from my bacon!!!!!
[ONE Original Android Development] Khizar:
Correct
[ONE Original Android Development] capitanouncino:
Holy ****, I have flashed 6th build on 1st (twrp 2.8.6) and now I'm without baseband. I tried to flash 3012 modem (cm and h2os) but nothing, the system doesn't read the SIM and it self-reboots continuosly. Help me!
[ONE Original Android Development] czesiu89:
Just wait. My phone rebooted like 7 times before it started to work normally at 6th build.

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] bobotauro:
Hi guys. My device is at version 13.0-20160101-Unofficial. I have tried to update to version 20160106. after the update the phone no longer detect the sim, and after a few minutes it will restart.

Someone of you has encountered the same problem?

Or for this update, is there a different procedure?

PS.

TWRP 2.8.6
[ONE Original Android Development] boak:
OMG I read ton of posts only issue with no Sim card
[ONE Original Android Development] payne_307:
Hi Sultan... This ROM comes pre-rooted and must be a great help to many. However, for me it works the opposite. I have some apps from my company which do not allow me to run them on a rooted device, unless I use Xposed and use a specific mod (I would personally want to avoid using Xposed since its introduces problems that are hard to isolate / rectify). I hence had to shift to Darkobas ROM as those are "user" builds instaed of "user-debug" builds. Is there a possibility you can make these builds "user" builds to eliminate su binaries in /system/xbin/? For people who need root can always flash a SuperSU zip. Missing some features from CM, especially after using COS 12.1.1 which though is smooth and cleanest COS build for OPO till date but not without the inherent Lollipop niggles.
[ONE Original Android Development] ryanmat:
[MENTION=4800121]Sultanxda[/MENTION], I was able to build with LZMA and flash and boot last night. The zip package was about 60 MB smaller than normal.

I cherry-picked this commit: http://review.cyanogenmod.org/#/c/125972/ then added # LZMA WITH_LZMA_OTA := true in device/oneplus/bacon BoardConfig.mk

I flashed it with the 20160101 TWRP from ketut.kumajaya, I'm not sure if that would make a difference, but it seems to be working. I also flashed the full zip, so I'm not sure if there will be issues using CMUpdater. Hope this update helps if you do try to add it back in to your builds. Thanks again for your awesome work!
[ONE Original Android Development] sneakerspark:
Flash latest cm 13 nightly with twrp 2.8.0.6 and then flash the latest sultan build.
[ONE Original Android Development] rayturner:
For the last 3 updates, I've been unable to change the wallpaper on my device. I've tried 4 additional themes (all CM13), and while other choices, like icons,animations, etc change, I'm always at the default wallpaper! I saw one person ask the same question but never found an answer. This problem survived a clean wipe. Any help would be appreciated.
[ONE Original Android Development] DarKAngel1234:
Clean Flashed, Latest build using open gapps mini. Can't get my google account to back up data, etc. Or even to hold the account info at all, ends up grayed out.? sync works, but no photo backup at all, sync option in google photos is greyed out as well, not sure what is going on.? Any ideas>?
[ONE Original Android Development] mcgrabowski:
I was on stock CM12S and decided that I wanted to come back to Sultans CM13. I downloaded the latest (1/6) build to flash, along with the 1/6 CM13 official nightly. Using TWRP 2.8.6.1 I wiped the phone, flashed the CM13 nightly, (I tried this multiple times wiping and not wiping in between), flashed Sultans CM13 and then pico Open GAPPS. No matter how many times I tried it refused to pick up the SIM card and would reboot after a minute or so. I even tried flashing the modem directly. Dirty flashing the CM13 Nightly and then re-flashing Sultans CM13. It just wouldn't work. I even let it sit idle and reboot about 10 times over 10-15 minutes as someone earlier had suggested.

I downloaded the 1/1 build, and using the exact same procedure with the same installation of TWRP and the same CM13 nightly download from 1/6, I flashed went through the procedure and flashed the 1/1 build and it appears to be just fine. It did appear to not detect the SIM card for about 3-5 secs before it picked it up.

From the working 1/1 build I used the OTA update to download and flash the 1/6 build. Again, no SIM detected and reboots after a minute or so. No idea what the issue is with this latest build, but it doesn't seem to work in the least bit for me here. I'm going to re-flash the 1/1 build, maybe I'll try OTA updating to the 1/4 build and see if that works any better for me and just avoid the 1/6 build for now. Just figured I'd share what I experience.
[ONE Original Android Development] ryanmat:
Just read back the past 10 pages or so. Only the Official TWRP 2.8.6.0 will flash the modem/firmware files correctly, no other version of the Official TWRP will work right. Or you can use the Unofficial versions here: http://xdaforums.com/oneplus-one/development/unofficial-twrp-2-8-3-0-t2981495

This is even mentioned by Sultan in the OP. Let's all remember the first rule of XDA, search before you post...
[ONE Original Android Development] mcgrabowski:
2.8.6.x works. 2.8.7.x doesn't not. Obviously it wasn't/isn't an issue with TWRP right? I mean, why would it be a TWRP issue if the same exact version/install worked for every other modem I've had to flash until the 1/6 build including the 1/1 build I just flashed that works perfectly fine? I've read the OP post, many times and I've literally followed and read every post in this thread.

Edit: Not to mention that doing the OTA to 1/6 from a working 1/1 build didn't work. Which doesn't involve flashing the modem at that point.
[ONE Original Android Development] alroger:
Wrong. Read again. 2.8.6.0 !
[ONE Original Android Development] mcgrabowski:
Seriously? So what you guys are saying is that dirty flashing the 1/6 build, which doesn't even include a modem from a fully functional 1/1 build (read that as the modem is installed and works perfectly fine) is not working properly because the modem that doesn't exist to be flashed is not being flashed properly because I'm using the incorrect version of TWRP. Good troubleshooting guys. :) Makes perfect sense to me.
[ONE Original Android Development] david72262:
I ota from 1/1 to 1/6 no problem I have used unofficial recovery 2.8.6.0 since it came out never changed it well once back to an even older version for the aroma installer function. IMHO this is the only recovery to use saved my azz a couple of times on lost efs use this version
[ONE Original Android Development] runderekrun:
Thanks I'll try that.
[ONE Original Android Development] hmzuleta:
I strongly advise those who had data limits set, to re apply them, as they might have been deleted with the updates.
[ONE Original Android Development] mcgrabowski:
Apologies to you both, I've been using the 2.8.6.1 since I started flashing Sultans ROMs back with CM12 and then onto CM13 and never had a problem until now. It still doesn't make any sense to me that flashing the build that isn't supposed to have the modem built in is what causes a problem and I was able to flash the 1/1 build without any trouble. 2.8.6.0 seemed to flash the 1/6 build fine. And the odd thing is the baseband version didn't appear to change. So it just doesn't seem to make sense. Sorry for clogging the thread up unnecessarily.
[ONE Original Android Development] nathan-96:
So I downgraded to recommended TWRP, did not solve my probleme. After flashing 6 i had those reboots and no sim again. I upgraded my TWRP again and flashed official nightly, then this rom, wiped cache & dalvik and now it's al working fine.
[ONE Original Android Development] ryanmat:
No problem, I'm glad your problem was sorted out. I actually grabbed the full firmware from CM13 and fastbooted them all to be sure that everything was flashed properly. I've been using the Unofficial TWRP for a few days now and I like it a lot.

I'm curious, what baseband is your phone showing? Official CM is c7-00011. Sultan did have his set to the c1-00011, but in his latest builds removed it so you can flash any modem you want now.
[ONE Original Android Development] mcgrabowski:
My baseband is showing

.4.0.1.c7-00011-M8974AAAAANAZM-1

And at this point I have flashed the CM13 Official Nightly from 1/6 and then Sultans CM13 from 1/6. I probably missed it being at C1. I'm guessing when I flashed Sultan's 1/1 build, it must have been at C1.

---------- Post added at 12:40 PM ---------- Previous post was at 12:39 PM ----------

What version did you 'upgrade' your TWRP too that worked for flashing the 1/6 build?
[ONE Original Android Development] mak725:
Other sounds to enter and exit setup fc gives me, anyone else with the same error?

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] nathan-96:
For me it's working fine, not the cause of the problem :)

---------- Post added at 10:38 PM ---------- Previous post was at 10:38 PM ----------

I flashed twrp 2.8.7.0 again, rebooted to recovery, then flashed official nightly from today (January 7), wiped dalvik + cache, flashed unofficial from Januari 6 and wiped dalvik and cache again.

p.s. I don't think it's because of TWRP 2.8.7.0, since it's not working for most. If it doesn't work just try this instructions with TWRP 2.8.6.0
[ONE Original Android Development] PivotMasterNM:
guys is there any way to get the newer modem version of the 1/1 build while using the 1/6 build? I've been searching the MPSS.DI.4.0.1.c1.11-00004-M8974AAAAANAZM-1 modem but can't find anything to flash or anything like that and a dirty flash from 1/1 to 1/6 doesn't do the trick (using TWRP 2.8.6.0).

does anyone have a link or smth?
[ONE Original Android Development] ryanmat:
If you want to try out the newer version check out this post: http://xdaforums.com/showpost.php?p=64578611&postcount=1267

You can also look through that thread to find all the other modems if you want to go back to a different version.
[ONE Original Android Development] PivotMasterNM:
You da real MVP. Thanks :)
[ONE Original Android Development] andrea90:
Could I undervolt on this rom? Sorry but search doesn't work now...
[ONE Original Android Development] cloudx720:
Hi sultanxda :) just a quick question. Does gpu overclock actually work on the oneplus one? I see some kernels with gpu overclock control, but i read somewhere its pointless as it doesn't work ? thanks if you can clear this up for me.
[ONE Original Android Development] counterfeit187:
Great ROM [MENTION=4800121]Sultanxda[/MENTION] thank you. I decided to switch to this until the official gets rid of the reboot issue, but not sure if I'll even switch back then. The snapdragon camera is better than Cyanogen imo. No issues here. Clean flash using the materialized TWRP, I did have an issue on first install attempt where it thought my phone was encrypted and asked for a password. I guess it was an issue of using f2fs? Anywho sorted it out by switching back to default file system and wiping everything including internal memory.
[ONE Original Android Development] abhibnl:
Hi all! Is anyone using the latest supersu beta 2.66 with this rom? Since [MENTION=4898097]arter97[/MENTION] has mentioned in his tweets that inbuilt supersu causes battery drain, i'm willing to try supersu but i won't be able to flash it till saturday.

Sent from OnePlus One
[ONE Original Android Development] joefso:
Currently using 2.66, no drain notice until now. Flashed today..
[ONE Original Android Development] Sultanxda:
Nope.

No.

...what?
[ONE Original Android Development] hamma:
Read this, why you shouldn´t undervolt: http://androidforums.com/threads/why-you-shouldnt-under-volt-or-over-clock.649634/
[ONE Original Android Development] binzianer:
24 hours running, 2h of display, 3h of Spotify and only lost 35%. I'm never gonna change anything on my phone again! Thanks so much [MENTION=4800121]Sultanxda[/MENTION]

To clarify: I'm a very conservative user, and I don't have cell data on because I'm abroad, though I'm more or less 24/7 on WiFi anyway. Was using the cm13 nightlies and switched to the 0104 sultan build dirty via twrp 2.8.6.0. This has been so far my best oneplus one experience.
[ONE Original Android Development] CalamitySir:
So when we flash the latest version of CM13, do we get "THE LATEST" nightly? or do we get the one with the same date as of this thread? So eg. Your version is Jan 6 2016, do i flash the official from Jan 6 or do I get the Jan 7th one which is the latest right now?
[ONE Original Android Development] david72262:
Either one should be fine haven't heard of them updating the modem again since the last update
[ONE Original Android Development] hey10103:
Still running 01.01.16 as I ran into the modem issue while updating to Jan 4th (updated before the changelog came out), does anyone have any recommendations for the best modem to use?
[ONE Original Android Development] mekanismen:
I can't use any of the newer ones, so I'm sticking to 0241 which is working fine for me.

[MENTION=4800121]Sultanxda[/MENTION]: Figured since you also live in Cali you're a good person to ask. Did you get the amber alert about the missing kid in Montebello? I didn't for some reason, but my wife, who's on the same carrier but uses an iPhone, did. Any clue as to why this might be? Would be a bummer if emergency alerts aren't working, with El Niño and everything.
[ONE Original Android Development] Sultanxda:
I didn't, and neither did my dad's Blackberry (we're both on T-Mobile, 400mi away from Montebello). I've received AMBER alerts in the past on my OPO (CM12.1), so I think it should be fine. Not sure why we didn't see anything this time though, as I thought they were supposed to be statewide.
[ONE Original Android Development] mekanismen:
Probably should've mentioned that we were sitting right next to each other when the alert was broadcasted, about 20 miles from Montebello.
[ONE Original Android Development] hmzuleta:
[MENTION=4800121]Sultanxda[/MENTION] I have the following issues with the ROM, both previously reported by my on the thread:

1.whenever I try to switch WiFi networks to one the phone has already saved (with its password and all) through the mini menu on the Quick Settings WiFi tile, it asks for the password anyway. When I go to the full settings (Settings menu, WiFi, tap on the network I want to switch to, connect), it doesn't ask for the password, as it is already saved. I can reproduce this bug 100% of the times, most likely CM side.

Here's a link to the screencast video I took of the bug: https://youtu.be/-qdek3c4wXk

2. I cannot take logcats, for some reason. Otherwise I'd provide one for the issue above :( I've tried all the apps in the Play Store. Every single logcat I try to make comes out empty. I checked permissions on them, nothing weird there. I gave root permissions, too. Even specified the logging permission using the Terminal for each app, with the command "pm grant package.name PERMISSION_LOG" or something similar I googled, to no avail. Unfortunately I'm on vacation away from my computer, so I can't try to run a logcat through adb. Should I try creating a logcat using the Terminal on the phone? EDIT: Tried, gets stuck. Proof: http://imgur.com/gallery/wrFnyS0

To be honest, I didn't try to record a logcat on previous builds, so I can't tell whether this is new for me.

New issues I found:

3. Chrome has some lag right after wake up. The main thread freezes for like 3 seconds if I try to open it after unlocking my phone, and then functions perfectly. This has been happening since the 4/1 build, iirc. Any thoughts?

4. Facebook says "Cannot connect right now" a lot, but I figured it's just their lousy programming rather than your ROM. Still, I'd rather report that.

5. Switching system profiles breaks Do Not Disturb settings. If a system profile is switched because of a trigger, the DND is deactivated and the profile settings override it. Not sure if this behavior is the designed one, but I found it odd.

That's about it, for now.

Thanks in advance for your time.