yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Khizar:
1. Don't have this issue.

3. Never had this on OPO, did have it on shamu a few times, I believe it to be app related and not rom cuz I had it on Google stock 6.0.1 as well.

4. Not rom related, app related, that's by far the worst app on the play store.

5. I always disable system profiles so can't comment.
[ONE Original Android Development] Milkeh:
I seem to be having a couple issues (6/1):

- Built in AOSP keyboard. Swipe gestures and auto-correcting don't seem to work even when the settings are enabled

- Bluetooth doesn't seem to be working properly with my Android Wear watch, drops out after a few minutes and doesn't reconnect unless bluetooth is turned off/on
[ONE Original Android Development] anthony.wang:
I have this issue as well! I thought everyone did, but apparently not (see a few posts below yours)...
[ONE Original Android Development] guywong:
OT: no Amber Alert

I am in Sacramento and neither my wife nor I received any amber alert today. She uses an iPhone bought from overseas and we are on AT&T. It appears Alerts are sent to phones capable of receiving Wireless Emergency Alerts. My OPO box does not have the WEA logo. So I don't know if we can get the alerts.

There is a FEMA app for Wireless Emergency Alert. You may want to download the app from the Play Store.

From the CHP web site,

https://www.chp.ca.gov/news-alerts/amber-alert/amber-alert-plan

Wireless Emergency Alerts Program (WEA)

The Wireless Emergency Alerts will allow consumers with WEA-capable smartphones and feature phones to automatically receive free AMBER Alert messages, along with Presidential and Imminent Threat Alerts. When a subscriber with a WEA enabled cellular phone is within range of the activated cell tower they will receive the AMBER Alerts, even if the wireless customer is not from the area. The program is an "opt out" program, meaning subscribers do not have to enroll in the program to receive alerts. The WEA AMBER Alert notification is automatically sent from National Center for Missing and Exploited Children (NCMEC) at the time of the AMBER Alert activation. The message includes an audible tone followed by a text-like message.

http://www.missingkids.com/Amber/WEAHow do I know if my device is Wireless Emergency Alert capable?

To determine if your mobile device is capable of receiving the alerts, visit www.ctia.org/wea and look for a link for your wireless service provider where you will find a list of mobile devices that will receive the alerts on their network. Also, be sure to ask for a capable device the next time you acquire a new mobile device.

Look for this symbol on the box:

Wireless Emergency Alerts

http://www.missingkids.com/en_US/desktop/MK-2A3cc-wea-logo.png
[ONE Original Android Development] Pjstaab:
Derp, showed up after reboot.
[ONE Original Android Development] zboq:
[MENTION=4800121]Sultanxda[/MENTION]

Have You ever tested NFC on Your phone ?. I tried yesterday to read info from my visa card and it's not working. I have also tested with Htc One and no problem on that phone.
[ONE Original Android Development] L0X0R:
Hey. I've been getting an issue for the past few builds that I'm hoping has an answer.

In the secret menu *#*#4636#*#* the band use keeps getting switched to LTE/gsm. I don't want 4g/lte and I have to keep selecting gsm/wcdma. Any ideas on this?

let me know if you have suggestions on how to get logs for it, if that would help.
[ONE Original Android Development] expiredd:
I'm having the same problem. But no idea how to solve it. Having been switching to 3g manually.
[ONE Original Android Development] Genericxx:
Same here, switches to LTE automagically after reboot and even after Airplane Mode. Probably related to the new Modem? Never had that on .241.

---------- Post added at 08:59 ---------- Previous post was at 08:47 ----------

Funny. It seems like CM is about to include Snapdragon Camera officially into the nightlies :eek:
[ONE Original Android Development] Khizar:
They had snapdragon cam in 5.1.1 too but didn't merge it.
[ONE Original Android Development] Genericxx:
Didn't recognized that. In this case, it's merged.
[ONE Original Android Development] Lamner:
Hi there,

I asked for the same thing twice and Sultan ignored me. Actually, I have the opposite problem: I'd like to stay on LTE/GSM auto prl but the phone sticks to WDCMA preferred after each reboot or when I exit from airplane mode.

I think the problem is related to build.prop and not the modem itself.
[ONE Original Android Development] mekanismen:
Thanks for that, I appreciate the info. Had no idea that it depends on what device you're using.
[ONE Original Android Development] thefraggle:
OK, after one another 2 days I can say that everything is working on my end. Fast and reliable, everything where it should. Okay-ish battery, but I did a lot of backups and installs.

