yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] esun:
Lazy post. I went from the new year build to the latest 11 jan. Now several apps are slow from time to time. Snapchat froze and won't start, Instagram froze when opening a thumbnail. Random hangups and the phone has restarted at least once since yesterday.

:)
[ONE Original Android Development] jdtimothy:
I haven't rolled back to a earlier version yet, but the newest Jan 11 build I cannot discover or connect to my mi band via Bluetooth. Has anyone else had any problems connecting to Bluetooth devices?
[ONE Original Android Development] skymera:
Yeah, it's been mentioned a handful times over the past few pages.

I rolled back to 06/01 build and my Mi Band 1S connects fine.
[ONE Original Android Development] sax0406:
All the kernels have throttling. Some may be more aggressive and some may be less. But it is present nonetheless. You can search the kernel/ROM threads and you will find posts about throttling. e.g. Intellithermal is present in ak kernel, Boeffla uses the stock mpdecision/thermald for controlling CPU frequencies (as in stock CM), etc.
[ONE Original Android Development] klausgra:
I started use Sultan's CM13 from the 1/1/16 nightly and now I'm on 11/1/16. In these twelve days I've no problem at all. The ROM is pretty stable and flawless, I don't want COS anymore.. The only little problem is in the contacts: I have Telegram and WhatsApp contacts separate from the original contacts but with the same name.

Thank you for your work Sultan! ;)
[ONE Original Android Development] Mr hOaX:
That's a known bug

One thing you can do now is that

- Open Contacts App

- Click on 3 dot menu (top right)

- Choose

Contacts to display

- Customize it or select any one from the list (if it shows some list to you)

This will hide duplicate contacts, but won't eliminate them!
[ONE Original Android Development] ryanmat:
I was digging into the bluetooth issue and it seems like this commit: https://github.com/CyanogenMod/android_system_bt/commit/80a7a7dc3125e463d06e7215feb3f5a27c4f3352 could be the cause of the problems. I don't know if [MENTION=4800121]Sultanxda[/MENTION] can or wants to debug/revert it in his builds. Otherwise, everyone with the issue should go here: https://jira.cyanogenmod.org/browse/NIGHTLIES-2286 and vote on the issue so CM team can fix it.
[ONE Original Android Development] lifelesslegend:
This problem is also present in [MENTION=2040569]jgcaap[/MENTION] cm13 build.
[ONE Original Android Development] flyfire04:
I'm on build 06/01. With basebad .4.01.c7-00011-M8974AAAAANAZM-1 with the newest google play services version.

I've never had problems with this awesome ROM. Even though this might not be specificly ROM-related I want to ask for help or if anyone else is facing this issue.
[ONE Original Android Development] novren:
Is anyone else getting a huge wakelock because of Facebook messenger? Had to uninstall it, kept the phone awake for 2 hours in a span of 4.
[ONE Original Android Development] Khizar:
Time to clean flash?

Fb apps are known battery drainer. Fortunately I haven't had issues with them on MM.
[ONE Original Android Development] athorax:
Anyone else having issues with gmail not syncing? I have sync setup, but randomly I'll notice I haven't gotten any alerts in awhile and will open the gmail app and refresh and all my messages come in.
[ONE Original Android Development] yaltis:
SOLVED

ty

the problem (and no one mention it on 704n pages)is that i was using twrp 2.8.6 but the Multirom version.after your help i flashed the regural one.

and finally works!!1

i was using multiron although i didnt want to multirom sultans rom with any other .

ty again
[ONE Original Android Development] ryanmat:
I did have that problem, I deleted my gmail app, and then reinstalled it. That seemed to fix it. Also had to do the same thing with Play Music app.
[ONE Original Android Development] athorax:
Just realized it is also affecting my Rewards app. Just force synced it and got 3 surveys that were back logged. I'll try reinstall and clearing data.
[ONE Original Android Development] mattgoldey:
It's Doze. Go to Settings --> Battery --> 3-dot menu --> Battery optimization, then select "All apps" from the drop-down menu and turn off optimization for GMail and Google Opinion Rewards. This fixed it for me.
[ONE Original Android Development] ovtovaz:
d2tw lags , sometimes it takes a few seconds for the screen to turn on

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] Zorachus:
Similar issue here. Sometimes need to double tap multiple times
[ONE Original Android Development] esun:
You mean format /system and flash latest image?
[ONE Original Android Development] Sultanxda:
DT2W is like pressing the power button to wake up the device, so any lag after using DT2W is not related to DT2W.

