yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] nicholaschum:
Thanks for the info! Really appreciate it.

Keep up the great work :good: :highfive:
[ONE Original Android Development] easy_mac:
Sometimes contacts are not showing up in notifications for me as well, happens about 20% of the time. I use signal as my texting app so I'm not sure if it's at the os layer or the application later though.

Also just wanted to say thanks again [MENTION=4800121]Sultanxda[/MENTION] finally made my way over to donate
[ONE Original Android Development] djuliusl:
There are some regressions, maybe? It happened to me as well. Can you recommend some good modems? Btw, did you include modem in your ROM?
[ONE Original Android Development] atakanyildiz:
People make mistakes. I Fixed it flashing with 2.8.6.
[ONE Original Android Development] Phoenix Wright:
http://pastebin.com/wYp3yRp8

There it is. I debugged dwc3_otg to learn how it worked; I basically partially rewrote it. I'm a coding newbie, so forgive me if you see anything wrong :D

I've tested this a lot and it covers all the wrong usage cases I could think of (like changing the parameter before removing OTG, or inserting regular OTG with parameter set to aca mode, and things like that).
[ONE Original Android Development] Sultanxda:
Will look at it after I wake up.

How can something regress if it did not change? Modem firmware is not included in the ROM. I don't know which modem will work the best for you; only you can determine which modem works best for you.

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] zBear:
right now I am testing your previously suggested kernel

you recommend to stop that test and use this new kernel?

can I flash today's kernel over the previous one?
[ONE Original Android Development] Sultanxda:
The previous kernel was already confirmed to not fix the problem (by quite a few users), so yes, flash today's kernel over the previous one and report back.
[ONE Original Android Development] Sultanxda:
Here's a new version with some bugs fixed: View attachment Sultan-kernel-CM12.1-New-Fuelgauge-2.0_2016-01-13.zip

Anyone else who wants to try my new battery driver should flash this kernel 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] tonyboy3:
Thanks a lot! I will try it!
[ONE Original Android Development] ikjadoon:
Oh, great, nice. OK, you guys can safely ignore the PM I just sent. My apologies; I didn't see this reply. Good luck--I'll be able to test it out in a few days using a Y-cable.
[ONE Original Android Development] zBear:
ok, thank you

I will report back in several charge/discharge cycles
[ONE Original Android Development] Mullermilch:
The Snapdragon Camera crashes everytime i try to start it. Does anybody expierences this issue too? I have installed another Camera app and with that i don´t experience any problem. Would be nice if there is a solution for that because the Snapdragon Camera app is very nice (:
[ONE Original Android Development] xzjn9p:
Ok. I know there is some "coexistence" issues between wifi 2.4ghz and bluetooth but I was running the latest rom (1/7) and was having drastic slow downs when bluetooth (smart watch, mostly) and wifi were operating. Like 1/10 of normal performance. Turning off bluetooth instantly fixes this.

Sultan remarked on this issue several times (e.g.HERE). Where wifi may be somewhat affected, maybe a 1/2 reduction. So I tried A LOT of roms and kernels yesterday trying to diagnose this. I found that the latest sultan cm12.1 and cm13 roms and the latest cm13 nightly have this behavior on my phone. If I go back to the sultan cm12.1 roms from November I get much better wifi performance. I tested 11/1, 11/16, 12/1 and 12/13. These all seemed to work but my methodology may have been slightly flawed. I would need further testing to make sure. Anyone else see this?
[ONE Original Android Development] nsmart:
I am using onscreen navigation buttons. Snapdragon camera always runs in fullscreen mode, so I have to swipe up to make onscreen buttons visible. Is there any trick to keep snapdragon camera from running fullscreen?
[ONE Original Android Development] broke86:
Hi, is anybody having this issue? Those eventX wakelocks are driving me crazy!

I've already did some research about them, somebody believes that they are related to Wifi but in my case they are always there even using just mobile data. I'm pretty sure that is something related to the touch screen. Any idea?
[ONE Original Android Development] qug:
I appreciate the insight. I tried flashing your 1-7 rom again (this time with twrp 2.8.6) and now I am no longer seeing any strange drops in cellular data.
[ONE Original Android Development] fradbari:
Hi, it's possible to install other kernel, like boeffa, AK or franco?

Thanks

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] Khizar:
You can use CAF kernels but not CM ones. Just make sure they're for LP and not MM.
[ONE Original Android Development] hansg01:
How do you guys change the DPI to something custom value like 420? Le DPI Changer and textdroider are not working in my case.
[ONE Original Android Development] Vriesdejoop:
1. Open Root Explorer.