Great job, waiting for updates :)
[ONE Original Android Development] alroger:
I frequently use it to change profiles. No problem reading or writing.
[ONE Original Android Development] gneville:
I'm having issues with in-call microphone being too high - people saying it sounds distorted. Is this to do with modem at all, or is this a CM13 tweak or a [MENTION=4800121]Sultanxda[/MENTION] tweak? Thanks!
[ONE Original Android Development] jamesking420:
Hi,

I recently received my phone back from Oneplus, where it had been repaired (and I assume updated with software/firmware and factory reset). I did not have OTA updates available when I received it, so I unlocked the bootloader and I immediately followed the instructions from this thread and loaded the SultanROM (4th January version). I did not need to flash the official CM13 first. It just worked – no modem issues.

I installed the 4th Jan release (Build date Sun Jan 3 20:14:42 PST 2016). I don’t appear to have the same modem that many have talked about. I have Baseband version DI.3.0.c6-00241-M8974AAAAANAZM-1.

Can anyone tell me how to get the most up to date modem without losing my installation, settings, etc? My guess is that I dirty flash the “official CM13” and then dirty flash SultanROM back? But I am nervous that if I get this wrong I’ll lose my settings so some confirmation would be appreciated 

Thanks,

James
[ONE Original Android Development] payne_307:
[MENTION=4800121]Sultanxda[/MENTION] ... Did you read my post about having user builds instead of user-debug builds which aren't pre-rooted? Is it possible for you to release user builds instead of user-debug builds?
[ONE Original Android Development] panxe:
I had similar issues.

Download new cm13 official nightly. Extract Non hlos .bin and flashboot .
[ONE Original Android Development] tsch:
[MENTION=4800121]Sultanxda[/MENTION]: I'm in plain 0601 (dirty flashed since ever). The accelerometer does not work anymore. Its stuck. Any cure? Everything else works perfectly. I saw it today taking pictures. Only portrait - in all apps...

Update: after flashing 0601 again, it worked again....
[ONE Original Android Development] Klaus_Trophobie:
We have reported this behaviour to the Oppo guys but nobody seems to be responsible anymore for the modem. This behaviour got reported back in 09/2015 and nothing has changed since... Very frustrating...

Check:

https://jira.cyanogenmod.org/browse/BACON-4178#

I´m still having this issue with a properly installed Jan 06 CM 13.0 and the very latest RADIO / Baseband.

[MENTION=4800121]Sultanxda[/MENTION] have you experienced something like this in any way during your own tests ? In the named thread there was also a mention of the error inside the codebase somewhere. Could you please verify this ? Mike mentioned a fixe there: https://jira.cyanogenmod.org/browse...issuetabpanels:comment-tabpanel#comment-82430 - BTW thanx 4 your efforts. Beside the modem issue all seems to work pretty good here....
[ONE Original Android Development] ryanmat:
I posted a link to the latest modem a few pages back. There is also a Radio thread that you can search for that has all the modems available to flash in zip packages to make it easy.

Also, for those with WiFi and Bluetooth issues, have you tried deleting all of your saved connections and re-paired them? That's what I had to do and everything has been working great. I don't know if it has to do with the Jan 1 security patch, but just a suggestion to test.
[ONE Original Android Development] world94:
How can I update the ROM if it's a secondary in MultiROM?

If I just dirty flash the zip i have an error and I loose gapps :(
[ONE Original Android Development] J_E_F_F:
can adaway be used with this ROM now? Has the CM bug that prevented it been corrected?
[ONE Original Android Development] 5ud0:
Is gps fix working correctly in this rom ?
[ONE Original Android Development] alroger:
Yes.
[ONE Original Android Development] octagonPerfectionist:
So, I've been having a problem where when flashing the zip from TWRP, it gets stuck at the "patching system image unconditionally" step. Same thing actually happens with the CM13 nightly build too. Any idea what this might be?
[ONE Original Android Development] highdiver_2000:
Yes you can. Fdroid +adaway
[ONE Original Android Development] ryanmat:
Have you checked to make sure the download size and the MD5 matches up?
[ONE Original Android Development] TareqA:
Looks like nightlies is going get a snapdragon camera tomorrow
[ONE Original Android Development] octagonPerfectionist:
Alright, so I found out that somehow things on my OTG USB drive were seen as corrupted on my phone for some reason. I managed to install the ROM and gapps via ADB sideload. But now it seems I'm having another problem - after CM boots, it comes up with a screen saying I need to enter my password to boot, and no matter what I type in it says "password was correct, but decryption was unsuccessful" then proceeds to automatically do a factory reset - then gives the same screen again.

Can't say I've ever run into this problem before. The same thing actually happened when I tried to restore a backup I had made earlier too.

Edit: Actually, scratch that. I went back and manually did a factory reset and it works fine now. Still have no idea why my OTG drive isn't working right now though...all of the data is still fine on my computer.
[ONE Original Android Development] Ste05:
As was I, although now I seem to be having problems with all Settings, whenever I enter any Settings I get a Force Closure with an error message "Unfortunately, Settings has stopped"

Sorry if this has already been covered, the XDA search is down and I only checked a few pages back.

Anyone had this issue??
[ONE Original Android Development] oudbrood:
Can't find anything about the gps fix in the changelog????

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] mr_riddle:
After flashing the latest update, the phone went into boot loop. I flashed it again (clean), this time it did not recognize the sim card (no sim). I went back two versions.
[ONE Original Android Development] alroger:
I just flashed and tested both last night.

