yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] kenboyles72:
Actually neither of these. With android M, there is a difference in how SU works, so you will need to flash the systemless beta version. You can find it here: http://xdaforums.com/showpost.php?p=64161125&postcount=3
[ONE Original Android Development] Sultanxda:
I'm not really sure what happened there. Bluetooth completely goes up in flames, but it doesn't give a definite reason as to why. I searched for the errors, and all I found was some Google issue on the Galaxy Nexus from 2013 :/

I haven't seen this reported before with my ROM. When in despair, clean flash?

EDIT: Are you using a 3rd-party app for Bluetooth?

Knock yourself out: View attachment Sultan-kernel-CM-fuelgauge_2016-01-08.zip

I saw more people reporting this issue on official CM recently. CM's battery driver is still very similar to what's in my kernel (both of them were done by Oppo), and the routines that actually estimate battery percentage are almost exactly the same.
[ONE Original Android Development] bounti:
Well he was referring to the Lollipop version.
[ONE Original Android Development] 69gm:
Very curious. I use bluetooth daily in my car and have not had any issues. I also just got back from a trip on which I also brought my portable bluetooth speakerphone to be able to make/receive calls hands-free. I had zero issues...so even on my vacation, I connected, and used bluetooth, without issues. It could be app related? Not sure...
[ONE Original Android Development] ikjadoon:
Settings -> About Phone -> Baseband version, I thought...

But, somehow, I think there's some weird naming going on. Another thread says you can't tell what modem you have, you just have to remember it. :confused:
[ONE Original Android Development] mr.shme:
Here is a collection of modems for the opo.

https://www.androidfilehost.com/?w=files&flid=40582

I am currently running c7-00011 as when I was using the latest C1.11 I was getting static when calling people
[ONE Original Android Development] undrwater:
If you mean do I have a 3rd-party app to manage bluetooth, I don't think so. Perhaps one of the apps I have installed is doing something (tablet talk, maybe?). Did you find something in the log that led you to the question? If so, throw me a bone and I'll follow up.
[ONE Original Android Development] gfinockio:
Ever since the January 5 update I've had bluetooth issues - specifically, I paid my OPO with my bluetooth dongle in my car, and while it says it's connected and the button controls playback and opening apps, there is no audio passed through the bluetooth to the car. The apps play. Same goes with phone calls, although if I receive a call the audio (sometimes) work.

Any thoughts? It worked perfectly fine previous to these past couple of updates...
[ONE Original Android Development] vl319:
Which build is the most stable best battery life? And least bugs
[ONE Original Android Development] Sultanxda:
I saw a post on stackoverflow with your errors, and the guy who posted it said that his app caused it (his app uses Bluetooth). Your log doesn't give the underlying reason as to why Bluetooth is crashing, so I really don't know how to approach this.

The way that the stable (YOG7D) branch works is that CM does not touch the ROM *at all* except for approved critical fixes and security patches from Google. I checked, and didn't see any changes to the Bluetooth stack since the last build (Dec. 20).

Bluetooth hasn't been touched on my end either, and it's working fine for [MENTION=4151403]69gm[/MENTION] (he uses Bluetooth every day).

