yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Mike_1996:
A few pages earlier sultan has explained the reason why Lightening is changing fast, that it locks the charging current at a high value which is not an acceptable solution.

I personally use stock COS 12.1 with AK kernel and sultan's CM13 as a MultiROM secondary. May flash another stock as secondary just to test this, but for now I'm unable to help further.
[ONE Original Android Development] nauj27:
I get the same message about screen overlay and the next screen shows a list of apps but not the one that raise the problem. I do not have xposed. It is a clean install v11 + stock gapps + SuperSU 2.62.
[ONE Original Android Development] NeoCreator:
Read big red text at first post.
[ONE Original Android Development] BarnOwl:
Well, I can confirm it works like a charm with Supersu 2.62. My TB is working without problems.
[ONE Original Android Development] EdenGottlieb:
1. Dirty flashing since the beginning of the month. Latest build fixed reboots, no problems with touch vibration or slow charging whatsoever.

2. Ampere is known to be very inaccurate, I reviewed it in the past and found the readings to be very inaccurate.

3. Latest build has tons of stutters, feels very sluggish. I don't know why.

4. Mobile Radio Active is killing my battery. Might be dirty flashing problem, just reporting to check if other peoplr have this issue

5. About "Prevent accidental wakeup", I think I may know what the problem is. Its' code is located in PowerManagerService, I gave it a quick look. I can see there's a timeout for the Proximity Sensor, if the sensor doesn't wake up on time the device simply turns on so the user is not delayed. Maybe that timer is too short? Our sensor may be too slow, maybe changing the timer a little can give the sensor enough time to do that. I'd do that but I don't have enough horsepower to compile and decompiling and recompiling services is living hell (if that's even possible).
[ONE Original Android Development] Mr hOaX:
5. Following features can be unlocked from Gravitybox (Xposed Module) without any crash or bootlloop

- Pin Quick Unlock

- Double tap to sleep on the lockscreen

- Proximity sensor: Prevent Accidental wake-up

- Data traffic monitor

- Many more features and tweaks

I only found that only Quick Settings tweaks gives crashes.

-
[ONE Original Android Development] expiredd:
Mobile radio active is making me think to go to iOS I can't believe after 1 year Google hasn't fixed this yet.
[ONE Original Android Development] xxDominatorxx2:
Dirty flashed latest build over 12/1 build.

So far so good.. No micro stutters or slow charging,, yet to test battery life
[ONE Original Android Development] ericmaxman:
Clean flashed the latest 11 Dec build. Can't seem to search for my Mi Band.

Other users said that 6.0.1 fixed that issue. Smart Lock is the casualty now.
[ONE Original Android Development] nauj27:
Yeah, I read it, but:

Without SuperSU, Titanium Backup was not able to get root access.

Running /usr/xbin/su on a Terminal does not bring a root shell without SuperSU

SuperSU 2.62 systemless beta version works fine with this ROM
[ONE Original Android Development] TCattd:
https://code.google.com/p/android/issues/detail?id=190396

Priority: small.

It's sad, really.
[ONE Original Android Development] exadeci:
87 Stars .... If you want this to get fixed you have to star it too, it helps it gain visibility.
[ONE Original Android Development] NeoCreator:
[MENTION=2516427]nauj27[/MENTION] Settings - Developer options - Root access - Apps and ADB activated?

My TB works fine with default CM root without SuperSU.
[ONE Original Android Development] FloorFox:
Yeah peeps. Let's vote this up
[ONE Original Android Development] raul.lopez1958:
I can not see NTFS disk via OTG ...

Edit: with ES File Explorer Pro work fine, i see ntfs HD OTG
[ONE Original Android Development] nauj27:
[IMG="You Win This Time"]http://cdn.meme.am/instances/500x/63058816.jpg[/IMG]

Thank you, maybe that tip should be also in the first post.
[ONE Original Android Development] raul.lopez1958:
Run with supersu v260 ... no problem.
[ONE Original Android Development] :
1. I haven't had issues using the same apps and data on other ROMs, Lollipop, and, yes, as mentioned, AOSParadox 6.0. And it's a general stutter, happens everywhere, not necessarily tied to one app.

2. I flashed the zip you posted. Initially when I went into V4A, it showed the status as being "Abnormal". Audio was being routed correctly through the speakers, however. I went back into V4A and it's telling me to install the app again. So that's not working. V4A remains unusable.