I think it's been working since the 1st on Sultans.

Can't help you with change logs.
[ONE Original Android Development] Zalbu:
Still getting the same error on Helium, I'm not even sure if it's a problem related to root so I'll just wait it out and see if anything changes with future updates.
[ONE Original Android Development] extrem0:
Great! Remember, you'll have to do it again once you clean or dirty flash rom again.

Then maybe it's an incompatibility in app itself with 6.0. Last time Helium was updated was on july, 07th. Android MM wasn't released yet. Did you check app permissions? Check if storage permission is allowed for helium.
[ONE Original Android Development] mik3see:
It seems that it needs a patch, that I was assuming was included in this ROM, cause its supposedly include in CM sources:

https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0

Maybe the patch is not included in this ROM
[ONE Original Android Development] Spider-Vice:
Yes, that makes it disappear.
[ONE Original Android Development] sash89:
U should already know that u don't have to flash gapps after a update buddy
[ONE Original Android Development] Perilla_:
Reboot in safe mode and set a working theme to fix it :good:
[ONE Original Android Development] eduardobarth:
Yep.
[ONE Original Android Development] Knox316:
No wifi, phone on standby 4h, no mobile data. Lost 45%. Gonna reboot and see if it helps.

[MENTION=4800121]Sultanxda[/MENTION]
[ONE Original Android Development] wendiko:
Nah i wasn't running I was riding a bicycle just to teste the GPS.

That's runtastic pro.

Cheers
[ONE Original Android Development] drewbot95:
FWIW, Doze Editor FC on Nov-9

Naptime still booting OK
[ONE Original Android Development] Biiz:
[MENTION=1736723]runderekrun[/MENTION] can you share your setting of doze editor?

me too :(

i can chose this:

WCDMA preferred

GSM only

WCDMA only

GSM auto PRL

CDMA auto PRL

CDMA only

EvDo only

GSM/CDMA auto PRL

LTE/CDMA auto PRL

LTE/GSM auto PRL

LTE/GSM/CDMA auto PRL

LTE only

Unknown

some help? 4G not working here :(

the rest, rock solid! only a FC in the led's configuration, battery seems good, at least as good as on 12.1 by sultan
[ONE Original Android Development] Cappelletti:
Are you using Trebuchet?

I'm using Google Now. The app drawer keeps the original DPI.
[ONE Original Android Development] Geordie Boyo:
Am a big fan of Sultan's custom Roms, and been running his CM12.1 for a while now.

How stable is the latest build of this Rom to use as a daily driver?
[ONE Original Android Development] cristianvaz81993:
is stable like a rock, battery very good and smooth criminal!
[ONE Original Android Development] Lupin The Third:
That built-in multi-window mode is awesome! Thumbs up!
[ONE Original Android Development] Mauzii:
Any one has a fix for preferred network?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] Knox316:
cofcof I Lost 45% in 4hours with my phone on standby cofcof

I like sultanrom but this is an alpha version and should be treated like that.
[ONE Original Android Development] cristianvaz81993:
Disable wifi and bluetooth scanning in search settings
[ONE Original Android Development] czesiu89:
In which search settings?

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] Chevan94:
Everything works so far! Thanks a lot for this, awaiting new features to be implemented!
[ONE Original Android Development] hepy117:
I have givem all apps within the device admins access
[ONE Original Android Development] Bluffer94:
Little OT, but,