The newest build...
[ONE Original Android Development] gfinockio:
Odd - absolutely nothing else has changed on my end (new apps, devices, etc. ) between January 4th (when it worked) and today (after 2 updates). Maybe a fresh install will help the situation.
[ONE Original Android Development] pSyLiquid:
[MENTION=237269]sultan[/MENTION], man, the question about the Skype is actual... Still black square((( is it possible to fix and made the patch only?

http://xdaforums.com/showpost.php?p=64435119&postcount=8173
[ONE Original Android Development] Sultanxda:
Skype does that when it thinks your network connection is too slow to carry live video. I tested Skype on the Dec. 20th build, and video calling worked fine.

Right now I'm on CM13, but my CM13 builds use the same camera HAL. I tried video calling in Skype over EDGE, and the video did not work (black screen). Then I switched to LTE, restarted the call, and the video worked.

There is nothing wrong with Skype in my ROM.

EDIT: Now Skype suddenly works over EDGE :/ Thanks, Microsoft.
[ONE Original Android Development] pSyLiquid:
Good assumption, but strange coz all the tests were with LTE and Wi-Fi connection after clean flash and dirty flash, but still the same $hit :( last version of skype from market on the both devices. Will try again clean flash. Thx
[ONE Original Android Development] Sultanxda:
Skype video calling suddenly works over EDGE for me :/

Try clearing data for Skype. I tested Skype several times, and I'm confident it's working fine.
[ONE Original Android Development] jarora24@gmail:
Thanks [MENTION=237269]sultan[/MENTION] for this awesome ROM.

But inam facing issues mentioned below

1) form last five month the call volume is always too high. I have to lower it again and again in during every call. The voice is distorted due to high volume set by itself.

2) from last update of 7jan the install button on install package screen gets inactive. Means I am not able to install apps using stored apk. I have to reboot for installing the apk every time.

3) there is a lag while opening the app from recent screen. Sometimes I have to click it two to three time to open the app from recent options

If any one is facing such issue please report..
[ONE Original Android Development] walent:
Hello, does anyone have problem with music player?

When i open google music, it says track currently unavailable, and when i open music app, it crashes when i play a song.
[ONE Original Android Development] grotesque02:
[MENTION=4800121]Sultanxda[/MENTION] is possible in some next release set max screen brightness if snapdragon camera is in used?

And I made some comparison, pics with this camera is a little dark.
[ONE Original Android Development] zBear:
if I understood you right and you were talking about the in-call volume, than:

1. find the file system/etc/mixer_path.xml

2. change the value from 100 to 95 like on this screenshot (you can change it to 90, if you want to)

3. save and reboot
[ONE Original Android Development] jarora24@gmail:
Thanks [MENTION=1250364]zBear[/MENTION] for the in-call volume fix

But, waiting for fixing of install button getting freeze issue.

At first I was facing this issue while installation. But when [MENTION=1250364]zBear[/MENTION] guided me to fix by rewriting the value, I was asked by superuser to grant the x-plore to access the root, but at that moment my grant button also get freeze like install button. I think this issue is for every option where I need to select right side button that is like insyall, grant etc.

[MENTION=4800121]Sultanxda[/MENTION] & [MENTION=1250364]zBear[/MENTION] to look in to this matter and requesting to provide the fix as soon as possible.
[ONE Original Android Development] Sarabveer:
Hey [MENTION=237269]sultan[/MENTION], I sent a request to Google to get this rom GMS certified. So it can work with Android Pay and stuff.

Is that fine with you?
[ONE Original Android Development] darkobas:
lol
[ONE Original Android Development] ikjadoon:
Anybody using USB audio on this ROM? Like, outputting to a USB DAC? Any issues?
[ONE Original Android Development] Khizar:
1. Custom roms will never pass certification.

2. This rom and all other CM/CM based rom will never have android pay since they're rooted by default. You'll need to wait for CM OS to release, whenever that happens. And even then, you'll need to use system less root, normal root breaks android pay.
[ONE Original Android Development] MrBoard:
Ota update question from 20151220

Hello, I am running 20151220 stable and it is working great. I recently noticed that there are 2 OTA updates available... 105 and 107. This may seem like a n00b question... So I apologize for that, but I don't want to mess anything up, so I gotta ask.

If I want to update, should I just select 107? Or should I do 105 first and then 107?

I am guessing that I could just go straight to 107, but I just want to make sure.

Also, is there anything special I need to do first in order to do an OTA update, such as clear cache or anything like that??? Or do I just select the update and let my device download and install it automatically?

Thanks ahead of time for your assistance.
[ONE Original Android Development] ciarpame:
Always install the more recent, they are full ROMs, not incremental packages.
[ONE Original Android Development] MrBoard:
Thanks for the quick reply.

Do you happen to know if I should clear cache before/after doing the update (dirty flash) ? Or does it handle everything on its own, since it is OTA?
[ONE Original Android Development] chrismalla:
Read the "Installation instructions" in the OP (the very first post in this thread).
[ONE Original Android Development] Sarabveer:
1. Let's see

2. The ROM is Open-Source, so I can remove root anyways.
[ONE Original Android Development] sQt:
1st - problem with audio volume and headphones - random volume changing ( on desktop and when music play )

2nd - when i listen music with headphones

when some1 call 2me and i pull out headphones

i hear everything from other side but other side dont hear me ( microphone off )

full reboot needed

this appeared since last 2-3 updates :(

earlier without problem :)

headphones checked on nexus6 , working without issues
[ONE Original Android Development] atakanyildiz:
after last two updates i have bad connection issue. mobile internet is slow too.
[ONE Original Android Development] nicholaschum:
I was spawned because I heard of someone claiming they could just submit an open source ROM to Google and had it submitted to be a CTS approved ROM.

That is not how life works. The ROM is not Sultan's. He's only a builder for a custom ROM that he's building off source from and applying his own patches. Personal commits vs. a whole repository built by CyanogenMod code review is different. The copyrights on all XML files and Java ensure that CyanogenMod owns the ROM and has final say over submission. Judging by what I see here, I'm rather unsure why this ROM is listed under Original Development, unless Sultan's kernel is the original developed item here.

You cannot just submit a ROM as yours to Google unless you are certain you have full permissions to do so. Not only will this ROM NOT pass certification by Google to run the Google Apps Suite, Cyanogen Inc. has full rights over this ROM presented by commit history, thus, rendering your claims nullified in all cases. If Sultan, or anyone claiming that they will submit this without the consent of CyanogenMod, that is called Kanging, and this sort of behaviour will not be tolerated on these forums, and by Google.
[ONE Original Android Development] Sarabveer:
Thanks, I wans't aware of this.
[ONE Original Android Development] djuliusl:
Me too. Cellular signal sometimes disappears completely. There's no issue in 20/12 version.
[ONE Original Android Development] mr.shme:
What was your baseband in the last few versions? I'm not sure if this rom includes one as I just flash my own every time.
[ONE Original Android Development] Valaran:
Hi there !

i got trouble installing your rom (and the cm13 version too). I reboot to recovery (2.8.7 or 2.8.6 tried both) and then format data/cache/dalvik. i flash the zip but after the "patching image unconditionnaly" i got a updater process endend with signal 6 "unable to mount /system". I flash right after the cm12.1s (3ql) without any issue. Tried to wipe system but same issue.

btw after the flashing abort, when i enter the mount menu of twrp, i can't tick "system" (either with "ro only" ticked or not). After i need to "restore" my backup (cm12.1s with ak kernel) and the system option is tickable again. The zip is readable from solid explorer.

it's may not be related to your rom but it's kind of weird and i've not running this issue testing some cm13 builds last week.

thanks in advance !
[ONE Original Android Development] djuliusl:
Attached. Btw, what are some good modems and where can I get it? Thanks.
[ONE Original Android Development] Sultanxda:
This isn't original development? There's more than just the kernel that's original in this ROM.

Certification by Google does not stipulate that the Apache copyright holders must provide consent; that's not how Apache redistribution works, and that would be impossible to enforce by Google anyway.

Kanging won't be tolerated by Google? Then what is AOSP, exactly? Unless you have official evidence to back up what you are saying (not some random post on XDA), then calm down and stop making things up.

This ROM won't be certified because I'm not an OEM and because it costs $$$.
[ONE Original Android Development] mr.shme:
Here is my post from the opo modem thread. http://xdaforums.com/showthread.php?p=64599786

I have had good luck with the c7-00011 firmware.
[ONE Original Android Development] paiktaras:
i have DI.3.0c6-00230 modem , it's correct το flash newest modem and if, what version?

Ι have last build rom sultan
[ONE Original Android Development] mr.shme:
Flash c7-00011 with twrp 2.8.6
[ONE Original Android Development] josip-k:
Ha.
[ONE Original Android Development] paiktaras:
After flashing the new modem its necessary to make wipe?

Sent from my 1+1
[ONE Original Android Development] mr.shme:
I have never wiped after a firmware flash
[ONE Original Android Development] skyrkt:
Hello! First of all, thank you very much for your ROM and all of the hard work that you've done to tweak and improve base CyanogenMod 12.1. I've been getting some seriously good battery life and performance out of your ROM and I appreciate it very much.

I'm running the latest update and I am running into a issue relating to wallpaper setting. When I set a wallpaper (no matter with what application) it won't show until I restart the device. I've tried in different launchers (Z Launcher, Nova Launcher Prime, Google Now Launcher) etc and the same happens.
[ONE Original Android Development] Deepak Vishnu:
The same here.. And i upgraded via ota. Dirty flash . could that be the reason and im using a theme too.
[ONE Original Android Development] urko95:
Aaaaaaand same here using Nova Launcher!

[MENTION=4800121]Sultanxda[/MENTION] you need a logcat?

Thanks!
[ONE Original Android Development] abhibnl:
It's an issue with the latest cm nightly. So because sultan updated the rom to the latest sources, hence this issue is here as well. People on other threads are reporting it as well.

Sent from OnePlus One
[ONE Original Android Development] LookedPath:
[MENTION=4800121]Sultanxda[/MENTION] Hi, this is the first time for me on one of your works and I have to say that I'm really happy.

You done an amazing work.

The only problem that I have experienced so far is that I'm not able to shoot a photo in the clear image mode with the CameraNextMod available here on XDA-Developers, it just shoots a normal photo. Is it caused by the OxygenOS HAL?

Thanks and keep up the good work.
[ONE Original Android Development] fmc000:
It seems that this commit fixed the bug in today's nightly.
[ONE Original Android Development] darkobas:
[MENTION=4800121]Sultanxda[/MENTION] maybe this broke orientation https://goo.gl/4Ch1jI
[ONE Original Android Development] kaz93:
Is it just me or this rom has a very contrasty and saturated screen color by default?
[ONE Original Android Development] aosp:
You gonna create another thread for omni based sultans?
[ONE Original Android Development] Sultanxda:
Maybe, but my phone is running Omni right now, and my ccache was regenerated for Omni, so I don't really want to test it myself at the moment :/

Probably. I finished the initial work I did porting my changes to Omni a month ago, and I'm really enjoying it. The compass issue, as well as a lot of other minor/less noticeable bugs (and CM's daily fails) are not present with Omni. The feature I was missing the most with Omni was built-in color control, but I added savoca's KCAL patches to the kernel and I'm happy with my display's colors tweaked using savoca's app, so there's nothing holding me back from changing from CM anymore. I'm very very happy with Omni so far.