I've already done a lot to make the device wake up faster. I don't experience any lag when waking up the device, so there's nothing more I can do in this regard.

This is handled by the touchscreen firmware, which I cannot modify. If DT2W works at all for you, then that means my touchscreen driver code is working correctly and that there is nothing more for me to do.

The touchscreen firmware decides what is a valid double tap, not the touchscreen driver.
[ONE Original Android Development] Zorachus:
Off topic,

my boring homescreen on this amazing ROM
[ONE Original Android Development] xeeee:
Hey guys,

Shouldn't we have an option to login in the Cyanogenmod or Cyanogen Account (in the Settings), so we could remote locate/wipe the OPO?
[ONE Original Android Development] highdiver_2000:
No, you won't. I am on the same version. Recovery is something you don't change when it works
[ONE Original Android Development] anseric:
Today I wanted to change my language from duth (Belgium) to English (US).

When I changed it the following error kept popping up: "unfortunately the process android process acore has stopped"

The theme engine also kept crashing. I tried clearing my contacts cashe, etc but nothing worked.

I eventually reverted the language back to dutch wich got rid of the problem...

I still want my system to be in english tough
[ONE Original Android Development] LucentBirch:
I haven't had this issue ever for this phone, but the last few days I have been having Android OS (Kernel) keeping my phone awake for an hour plus some...anyone else experiencing the same?
[ONE Original Android Development] renaltosonylevi:
Agreed why change if you know what you have works.