Ocassionaly when I open Google now and tap on the search bar it looses focus and keyboard disappears again, which leads to a glitch and me tapping Google now cards instead of the keyboard.

This gets so annoying.

It happens with stock and SwiftKey.

Does anybody else experience this bug?
[ONE Original Android Development] casshern94:
succeeded install the rom via twrp 2.8.6

but opengapps cant install, error execute binary error.

but still, i managed to install the slim gapps.

but then the device just stuck on the loading screen...cant boot...any help?
[ONE Original Android Development] abhibnl:
Thanks! Will flash it on my device as well.

[MENTION=4898097]arter97[/MENTION] posted on his twitter, and i quote

"Enabling native root support causes su daemon to load continuously -> battery drain"

"Pro tip for CM users who uses SuperSU :

Make sure to disable "Root access" from "Settings -> Developers settings"

That's why i was willing to give SuperSU a try again. What's your thoughts on this matter. I, clearly, am not an expert so can't comment anything at all. :eek:
[ONE Original Android Development] Sultanxda:
Once upon a time, I nearly went insane when I tried to tweak the in-call microphone. I'd rather not play with it anymore.

User builds won't come until a stable CM13 branch comes.

Settings chosen in the secret menu are not permanent, and are reset upon reboot. You can try changing ro.telephony.default_network to 3 in build.prop and see if that does anything after a reboot.

I tested Android Beam with a Galaxy S2 and it worked fine.
[ONE Original Android Development] ItsBeepo:
Can someone post battery stats on this?
[ONE Original Android Development] mamelouc:
Hi [MENTION=4800121]Sultanxda[/MENTION]

Could you add the option to compile the kernel with NFS support in your next build plz?

Thx in advance
[ONE Original Android Development] casshern94:
[MENTION=4800121]Sultanxda[/MENTION] i've succeeded install the rom via twrp 2.8.6

but opengapps cant install, error execute binary error.

but still, i managed to install the slim gapps.

but then the device just stuck on the loading screen...cant boot...any help?
[ONE Original Android Development] ryanmat:
In the OP, but since it's Friday: https://github.com/sultanxda/android_kernel_oneplus_msm8974/commits/cm-13.0-caf

Spamming the board won't help you any faster. Did you follow the instructions on the OP?

Installation instructions (for first-time installation):

First, perform a backup of your existing setup, and then perform a clean install (wipe /data and /system; TWRP is recommended). 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.

If you get an error when trying to install ("oppo.verify_trustzone" error), then first you must install/use TWRP recovery 2.8.6.0 (TWRP 2.8.7.0 cannot properly update the modem). Next, download and flash the latest official CM13.0 nightly. Then, without rebooting from recovery, wipe /system and flash my ROM. This process is necessary to update various firmwares (including TrustZone), as the updated firmware is needed by my ROM. After flashing my ROM, flash a Google apps package, and then reboot.
[ONE Original Android Development] casshern94:
sorry, doesnt mean to spam the board, just that nobody notice my prob.

and yes i did follow ur instruction.

factory reset wipe then the rom+gapps(i use slip, cuz opengapps gives me error)

im using twrp 2.8.6.0 btw
[ONE Original Android Development] ryanmat:
Did you flash Official CM13 Nightly and then flash Sultan's ROM right after?
[ONE Original Android Development] mamelouc:
thx [MENTION=3529053]ryanmat[/MENTION]

Didn't see it ... Looks like busybox mount doesn't support NFSv4.
[ONE Original Android Development] Paoliz:
I have 1/1 ROM, can I update it to 6/1 ROM woth dirty flash? Or should I flash a cm13 nighly and dirty flash this rom?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] L0X0R:
Didn't work sorry.

1. I have no idea why it's ignoring what's selected in the mobile network menu in settings.

2. why is it happening now? it never used to do this.

3. would it be more of a CM thing to fix instead of you?

4. build.prop fix seemed to be ignored as well, its still 3 in there but still auto goes to lte. :/
[ONE Original Android Development] venky716:
Turn the OK Google detection from app on.