I understand that it is experimental, and that is why I'm posting all these bugs and issues I'm having. Granted, V4A isn't a ROM issue, but the stuttering, and the horrible quick settings control is, in my opinion.

Also, another bug, landscape with nav-bar activated produces weird results when the notification drawer is slid down. Check screenshots for reference.

EDIT: V4A fixed. Used this. Your mileage may vary, not responsible for yadda yadda.
[ONE Original Android Development] rajarshi10:
OPO is not going to sleep on this rom. What can be the reason for it?
[ONE Original Android Development] dasti555:
V4A is working fine (y)
[ONE Original Android Development] georgek_gr:
Hi everyone! I'm not sure whether this is a bug or a feature but my screen keeps turning on (not at full brightness, rather around 50%) every now and then. At first I thought it was because of notifications but it happens when there are no active notifications as well. Does anyone know how to prevent this from happening?

Thanks a lot for your help!
[ONE Original Android Development] aimcr7:
1. Have you tried reflashing or switching kernel? Are the microstutters gone?

2. Pretty sure it was working for me in the older build, but I stop using v4a since 1/12 build.

So far I am not experiencing any stutters, I can confirm about some graphical glitch and almost unusable qs control tho.

Since no one reporting this, but it seems now on tap is still hit or miss on hardware button in the 12/11 build while it works everytime on navbar. And yeah I actually use it and not just forgot about it after the first day on MM, I found it quite handy feature when receiving a long invitation message or looking for a location.

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

Try wakelock detector or betterbatterystats to find that out, one of your app keep your phone awake
[ONE Original Android Development] EdenGottlieb:
Does it wake up on a table or in your pocket? If in your pocket, it's probably double tap to wake. Turn it off, as "Prevent Accidental Wakeup" doesn't work right now.

If it happens when screen isn't in contact with any surface, my only idea is ambient display (Pretty black screen with only clock and notifications). Turn it off in display settings
[ONE Original Android Development] :
1. I have tried reflashing - I had to because of how the V4A posted here screwed up my setup and routed all audio through my earpiece speaker. It wasn't using the loudspeakers at all, and I couldn't uninstall the driver because every time I went into V4A, it asked me to install the driver. So I factory-wiped, reflashed the ROM, and the microstutters still exist, so it wasn't just a bad flash before that caused it. I don't believe I'll be reflashing this nightly, seeing as how Sultan updates his ROMs fairly regularly, so I'll just clean-upgrade then and hope the stutters are gone. Some times the loading circle animation stutters and that's just annoying as hell. Even more annoying is that if I tap on something and it stutters, it "pools" the touch - making it behave like a long-tap, even though I lifted my finger a long while ago. This has happened admittedly only several times but it greatly impacts performance and usability. Also, Nova Launcher seems to be prone to the most lag and stutters that I've noticed - I shall try uninstalling and re-installing to see if that's where the problem is, although I doubt one app would have such an effect on the system as a whole. I haven't flashed any other kernels yet, because everybody seems to be raving about Sultan's kernels and optimizations and what not, but I may just have to. I used to dabble in flashing kernels on Lollipop but I thought Marshmallow would render underclocking, undervolting and everything else obsolete. Clearly that isn't the case, because I'm getting massive drain due to Google Play Services today. Speaking of which, anyone else noticing that?

2. V4A worked for me on 6.0 on AOSParadox, too, it wasn't working on this ROM. But I managed to get it working, finally; refer to my edit on the parent comment you quoted if you're still interested in getting V4A running.

I wouldn't say QS is "unusable." What I would say is that in the aim of getting it to look better, it's lost a lot of its functionality and customizability, and it leaves a lot to be desired. I understand that having QS editing available within the QS dropdown is ideal, and kind of intuitive, but I would prefer a more ghetto approach if it means it does everything I want it to.

Also, I can confirm that Google Now On Tap works perfectly each time with the navbar. I haven't tried it with the hardware buttons.

EDIT: New bug, double-power-button-to-camera doesn't work even when turned on. Was working fine yesterday. Looks like I'm just going to have to reflash the ROM and maybe that'll iron out the kinks.

---------- Post added at 09:19 PM ---------- Previous post was at 09:18 PM ----------