2. Go to /system

3. Click on Mount RW (It should appear as Mount RO, that’s when it is correct!)

4. Look for build.prop. Long press on the file and press Open file in Editor

5. Add the line: ro.sf.lcd_density=420

6. Click on the Menu button, and Save and Exit.

7. Reboot.

After this you can change the DPI with e.g Le DPI Changer and textdroider, problem is that the line (ro.sf.lcd_density=420) is missing in build.prop!
[ONE Original Android Development] pSyLiquid:
Try Build Prop Editor or by hands. Use root explorer or other one go to the /system/build.prop and make the change in ro.sf.lcd_density=480 to 420 save it reboot. profit. Need root.
[ONE Original Android Development] Khizar:
I manually edit build.prop.

However in your case I may know why dpi won't change, have you ever used the CM built-in dpi changer? If you did, it forces you to use it even if you use another app or even if you manually edit build.prop. So try changing dpi using the built-in dpi changer.
[ONE Original Android Development] hansg01:
Looks like this is the reason, why I am able to change dpi using the build-in dpi changer but not using any other app, or even manually.

Any workarounds for using custom dpi in this case?
[ONE Original Android Development] Khizar:
Yeah set the custom dpi using any of the apps, all you'll have to do is reset it using the CM dpi changer. So change dpi(eg. Using texdroider), reboot, change dpi(using CM dpi changer), reboot.

It's really annoying so I recommend clean flashing and then not using CM dpi changer again. No other way to get it to stop forcing you to use it AFAIK.
[ONE Original Android Development] xzjn9p:
I further tested and confirmed that the 12/1 version works great w/ 2.4ghz wifi and bluetooth but the later (e.g. 12/20 1/7) do not. The changelog notes some wifi changes which I assume has some effect.
[ONE Original Android Development] zBear:
2 All

how often do you restart your phone on this ROM?

I do it after every full charge, but maybe it's not necessary to do this daily?

I'd like to hear your answer and an opinion why you do it exactly like you do it :)

thanks
[ONE Original Android Development] easy_mac:
I end up restarting it every few days, usually because of an xposed module update or if my phone is really acting up. No need to restart after charging.
[ONE Original Android Development] elwood_:
I have the 2 latest updates available (01/05 & 01/07) can i install 01/07 and skip 01/05 or do i need to install them both?
[ONE Original Android Development] mr.shme:
Just install the latest one. They are full releases every time. Not incremental.
[ONE Original Android Development] easy_mac:
This was just asked on here a day or two ago, no need to flash each update you can just flash the latest one
[ONE Original Android Development] bucketheadmjs:
Once a week maybe. Usually the phone freezes and I am forced to. [emoji12]
[ONE Original Android Development] slamdunksaliby:
With the new battery driver, my opo charged with no cable ? lol thanks Sultan!
[ONE Original Android Development] Medvosteri:
You sure you posted this in the right thread? 5.1.1 didn't get a new driver?

Edit: Apparently I missed something. Ignore
[ONE Original Android Development] pSyLiquid:
I think yes coz he mean this http://xdaforums.com/showpost.php?p=64792183&postcount=8407
[ONE Original Android Development] slamdunksaliby:
Yeah he made a new kernel as opposed to making an entire new update like he did for 6.0.1
[ONE Original Android Development] Renosh:
I've seen this same behavior on stock COS12.1 so its not that strange.
[ONE Original Android Development] Cesaragus:
I posted this on the CyanogenMod 13 thread, but I wanted to post it here too [MENTION=4800121]Sultanxda[/MENTION]

I was wondering if you can use Color OS camera libraries instead of Oxygen OS libraries in your ROM. There are some Color OS ports and they have manual focus and slow shutter for more than 2 secs.

Is it possible? I was wondering if you can put that in your ROM, it is the best one I've ever tried in my OPO. Favorite ROM ever.
[ONE Original Android Development] Sultanxda:
Sure, let me just burn 2+ months of work on the camera HAL and switch to Color OS camera libraries. /s