Also don't forget that bad things can happen when you try to restore a backup on a recovery different from the one that made it.
[ONE Original Android Development] dorian1326:
[MENTION=4800121]Sultanxda[/MENTION] I don't know if you remember, but I was one of the users complaining about the inaccurate battery percentage a couple months ago. Everyone was saying that the battery was bad and it was gonna die soon. Well, that is not the case. It's something definitely with the software (and I'm glad you still looked into it). What I found is that in order to work properly for me was to let the phone charge a little more (30min - 1 hour) after it shows 100% percentage. After that, it goes all the way down to 1% as it normally should (and lasts about 4:30-5 hrs SOT) instead of shutting down at like ~20%, heck it even shut down at ~40% a few times.

I will try to charge it till it says 100% and immediately remove it and see if it's gonna last till 1% or die at ~20%, maybe the new changes you made solved it. I'll post back with the results.
[ONE Original Android Development] Romman0:
You can do the same with the built-in Android device manager, from your Google account. Settings / security / device administrator.
[ONE Original Android Development] critofur:
Oh, I do use profiles, but it's happened not while it wasn't plugged in. I really like profiles and don't want to not use them.
[ONE Original Android Development] FloorFox:
Had this problem. That's why changed rom. Report back if it's fixed
[ONE Original Android Development] hamma:
It´s fixed. I never had this problem.
[ONE Original Android Development] FloorFox:
You really can't tell it's fixed because you never had it.
[ONE Original Android Development] hamma:
Maybe because it never really existed?
[ONE Original Android Development] siddardha21:
[MENTION=4800121]Sultanxda[/MENTION] I had phone shutting down at 20% on cos 12.1 rom and I haven't faced this issue on your rom untill 11 jan update. Now I again I've the problem where my phone shuts off without reaching 20% also. :( so it's probably cm's fault and may be you could revert the changes you've made?! :( thank you.

Edit : have been running this rom since November and never had the problem. It reappeared with the latest build again. So it's definitely with the new cm's battery thing.
[ONE Original Android Development] Sultanxda:
How easily/often can you reproduce this bug?

Some users on official CM are affected by this bug as well. It isn't limited to my ROMs.
[ONE Original Android Development] nkanish2002:
Hi, I recently installed this ROM and I am quite happy with it. ?

I have question though, while tweaking the CPU prefs on Kernel Auditor, I noticed that the maximum frequency is 1958Mhz. Isn't OPO's Max frequency around 2.5Ghz? Is this a problem? If I change the kernel, would it allow throttling up to 2.5Ghz?
[ONE Original Android Development] xodeus:
You can disable the cpu underclock. See OP.

Sendt fra min A0001 med Tapatalk
[ONE Original Android Development] inversechi:
I had an issue going from 6 to 11 with the CPU hitting 100% amongst other things. Rolled back to a build from last year as going back to 6 (fresh install) titanium backup had permission issues with accessing the backups.
[ONE Original Android Development] alonroz:
Serious wakelock issue with Facebook and Messenger apps

Hey guys.

Running the Jan 11th build now, been updating it with every build for the past month or so. Starting from about a week ago, I have this wakelock issue with Facebook apps, both the main app and the Messenger. I've attached screenshots.

What I've tried:

- Greenified both apps (Greenify in the new Boost mode)

- Amplify - set to be allowed once every 2400 seconds.

- App Ops - blocked both apps from waking up the phone.

Still, the issue persists. I keep getting hundreds of wakelocks per day from both apps. I've no idea where too progress from here. I'm not going to delete the apps, as I use both quite extensively. Any help will be appreciated.

Thanks!

EDIT: Just wanted to mention that except for these two wakelock issues, my battery life has been phenomenal since upgrading from 12.1. Doze really does make a huge difference.
[ONE Original Android Development] exadeci:
Had the same issue so I tried to change the permissions on the "sd card" and other thing what I did was copy my data on my computer, format internal and copy it back.

[MENTION=1449932]alonroz[/MENTION]: Nothing to do with this rom, Facebook apps are battery drainers that's it. I don't have the Facebook app because if you login on chrome it will ask to access the notifications and then you'll have them like the facebook app without the drain
[ONE Original Android Development] alonroz:
I know it's nothing to do with the ROM directly, just wanted to see if anyone else had this issue and was able to solve it on Sultan's ROM. I imagine I'd have the same issues on the CM13 nightlies. But again, this issue has never existed for me and I've been running Sultan's builds for at least half a year and this issue started only a week ago. Never had any issues with the FB apps before.

My biggest problem is that I don't understand why this specific service is not blocked by Amplify or Greenify when I've clearly set it to be allowed only once in 40 minutes...

Service name (as it appears in my screenshots) is:

*job*/com.facebook.orca/com.facebook.bugreporter.scheduler.LollipopService

Is there any way to block it from waking up the phone besides the 3 ways I've tried?
[ONE Original Android Development] Biiz:
i've searched alot for facebook hibernation, or decrease the frequency of his itswakelocks...but as you saw, you cannot greenify facebook. What i learned was that facebook is programmed like a system app (do not build science from my words, lol) so even with privacy guard you cannot deny the auto wake-up, keep-awake etc

i suggest you to try FOLIO, is a great app which use the official API from facebook and for me, works great
[ONE Original Android Development] Sultanxda:
Flash this kernel and see how it goes: newer version

I made my own battery driver (for our BQ27541 fuel gauge chip) using the vanilla reference driver from Qualcomm. If this kernel still has your issue, then it's not a software problem (or it's a software problem that's too difficult for both the OEM and me to solve).
[ONE Original Android Development] totoybibo:
New to this rom and all i can say is it's buttery smooth! One question, is there a way to remove the root icon in the status bar? Ty
[ONE Original Android Development] soralz:
I don't know if this has been asked before, but this is my first time posting in this thread... Anyway anyone knows why we can't install SuperSU on CM13?
[ONE Original Android Development] Khizar:
Like it's been mentioned multiple times in the thread, only way right now to disable it is by using CM settings xposed module.
[ONE Original Android Development] siddardha21:
Just flashed you kernel. Will report back how it goes. As I mentioned. I had problem with official cos 12roms. Never had this problem on your rom till 11th jan build. Will see how this new calibrations goes. Thanks for your effort.
[ONE Original Android Development] madsponge26:
Try to use xposed..
[ONE Original Android Development] Play!Ya:
You can flash SuperSU right after flashing rom and gapps... I'm using 2.66 beta at the moment and no issues whatsoever.
[ONE Original Android Development] alonroz:
Just a quick update on my issue here, for other who may experience the same wakelock from *job*/com.facebook.orca/com.facebook.bugreporter.scheduler.LollipopService

It seems now that the issue only exists with their beta versions. I've left the beta programs for both apps and installed the normal versions and the wakelock seems to have disappeared. I'll update later if it comes back, but all seems good for now.
[ONE Original Android Development] netcitizen:
I'm getting wake lock from the Facebook app itself. I'm not on beta version
[ONE Original Android Development] Zorachus:
Everyone using the actual Facebook app;

Delete and uninstall that evil crapware Facebook app, there's ZERO reason to have it. The app is a known battery hog, and seems to always cause an issue with something.

The mobile site works just fine, that's what I use, and it's great. And who the F. cares about FB notifications ? First world problems huh ? Humans got by just fine without FB a few years ago.

My advice, just use the mobile site for FB.
[ONE Original Android Development] RedBux:
Had an issue with Root Explorer...........RE failed to run

Tried RE 3.36 and 3.3.7 No Go

Any suggestions for better Explorer wit rooted
[ONE Original Android Development] Goldnessel:
No issus with RE here... But you can try the ES Datei Explorer. If you are rooted, it will ask for root rights...
[ONE Original Android Development] thefraggle:
After Root Explorer stopped working for me, too, I am now using Root Browser

https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree&hl=de
[ONE Original Android Development] svil3:
Agree with all of this, but with chrome browser you can have push notifications for facebook and other sites, so, actually there's nothing to lose here, and all the battery life to gain :p
[ONE Original Android Development] honor_77:
Flashed the Jan 11th build. Everything's seems to be working fine here.
[ONE Original Android Development] rayturner:
Response to setting wallpaper problem.

I, too am unable to change from default wallpaper for last several updates. I also asked your question here about this, but received no response.
[ONE Original Android Development] Tajnymag:
Could the changelog be implemented in the cm updater. It would be great to quickly check if I should bother with downloading the OTA or not :)

Odesláno z mého A0001 pomocí Tapatalk
[ONE Original Android Development] goodsmile:
Anybody using steam app ? I am having a network error with the app. See the screenshot.
[ONE Original Android Development] ryanmat:
Are you using an adblocker app? It looks like you might need to whitelist the Steam urls.
[ONE Original Android Development] goodsmile:
Nop not using any adblock. Is it working on your phone ?
[ONE Original Android Development] skiely666:
Should be fixed in next update.

http://review.cyanogenmod.org/#/c/127937/
[ONE Original Android Development] Sultanxda:
Here's a new version with some bugs fixed: View attachment Sultan-kernel-CM13-New-Fuelgauge-2.0_2016-01-13.zip

[MENTION=6480870]dorian1326[/MENTION] you may be interested in this as well.

Anyone else who wants to try this kernel should try it and report back. For me at least, battery percentage readings are more accurate. You might get very slightly better battery life, too.
[ONE Original Android Development] leomd333:
Running the 11th build with no issues! (Haven't tried Steam yet) but stable as a rock so far, cheers Sultan! ?
[ONE Original Android Development] Zorachus:
I'm happy to be guinea pig to help out :)
[ONE Original Android Development] debsahu:
You can use my workaround till it gets fixed http://xdaforums.com/showpost.php?p=64770406&postcount=7089
[ONE Original Android Development] o-l-a-v:
Hi! Just got myself a used Bacon. It was stock but is now running sultanxda cm13 like butter :)

- I started by unlocking the bootloader. (adb oem unlock)

- Then boot twrp 2.8.7.0.5 materialized from fastboot.

- Fotmatted everything.

- Sideloaded cm13 nightly (13/1).

- Wiped system.

- Sidloaded Sultanxda cm13.

- Sidloaded the kernel a few posts above.

- Sidloaded latest gapps from open gapps.

Now its up and running, stuff seems to be working :) Will report if I find bugs and stuff like that.