Thank you for your extremely valuable input.
[ONE Original Android Development] dasti555:
This : http://xdaforums.com/showthread.php?t=2524485 > set SELinux to permissive

This : Attachment - Flash via recovery

Go to application > install driver (i'm using that middle option good quality or how its called)

Reboot

Working
[ONE Original Android Development] :
This didn't work for me. The setting doesn't hold, especially not when you insert earphones into the jack. Doesn't process the audio stream, changing settings doesn't work. After you reboot, it asks to reinstall driver. SELinux set to permissive. I fixed it using another method (posted in the parent comment), but thanks anyway. Maybe this will help someone.
[ONE Original Android Development] raul.lopez1958:
Nice blur effect to implement the rom
[ONE Original Android Development] aimcr7:
Not the qs, I mean the qs settings.

Your link gave me invalid thread id on tapatalk will try on chrome later.

Double power button to camera works fine for me, just tried it.
[ONE Original Android Development] :
Blurred system UI? Had problems with Heads-Up notifications with that. Kept blurring the entire screen when I got a notification and that was annoying af.

---------- Post added at 09:35 PM ---------- Previous post was at 09:34 PM ----------

Doesn't work for me today. Worked fine yesterday. I guess I'll just have to start everything over.
[ONE Original Android Development] blinoff82:
How?:confused:
[ONE Original Android Development] BeingEEE:
Viper4Android running with SELinux Enforcing :victory:

Flashed the zip from this thread: http://xdaforums.com/nexus-6/themes-apps/viper4android-t2952137

Follow the instructions correctly.

SuperSU required for it to work with enforcing security enhanced Linux I guess, so flash SuperSU 2.62 first.

Enjoy :)
[ONE Original Android Development] hachel:
I have that problem. Disabled "vibrate on touch" within sound-settings, still vibrating.
[ONE Original Android Development] dasti555:
You are right I didn't test it with headphones... Do you have backup of musicfx? And can I remove that Dolby eq?

I flashed that zip you posted link to.. But still no sounds since I don't have musicfx :(
[ONE Original Android Development] govigov:
Yes. Somebody mentioned about 'mobile radio active' battery drain. You are not alone, I too am suffering from battery woes due to this. I was hoping that 6.0.1 would have fixed it. Sadly not. This combined with slow charging is making my phone tethered whenever possible. Sultanxda, please can you look into this when you get a chance?

In other news now on tap works - almost always.
[ONE Original Android Development] georgek_gr:
Thanks a lot EdenGottlieb, the ambient display was on indeed (I could swear I had turned it off!). Let's see if it was the culprit :)

EDIT: Yup, that's what it was...good call EdenGottlieb, thanks again!
[ONE Original Android Development] HydroX7:
Edit: my bad this was meant for 5.1.1 version...
[ONE Original Android Development] Phate00:
Does convoler is enabled and preset IRS working?
[ONE Original Android Development] DerRomtester:
Nice debugging work sultanxda to fix the charging issue. I wish i had so great skills. :)
[ONE Original Android Development] fc528e:
I cannot receive SMS. I've tried 4 different texting apps (including the stock one) and tried changing an settings to no avail. Anybody have thoughts? AT&T is my provider. Thanks!
[ONE Original Android Development] Andy1911:
[MENTION=4800121]Sultanxda[/MENTION] .. Wanted to request a feature that is the ambient display setting where device screen does not turn on until we double tap. Whenever it may be. Screen turns on when we tap during ambient display. The problem now in the current build annoys at times. So please add that feature or please make a patch for it. Thanks in advance

Regards

Andy
[ONE Original Android Development] Borsutkar:
[MENTION=4800121]Sultanxda[/MENTION] Thanks a lot for considering our request and debugging slow charging..

Expecting a new build with slow charging fix
[ONE Original Android Development] Mike_1996:
I really don't know what happened to me but with stock cable and charger I managed to get round 2000mA charging current (on flight mode) and I'm totally satisfied with that...
[ONE Original Android Development] ashaik:
Is there any way to set the default USB connection to file transfer? I tried looking through the settings and couldn't find it.

It's not a big deal, but its slightly annoying to have to unlock your phone to enable it when you're doing a lot of flashing work and copying many files over while moving around.
[ONE Original Android Development] Suarezian:
Can someone please upload the latest version on google drive? I'm unable to download from both the links :(
[ONE Original Android Development] Al-Azraq:
I think that I am unable to receive SMS. I was trying to activate Waze and I had to use the call option as the messages were not arriving.