I faced this a while ago and turning that on seems to solve it.
[ONE Original Android Development] payne_307:
Can someone tell me what's this happening on CM13 - http://www.cmxlog.com/13/bacon ... Seems they are integrating Snapdragon camera with the next set of nightly. Is it just a shift of the camera app or there is more to it in terms of camera and picture quality?
[ONE Original Android Development] raul.lopez1958:
They have seen that the snapdragon of [MENTION=4800121]Sultanxda[/MENTION] is good and they have copied :laugh::laugh::laugh::laugh:
[ONE Original Android Development] payne_307:
Really? Hope its more than just changing the apk from Camera2 to Snapdragon Camera
[ONE Original Android Development] raul.lopez1958:
It's a joke ... but I would not be strange :laugh::laugh:
[ONE Original Android Development] RotesMeerJogger:
In OP is the answer at your question but yes u can! (only dirtyflash sultans ROM) :cyclops:

---------- Post added at 12:18 AM ---------- Previous post was at 12:13 AM ----------

i don't know what some people do but sultans ROM works like a charme. every version! newest version updated my baseband, all work fine, i'm happy :D

THANKS A LOT Sultanxda! :good::good:
[ONE Original Android Development] Bluffer94:
Thank you sir!

That seems to work out!
[ONE Original Android Development] vinistois:
Not sure what is going on here but I sure could use some help.

I was running a build from early December, CM13 Sultan Unofficial.

I decided to download the update last night using the built-in CMupdater. December 6 build. I flashed it and rebooted and it's stuck at the pulsing CM logo.

I've since tried wiping system, cache, etc and trying again - same result.

I tried flashing CM13 official Dec 6th, then the Sultan file again - same result.

What is going on here? Nothing will boot!
[ONE Original Android Development] 69gm:
I think you need to clean flash. BTW, what recovery are you using? That might be the culprit as well...

After wiping everything except internal storage, flash LATEST CM13 Nightly, then without reboot flash the LATEST Sultan ROM. Flash Gapps. See if that works for you.
[ONE Original Android Development] vinistois:
Thanks just tried that but still the same endless logo boot.

Shouldn't' I have been able to just dirty flash? The build I was on was December 21st. I just recovered that backup and it is working fine, although I lost all my settings which is massively annoying.

What kind of thing can break an upgrade process like this?
[ONE Original Android Development] highdiver_2000:
That is cold.

Check your themes and dpi settings? Never encounter this problem before.
[ONE Original Android Development] whee90:
In between were some modem modification updates.. Maybe that's it.

Try one of the h2os modems posted in the thread before flashing a newer suntan
[ONE Original Android Development] vinistois:
Ok What the F is going on here.

As I said restoring to a Dec 21 build worked fine. So I tried to do it totally clean, formatted everything and started over. CM13 official nightly, then wipe system, then Sultan nightly, then Gapps, and BAM stuck on logo. What?? Nobody else has problems with the Jan 6 nightly??
[ONE Original Android Development] Khizar:
Sounds like a bad download, check the md5 of zip.
[ONE Original Android Development] renaltosonylevi:
OK just to make sure. What recovery are you using?

Today I have done a clean install with no issues. My phone was previously running a different rom with outdated firmware.

Using twrp 2.8.6.0.6(my favorite 2.8.6.0 based recovery)

Wiped everything except internal storage.

Flashed official cm 13 01/07 build.

Flashed sultan cm 13 01/6 build.

Flashed open gapps-arm 6.0 stock 01/08

Rebooted and setup with no issues.

Most likely a bad download or you might have downloaded the wrong gapps by mistake.
[ONE Original Android Development] vinistois:
I am using 2.8.6.0

I just tried to wipe the internal data partition and it hung. Forced a reboot and then all my partitions were messed up. So i have now decided to flash twrp 2.8.7.0 and try again from scratch. Anytime I try to wipe partitions it gives me errors E: unable to mount /data, and windows won't let me copy files to the device anymore. AWESOME. ADB push commands to push the file to the device also hang. How to I completely format the various partitions?
[ONE Original Android Development] renaltosonylevi:
Nothing sharpens the mind more than having to un brick your phone. Have a look at some of these guides. I suggest the automated return to stock via fastboot/adb might be a safe bet. But read carefully, read like your phone depends on it then read some more.

Edit: stupid xda link to post #4 and #7 comes up.

Look at post number #4
[ONE Original Android Development] tomkozuki:
Has anybody with the status bar time/clock freezing been able to fix it? It's driving me crazy. I've tried everything I can think of and can't figure it out.

The time freezes until I lock and unlock the phone.
[ONE Original Android Development] Khizar:
Try this. Go to settings > apps > settings icon > all apps, disable battery optimization for clock.
[ONE Original Android Development] se7enlyn:
after flashing cm 13 official, don't wipe anything. just flash sultanxda's rom and gapps. then wipe dalvik+cache and then reboot.