Thanks!

Oh, by the way. I tried to format data and cache to f2fs. CM13 nightlies' kernel supports it (I tried it before your rom, it booted), but SultanXDA CM13 bootloops. So F2FS support is something I'd kindly wish for in future updates :)
[ONE Original Android Development] Bryski:
Any custom kernel work with this rom that allows custom screen colour adjustments?

Cheers
[ONE Original Android Development] Dzhedaj:
Using this since Jan 1st, no issues so far.

One question though - avoid accidental wake up(proximity sensor check) is missing in settings. Is that simply a CM13 "feature"?
[ONE Original Android Development] Raider1284:
With the latest 1/11 build I'm having a problem where Root Explorer crashes instantly and consistently. Anyone else having this issue? Tried uninstalling and reinstalling the app, clearing app cache/data, etc without luck. Other root apps seem to work without issue though.
[ONE Original Android Development] darksonic:
I've tried flashing both 01/06 and 01/11 and both of them cause my phone to lock up seconds after booting. 01/01 works for me but occasionally I'll lose data (exclamation mark over the LTE signal).
[ONE Original Android Development] Brian325:
Personally I get a kick out of reading all the drama people have with this ROM....meanwhile I'm over here using it with ZERO issues. ?
[ONE Original Android Development] rondinelle:
Appear unrooted?