I've tested the Color OS camera libraries before, and they suffer from the same crippling bugs as CM's camera libraries.
[ONE Original Android Development] Cesaragus:
I didn't demand you to do it, I just wanted to know if it was possible. Sorry for asking.
[ONE Original Android Development] tankhood:
I was on cm13 gotta say I find this built much better.
[ONE Original Android Development] mr.shme:
I switched from 13 to 12.1 because of the better battery life and stability a few weeks ago. It is much better. CM13 is just not mature enough yet.
[ONE Original Android Development] Plohish:
Good afternoon!

I did not answer for a long time, as the situation with the energy consumption of my smartphone suddenly became normal. However, today all over again, I cite a screen shot:
[ONE Original Android Development] gwindlord:
Is this new kernel Github open-source already?.. For the case if I'd like to include it into my build process.
[ONE Original Android Development] Biiz:
guys why cant i install BearTunnel (vpn) in this rom?
[ONE Original Android Development] tankhood:
Daily driver all the way.
[ONE Original Android Development] gronostaj:
In Snapdragon Camera when I have manual shutter speed set, flash doesn't work even when it's enabled. Can anybody confirm this?
[ONE Original Android Development] zBear:
I use this app

no problems detected
[ONE Original Android Development] Biiz:
See photo....
[ONE Original Android Development] bucketheadmjs:
I've tested TunnelBear and PIA and both are working.
[ONE Original Android Development] Biiz:
i had the same problem in sultan's 6.0.1 and now in every sultan's 5.1.1 build :/

of course i did clean flash
[ONE Original Android Development] kimikim0:
hey guys , just wanna ask, what the best firmware for lolilpop ? 241 ? c7.011 ? tq
[ONE Original Android Development] Sultanxda:
I looked into the NextAlarmTracker wakelock, and it is a temporary wakelock that only holds itself for 6 seconds every time it is used (so that it doesn't remain forever and kill your battery). This means something is constantly using this wakelock... and I have no idea why.

It's been on GitHub for 3 days.
[ONE Original Android Development] 69gm:
This is more a function of where you live and your carrier. There is no "best firmware".
[ONE Original Android Development] kimikim0:
okay how about the most stable firmware for lolilpop ?
[ONE Original Android Development] 69gm:
I would suggest you try it. Start with the stock. H2 firmware has also been good for some...but stability isn't much of a factor for firmware.
[ONE Original Android Development] gwindlord:
Got it, thank you, just saw that cm-12.1-caf branch of android_kernel_oneplus_msm8974 was not updated a bit longer, so I wonder where is it located then - is it even android_kernel_oneplus_bacon-3.10 ?..
[ONE Original Android Development] Sultanxda:
I haven't touched 3.10 in over 6 months...

It's under the cm-13.0-caf branch: https://github.com/sultanxda/android_kernel_oneplus_msm8974/commits/cm-13.0-caf
[ONE Original Android Development] gwindlord:
Thank you and sorry for stupid questions, I just could not imagine kernel from cm-13.0-caf branch would suit for 12.1 as the Fuelgauge one >_<
[ONE Original Android Development] fradbari:
The mobile active radio fix works of bazoocaze is integrated in this Rom?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] Nickamina:
It's not a fix.