Enviat des del meu A0001 usant Tapatalk
[ONE Original Android Development] britdude:
try deleting APN and reimputting it, i'm on cricket and it had to be deleted then reinput
[ONE Original Android Development] Al-Azraq:
Will give a try, thanks!

Enviat des del meu A0001 usant Tapatalk
[ONE Original Android Development] Pepsy89:
Is the charging speed fixed on last build ? becouse on official cm 13 nightly i get from 10 % to 100 % in like 1h and 40 min , and when i was using sultan version in 4 h :)
[ONE Original Android Development] Medvosteri:
If you are using Greenify, it could be the auto-hibernation. For me it happens while charging, when I disable the auto-hibernation it stops happening.
[ONE Original Android Development] raul.lopez1958:
nandroid backup

With a file browser with root access to see:

/data/data/com.android.providers.telephony/databases/

In that folder deletes files:

mmssms.db

mmssms.db-journal

After the phone restarts and you can send and receive SMS
[ONE Original Android Development] :
I don't have MusicFX and AudioFX on my current setup, a V4A zip I used (I believe LolliViper) deleted everything. But V4A from the link I posted still works on my phone. What you can do is perhaps dirty flash the nightly you're using, and then try the V4A from the thread I posted. You don't have to use Dolby EQ - there's different versions of the flashable zip in the OP of the thread linked, use the one without Dolby. I'm using the one with Dolby, and haven't deleted it because I'm using the OP's default Audiophile settings.

Edit: ... which sucks, so even though I've got Dolby installed, I've turned it off. The next time I upgrade this ROM, I'll use the default V4A zip in the OP I linked earlier.

---------- Post added at 03:51 AM ---------- Previous post was at 03:47 AM ----------

Yes, convolver enabled, preset IRS working.
[ONE Original Android Development] novren:
So in order to install v4a, what exactly should I flash? I understand I'd need busybox, selinux permissive, and what else?
[ONE Original Android Development] dasti555:
Don't know how but it's working :D

I have my own presets in v4a but don't know if remove Dolby also after update will I have it there?
[ONE Original Android Development] :
Again, your mileage may vary, but from what I understand - that is, how I feel I have to go about it next time:

1. Ensure your ROM is clean - no V4A pre-installed, no MusicFX tweaks, or AudioFX tweaks, or anything. Like you just flashed the ROM.

2. Install busybox, using busybox installer. You do not need to set selinux to permissive.

3. Go here and download one of the flashable zips provided. Transfer to your phone.

4. Reboot to recovery, flash the zip.

Done.

---------- Post added at 04:15 AM ---------- Previous post was at 04:13 AM ----------

I'm not sure how V4A will react when you remove Dolby. It looks, from a cursory glance, like V4A and Dolby are both interconnected somehow, hence the singular zip to install them. I could also be way wrong and not know what the hell I'm talking about.

But, with regards to your profiles, they should stay intact. Profiles are stored in the ViPER4Android folder in your Internal Storage.
[ONE Original Android Development] tsmith1223:
So far it's mostly stable, only been running about 24 hours. Just some things I came across and if they've been mentioned I apologize:

1. System Battery Stats causes settings FC

2. LCD Density results in settings FC