I've searched the thread and haven't found this issue raised (well it was raised here by drewdatrip but as a complete "unroot option" not just to appear unrooted like SuperSU can do).

I'm loving this ROM and I know that root is built-in, but just wondering if there is a way to fool apps that will not work on a rooted phone that the OPO running this ROM is not rooted. Even when root is disabled in Developer under Settings, some apps report the phone as rooted and thus won't run. If there is a solution out there, I'd appreciate any advice...
[ONE Original Android Development] Prodromodinverno:
I'm trying it.
[ONE Original Android Development] darksonic:
Yeah it's certainly hilarious. What a great addition to the conversation. Thank you for your opinion.
[ONE Original Android Development] Zorachus:
Me too, I guess I've been lucky, really no issues to speak of. "It just works" And I have several Xposed apps running without issue.

Best CM13 ROM IMO
[ONE Original Android Development] D_black84:
lightning kernel
[ONE Original Android Development] kaustubhatzenith:
I have an issue with this rom.... Sometimes the ringtone doesn't play but only vibrates...Only a reboot fixes the issue
[ONE Original Android Development] Sultanxda:
The included kernel supports custom color adjustments via LCD KCAL and LiveDisplay.

I removed this feature because it's completely broken in CM13. It does not work *at all*.
[ONE Original Android Development] Acxjet:
I'm curious.. What does this rom pack which make it special? I'm curious since I know nothing.
[ONE Original Android Development] kalapapa:
Check op
[ONE Original Android Development] Acxjet:
Read it. Though. I'm curious on the kernel. What special features does the caf have? I know it got custom thermal. Just curious
[ONE Original Android Development] Xoomong:
No..never experience such issue in 1/11 build.
[ONE Original Android Development] Khizar:
That's a known CM issue. CM recently changed from busy box to toy box, which broke root Explorer. The app needs to be updated.

I personally switched to solid Explorer and I think I am a convert. I don't think I'll even return once root Explorer is updated. And this is coming from root Explorer user/lover of 5+ years.. LOL

I had that once when I first flashed the latest build, haven't had it again.
[ONE Original Android Development] arachne:
I have this problem too, with syncing my Fitbit One via Bluetooth. Took me ages to realise that 11/1 was the day I switched from CM 13 nightlies to sultanxda and that's when the problem started for me. Now to find the 06/1 build...thanks for posting about this as I wouldn't have realised it was an issue!
[ONE Original Android Development] alroger:
BlueTooth 4.0

Hey. Working good here.

Good news.. I decided to test my PowerUp 3.0 wich requires BT 4.0, and with this kernel it works!
[ONE Original Android Development] ~KV:
Maybe that's the reason why even build.prop can't be edited?
[ONE Original Android Development] JimJ2Mz:
Wow, lots of things I still need to discover. Thanks.
[ONE Original Android Development] sgroimax:
I've dirty flashed the latest one but my phone Info's show me that I'm currently on 20151108 instead the download say me 20151109. So I tried to search updates via ota but anything about 9 build was found. Any one has my little issue?
[ONE Original Android Development] Zalbu:
Somebody mentioned the buildprop editor app from the Play Store a few pages back and that worked for me but I'm on the Nov 9 build
[ONE Original Android Development] 1ceb0x:
pretty much i suppose.

the Build date shows indeed 8th of November, but the Cyanogenmod version (which is the name of the zip) says 0911 - which is correct. Sultan forgot to compile a new build.prop with the correct date :). Will be fixed in the next builds.
[ONE Original Android Development] 4b3ck:
Naptime works.
[ONE Original Android Development] Antoine Vdb:
Lol it's the opposite ! People couldn't boot with open but it worked with slim. Although I think OpenGapps have fixed the problem
[ONE Original Android Development] shaheen7m:
Xposed is the deal breaker for me. Waiting for the xposed for M
[ONE Original Android Development] 1ceb0x:
what's the point of your reply?

how is this going to add something to the thread?

oh yes.. more clutter. keep these replies to yourself bro, unless you have something useful to add to the discussion - like bug reports or solutions to problems.
[ONE Original Android Development] lullo88:
Can you please post a screenshot that shows how those 2 option should be? Because i have both disabled but still that huge battery drain...