http://review.cyanogenmod.org/#/c/107828/
[ONE Original Android Development] neojacks2:
Any solution to the quick battery drain from 10% to 0%? it just takes 30 seconds to deplete to 0 :(
[ONE Original Android Development] wikid24:
can't get usb connection working

Help!!

in the Storage > "USB Computer connection" section, I accidentally unchecked MTP (so that nothing is checked), and the device switched to USB is not disconnected and kicked me out of that screen.

Now, whenever I try to re-enable it, I try to go to Storage > "USB Computer connection" press the 3 dots and it won't let me!

I tried the following:

- enabling/disabling the developer options,

- unchecking and rechecking "enable USB debugging", and revoking current architecting

- reinstalling the the same image

- connecting a OTG cable

- connecting to my laptop

- various reboots, removing the cache

I still can't get back to the "USB computer connection" screen, and am 90% sure it is a defect.

Can someone please try it out and validate the bug please? I can't even backup my phone and factory refresh without this at the moment!

Thank you!
[ONE Original Android Development] fradbari:
[emoji54] [emoji54] [emoji54] this post was made by bazoocaze.... And why he create a xposed module? [emoji29]

I am a little bit confused; so download the fix mobile module is pointless?!

Inviato dal mio A0001
[ONE Original Android Development] lifelesslegend:
Its just a module that hides the mobile radio active timer on the battery stats section.
[ONE Original Android Development] pSyLiquid:
Unfortunally factory reset will help u only
[ONE Original Android Development] zBear:
try this kernel http://xdaforums.com/showpost.php?p=64792183&postcount=8407

and/or

use your phone until the it switches itself off in the evening, plug your phone in charger, don't turn it on and don't disconnect it till the morning

did your problem appeared after the rom update or you made a clean install?
[ONE Original Android Development] paiktaras:
In having someone use it, worth the effort against the base ?
[ONE Original Android Development] Valaran:
Hi ! Nice rom ! no issue so far ! Daily driver as mentionned before !

i'm waiting for bluetooth stabilisation to jump into your cm13 build ! Good job [MENTION=4800121]Sultanxda[/MENTION] !
[ONE Original Android Development] :
Stuck on CM logo after clean flash. (tried clean flash 2-3 times already)

I was able to flash this ROM in the past. In fact i was using this ROM 2 days back. But then i decided to try out COS 12.1.1 and flashed it using fastboot. Now when i tried flashing back this ROM, it just gets stuck on CM logo.

I tried flashing CM nightly to test and it boots.
[ONE Original Android Development] zBear:
I don't see any difference, but it doesn't do any harm either

worth trying if nothing helps
[ONE Original Android Development] mr.shme:
Can anyone confirm this bug for me. If you open the dialer, go to recent calls, and tap on the round icon that brings up contact details, it crashes the dialer?

It only does it for me with numbers that are not in my contacts list.
[ONE Original Android Development] Odysseus1962:
I've never seen this issue, and I've been using this ROM off and on for many months. But then again, I use open gapps "stock" then limit what gapps are installed via the gapps-config file. In my setup the stock Cyanogenmod contacts app is replaced by the Google version. Perhaps the bug you're experiencing is in CM's implementation of the contact app? If so, that would make the problem probably out of Sultanxda's control.

I have several suggestions, 1st try wiping your caches to see if this resolves your problem. If not, back everything up then trying a minima clean install and see if the problem is persistent. If that fails, try a clean install of the last CM snapshot. If the issue is still evident, then it's obviously in the CM code. The only alternative would be to replacing the CM contact app with another. The easiest method being using open gapps to replace the included contact app with the Google version.

I hope this helps.
[ONE Original Android Development] mr.shme:
Ya it's no big deal. It's probably cause I haven't done a clean install for a couple of builds. I was just wondering if someone with a clean install could reproduce it.
[ONE Original Android Development] Madridista7:
This also happened to me. I flashed the the COS 3JL build (the one prior to the Cortana integration), later this ROM and it worked.
[ONE Original Android Development] kenboyles72:
just did a test, everything ok on my end
[ONE Original Android Development] rahulbhasme:
I can't load my owner photo from google plus app on status bar (Owner Pic In Circle).

When I select keep contacts up to date in google plus settings, first it checks the box and when i go back and again open it the box remains unchecked. its really annoying me.Does any one have solution for it. my app is updated to latest google plus.

Also when in call,while talking the other person cant hear my voice and when i turn on the speakerphone he can hear my voice,whats happening?
[ONE Original Android Development] Murphy7523:
CVE-2016-0728 hello Is this ROM or any your other work vulnerable to the Linux bug?

Reference: http://arstechnica.com/security/201...f-millions-of-pcs-servers-and-android-phones/

Thx.
[ONE Original Android Development] gfinockio:
Just tried it - and indeed I confirm. Works fine with numbers that called me or numbers that are in my contacts, but if I click on a number I called that isn't in my contacts, "Contacts" crashes.
[ONE Original Android Development] ikjadoon:
I can't reproduce it in on my end. Tried both a contact and a random number.

This is using the built-in phone app, right?

Hmm, but if both of you have it, record the crash with logcat and post the output. Logcat will narrow it down quickly. Last time I posted a logcat, Sultan was able to fix it within two days. :D
[ONE Original Android Development] mr.shme:
Here is a log cat of the crash. You can see it on the line that says "TD BANK FNC"

http://pastebin.com/fRUk6tAJ
[ONE Original Android Development] ikjadoon:
It says it uses Linux kernel 3.8 and later. My phone says it's using kernel 3.4.0....so, we're OK?

Edit: OK, apparently, the keyrings function (that this exploit uses) was backported to 3.4, lol. So, ostensibly, yes. Cyanogen, though, will push the patch soon and we'll get it. We'll probably be some of the first Android users to get it...

In the meantime, SELinux should help to prevent this, they said.
[ONE Original Android Development] easy_mac:
Same here, have had this issue for several months but I've just used workarounds
[ONE Original Android Development] rcloke91:
Had zero issues with this rom for months, and then, weirdly, upon trying to change my wallpaper tonight via Google Now Launcher, the OPO was sent into a boot loop. Turning it off and on via hardware buttons have gotten it back up and running, and, figuring it to just be a weird, singular thing, I tried it again. Nope, another boot loop. But, after the bootloops, shutting down and turning back on this time, the wallpaper changed lol.

Has anyone had this happen to them?
[ONE Original Android Development] gwindlord:
Could you please point on commit in gerrit or something else to track changes in that direction?..
[ONE Original Android Development] ikjadoon:
Mate, I know just as much as you, :( I've got no real idea what's going on. Here's the gerrit for bacon, so that's where you'll see any updates:

http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_oneplus_bacon

But nothing about this CVE, yet. Here, some Cyanogen developers mention that they've patched a couple of device kernels already.
[ONE Original Android Development] gwindlord:
This link

http://review.cyanogenmod.org/#/q/message:join_session_keyring

may be even more relevant.

Also according to the existing fixes (like this) kernel for our device just does not have the "else if" branch to patch. Not sure what does it mean.
[ONE Original Android Development] Emrets61:
Hello. I want to take some long exposure photos. (8 sec, 16 sec, 32 sec) I flashed HAL but it bricked my phone. I think it's not working with the new libs. How can I change the camera libs to the original CM libs?
[ONE Original Android Development] rcloke91:
Welp, I was fortunate to wake up before my alarm this morning and found my phone in a bootloop. Really not sure what the deal is. I don't change any kernel settings or any weird stuff. At first I was wondering if using Twilight, which I hadn't been doing until recently, might have caused it as I know using it and f.lux on previous phones could make things weird, but even after uninstalling it last night this issue persists.

Guess I need to wipe everything. Before I do that, one last call for any suggestions. I don't mind doing the wipe, but I don't want to run into this issue again. I can give whatever info would be deemed helpful.
[ONE Original Android Development] JadeSoturi:
Hi guys....

This is probably a little oftopic, but since I'm on the latest nightly of this ROM, I'm gonna ask anyway - hope it's OK.

I've been having issues with the main mic for well over a year now. Tried all sorts of fixes like mixer_paths and audio_platform_info xml files and build.prop fluency stuff. Nothing really helps - just end up with more noise / static along with increasing the volume of my voice on the other end. Even got a replacement daughter board with a new mic - didn't help, actually got worse with more echo. SO, I want to to a full nandroid backup today and revert my phone to stock CM11S to see if it helps(problems started when I went from CM11S to CM12). BUT, can I just restore an old version of android using NANDROID backup? And then return to the current installation the same way? Or is there something else I must flash first? I've read a few places that I need to install corresponding firmware/modem, but others say it's no problem to just flash the nandroid as it should contain everything, including modem, efs etc...

What would be the safes way to do this? The thing is - if it doesn't help reverting to CM11S - I want to get back to my current install with as little hassle as possible, including the restore of messages, pictures etc - since it takes a ****load of time with the amount of data I have and restoring NANDROID seems like the easiest way to go :)

Thanks in advance:)

//jadesoturi
[ONE Original Android Development] Odysseus1962:
[MENTION=2680259]JadeSoturi[/MENTION] have you tried disabling "OK Google" detection from any screen? Go to the Google settings applet and dig down to Search & Now/Voice/"OK Google" detection, and turn off the 'From any screen' button. I bet this will help.

There is a known bug with the OPO and Google Now that interferes with the noise cancelling mikes that causes a range of audibility issues in phone call clarity
[ONE Original Android Development] JadeSoturi:
[MENTION=5463522]Odysseus1962[/MENTION] - yeah, tried that - no luck :/ The best I've got is 95 on DEC4 in mixerpaths, but that only helps on calling(with a massive noise/environmental feedback) - sound recording is still a no go :/