3. White glow or halo around phone screen (Don't know if this helps but Oxygen OS did the same thing until the 2nd or third build)

That's all I remember off the top of my head, everything I use for daily use seems to be running great!

Keep up the awesome work!
[ONE Original Android Development] threetwentyfizzle:
Hey Sultan, haven't seen any posts related to a bug I'm experiencing, but on the latest build (12/11) whenever I leave the vicinity of my WiFi networks, my mobile data is not working.

I have signal but have the "!" Next to my signal bar. I have to toggle airplane mode to reconnect to LTE mobile data.

I've double checked my APN settings for T-Mobile and all is correct on that end so I'm assuming this might be a CM bug but just thought I'd report. This has been a consistent reproducible scenario I've observed the last couple days, in different locations (work and home) so I know its not a signal drop related to reception.

Let me know if I can provide anything else that can potentially help.
[ONE Original Android Development] ddulic:
Same prob :( also had this in 5.1
[ONE Original Android Development] highdiver_2000:
Try this.

Settings, Developer options, Networking section, Aggressive Wi-Fi to Cellular handover < check this.

I needed that in Lollipop, strangely not in MM
[ONE Original Android Development] In3rDm0RetHeNu:
Well I have been having data issues for the longest time. (T-Mobile California) and I did nothing that seemed to help it a bit. I opened up dialer and punched in *#*#4636#*#*, then went to phone information set preferred network type to "LTE/GSM auto (PRL)" and clicked on the settings button on the top right, select radio band then the US option. While connection is much better than before, it's still not that great and right now I'm just not sure if it's hardware or software.

EDIT: I've also tried different modems with no real differences in results. I was running TWRP 2.8.6.0, but recently decided run TWRP 2.8.6.0.6 materialized and then re-flashed the oxygen os 241 modem.
[ONE Original Android Development] miesfu:
we have same setting(12/11 ROM, stock kernel, same cable and charger), I never faced such a low current. I checked almost every version ROM, always get >1700ma current.

I can't tell where, but there must be something wrong in your phone (SW or HW related).
[ONE Original Android Development] lordsinasina:
I am experiencing random System UI crashes on latest build. It usually happens when I start typing on the search Bar. Any one else having this issue ?
[ONE Original Android Development] Khizar:
No issues here. Guess time to clean flash.
[ONE Original Android Development] Prinz`:
Battery Saver !

The 11/12 build runs perfectly fine for me, except for some specific settings fc, but thats alright. Do have one question though. There's no option to turn on the "Battery Saver" manually :eek: Dunno if its a rom or CM issue. Is there any work around for this, such as any third party appor something ?:confused: - Btw ! Awesome work with this rom, kudos Sultan !(Yu da man !:cool:)
[ONE Original Android Development] Mr hOaX:
There is NO way to turn on battery saver manually on this build as of now. You can just set battery saver to turn auto-on @ 15% or 5%

May be in future, CM integrates this feature.
[ONE Original Android Development] sambya:
love the return of In call vibration feeedback feature. (Vibrate on andwar was really important for me) cheers [MENTION=4800121]Sultanxda[/MENTION]
[ONE Original Android Development] Nitrogen:
my OPO always in active state after listening podcasts via headphones.

doesn't matter which podcast player i'm using. podcast addict or beyond podcast.

until reboot.
[ONE Original Android Development] Raj joshi:
That green color thing? Is it normal or a glitch? I also see this in toast notification.
[ONE Original Android Development] atulclassic:
Status bar is coming down very slowly..any solution available?
[ONE Original Android Development] Lupin The Third:
What launcher are you using?
[ONE Original Android Development] dasti555:
Working fine even without Dolby but now I think with Dolby I had better sound :D

Is any way how I can know which driver I have installed? If high or super? Because super seems take too much battery.. Or?
[ONE Original Android Development] lynxboy:
I had this on a previous build and clearing the cache solved it for me.

Hope this helps.

Thanks
[ONE Original Android Development] dadounet91:
Unfortunately I have the exact same issue... On the 28112015 release, it fixed itself after about 5 days, no idea why. Hopefully it does too with this update :confused:
[ONE Original Android Development] Aniket.t20:
Ur going to need amplify pro for this and ofcourse xposed installed. U need to block the audiomix wakelock and only deactivate the block when u r listening to audios. If u dont deactivate the block when listening to music itll stutter or not play once screen goes off.

Audiomix wakelock has been sucking the battery dry a lot atm!
[ONE Original Android Development] dadounet91:
I don't get it ? Where did he say he found a fix ???
[ONE Original Android Development] Borsutkar:
I think he is referring to 5.1.1 13th build change log...
[ONE Original Android Development] Nitrogen:
audiomix is affected for speakers and headphones but problem with headphones only.

Blocking audiomix is bad idea
[ONE Original Android Development] P1f:
Probably on the 5.1.1 thread, I saw there a fresh build with the slow charging fixed.

I do not have this issue on 6.0.1 so is not a problem for me.
[ONE Original Android Development] atulclassic:
Nova prime
[ONE Original Android Development] cristianvaz81993:
you need to give nova super su , it aply a fix to this bug, when i go down the status bar and go slow nova give me a message in screen and supersu toast
[ONE Original Android Development] Lupin The Third:
I suspected that. You need to give nova root access. That was stated by the developer of nova and it's a known issue, but not ROM related.