If I decide to post Omni builds, then my CM builds will be discontinued.
[ONE Original Android Development] abhibnl:
I second that. I would love to see an Omni based rom + pure CAF kernel by Sultan. Omni base is really clean and the only thing it lacks is the Layers/Themes support.
[ONE Original Android Development] Sultanxda:
Technically the official Omni kernel is closer to pure CAF than mine (except for the camera drivers). The difference is that my kernel has tweaks and features that I like (can't live without ULPS), and I follow the absolute newest compatible CAF branch, so my kernel/HALs are more bleeding edge.

Lack of themes support == fewer bug reports! :silly:
[ONE Original Android Development] sneakerspark:
No themes. ??????
[ONE Original Android Development] stryker09:
Post that thread already! :cowboy:
[ONE Original Android Development] abhibnl:
Well still, i believe Omni's ROM is more clean than the CM. So it would be great to see that rom + kernel from your side as well. Also, maybe you can cherrypick layers support since merging themes manager would mean adding hundreds of lines of code and may introduce bugs as well.

Yup! that sucks actually, But i've heard DU is based on Omni with theme manager.

:highfive:
[ONE Original Android Development] joefso:
yeah roll with omni rom dude, fck cm
[ONE Original Android Development] Deepak Vishnu:
Omg just love that idea sultan . bring it on.. I wanna try omni
[ONE Original Android Development] abhibnl:
Make sure you guys try official nightly before vouching for this idea. I tried it and it was too plain/vanilla AOSP with no theme support and shiny features so wasn't a daily driver for me. So i guess it's totally upto Sultan if he has the free time to do it cause i have no doubt about his capabilties and knowledge. All he would require is some extra time and as we all know, that is the only thing that developers don't have in excess.
[ONE Original Android Development] lordsinasina:
What features are exactly missing except the theme ?
[ONE Original Android Development] joefso:
I tried it and ditched omni because of lack of theme engine support, old find7 hall and no oxygen cam libs, but way more stable than cm. I would take that stability over the state cm has been in for a while now. Currently running a exodus 0615 build.

There are alternatives though, such as PA, which is AOSP with cm theme manager, I always liked PA. Or slimsaber ... both are btter than cm. atm.

Thoughts?
[ONE Original Android Development] Locklear308:
Unsure if I am late to the party, but flashing Xposed over the lastest firmware kills the device. Bootloops endlessly. Going to try to dirty flash the rom again as I've got too many apps to have to find again manually lol. (Like 180+)
[ONE Original Android Development] easy_mac:
Yeah this happened to me all last night. This rom has problems booting for me very frequently, especially after a dirty flash. Not sure if it's xposed because even after just dirty flashing the rom and not flashing xposed or anything it still has problems. Not sure how to explain it but it takes me a bunch of reboots to get it to pass the boot animation.

To clarify, for me it gets stuck on boot animation. Once it overheats it reboots and keeps rebooting because it's very hot.
[ONE Original Android Development] modemhead:
Are the "data usage settings" working on the last version? I really want to try Sultan's ROM but I've had experienced issues (force closes) when trying to access those settings, either on the last four official COS12.1 updates, and even in the last CyanogenMod 12.1 stable build.

Thanks in advance!

Ps. The crash always says "index out of bounds"..
[ONE Original Android Development] ciarpame:
You never have to clear cache/dalvik (OTA or not), update scripts take charge of all the needed stuff.
[ONE Original Android Development] atakanyildiz:
i was 13.12 wifi was working good. after flashing 5.1.2016 update new wifi firmware (WCNSS version: CNSS-PR-1-4-1-c5-00086) wifi connection is unstable slow, and reception is weak. is there a way to flash old wifi firmware. i dont know if theres a connection but mobile data was better too.
[ONE Original Android Development] lpranal:
Been having weird connection issues with wifi / cellular as well on the last few builds - i.e., data randomly turning off, trouble toggling wifi off and on, etc. Not really reception issues per se, but getting lots of "no network connection" issues from time to time. Running 11-1 build. I'll try a full wipe if anyone thinks that'll fix it.
[ONE Original Android Development] atakanyildiz:
flashed it with twrp 2.8.7 now my efs gone :(
[ONE Original Android Development] uronfire:
All that reading has made me thirsty , time for a cold one
[ONE Original Android Development] qug:
I was also having issues with the 1-7 build (dirty flashed over the 12-20 build with twrp 2.8.7) where my cellular data connection would randomly drop completely. Back on 12-20 for now.
[ONE Original Android Development] mr.shme:
Dude my message was only 5 words long and you still couldn't follow it. It said to use 2.8.6... Not 2.8.7
[ONE Original Android Development] ikjadoon:
Anybody interested in USB OTG with charging? You can charge your phone while you're using it with a USB flash drive or a USB DAC.

It uses a small kernel mod, written up for the OPO by Sollapse (XDA link; Github here). Phoenix Wright updated it with some patches, too.

[MENTION=237269]sultan[/MENTION]: I think it would be a neat addition to your kernel, Sultan. I think most of the heavy lifting is already done.

I'm just patching it in myself right now, but it would be kind of cool if everyone had it (and, selfishly, I wouldn't have to clone your repo, patch it, build the kernel, and flash it every time there's a new OTA--all of which I learned in the past two days just for this mod, hahaha).
[ONE Original Android Development] Sultanxda:
Google is a big company; they don't care if some random people on XDA kang their stuff.

Most of the things I listed in the OP constitute a "significant 'first' in development for a device". The kernel has 1,000+ lines of original code I wrote, and contains other things that are also a significant "first" for the OPO. The short lists I gave in the OP don't cover nearly all of the OEM's bugs I quietly fixed in the ROM and kernel.

If the OS were a car, then I completely reworked the engine. The car still looks the same on the outside (i.e. CyanogenMod), but it's completely different under the hood.

This is probably the most original ROM for this device, and I spent 1,000+ hours working on it. I think it qualifies as "original" development by XDA's standards, even though it may not appear all shiny and original on the outside at first glance (with the exception of Snapdragon Camera).

The new WiFi firmware is only very slightly different from the old firmware, and it works perfectly for many, many people.

Mobile network components have not been touched for months, so I don't see how mobile data could have been better on the old build.

Wrong thread. This thread is for CM12.1.

Mobile network components have not been touched for months.
[ONE Original Android Development] Sultanxda:
The code for it was very messy, and I heard it wasn't stable, so I avoided it. If you have a cleaned-up version of the patch with Phoenix Wright's changes then I'll gladly look it over again.
[ONE Original Android Development] gaspolo:
[MENTION=4800121]Sultanxda[/MENTION] i found 2 strange issue, when receive SMS, i cannot see name , but see only the number ( only on headsup) because if i go to sms app...i see the name.

second: when in call , somtime the proximity sensor not work, dont wakeup the phone .. and i need to wake up with button.

some suggest?