yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] drakonizer:
As you may already be knowing, a new weekly has been uploaded. As usual, for the full changelog, you can visit our website https://carbonrom.org/changelog but the major changes include:

-> Separate power configs for the 3 and 3T

-> Toggle for capacitive button backlight

-> Quick unlock by entering the right pin/password, without pressing the enter key.

Enjoy!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nice work guys :good:
[OnePlus 3 & 3T Cross Device Development] himsin:
Any comments on this?
[OnePlus 3 & 3T Cross Device Development] sclcn12:
I think everything is ok, swipe from recents does not stop app, and an app that can't run in background can post notifications via GMC (now FCM).

In my case I don't have play services and app that can't run in background can't post notifications, so for what I know appops works.

Take a look to wakelocks
[OnePlus 3 & 3T Cross Device Development] himsin:
If we clear an app from recents (battle bay game in my case), then should it be shown as running in app-info with "force stop" button? Background permission is also turned off in app ops. I begin realizing all this after youtube video (https://www.youtube.com/watch?v=omPD-F8IXiA) posted by official channel of XDA. That's why I wanted to ask here but no one cares for a comment :(
[OnePlus 3 & 3T Cross Device Development] drakonizer:
It's not that we don't care for a comment. Clearing apps from recents doesn't necessarily force close the application, that has always been the behaviour of Android. However your concern with App Ops seems genuine, but I am not the one who pushed it, nor do I use it/know how it works. I have contacted the team members who worked on App Ops and they'll get back to you. They're a little busy at the moment.

Sorry if you felt like you were being ignored.

Meanwhile, you can allot the "kill app" option to long press of the back key to get your job done. That's what I use.
[OnePlus 3 & 3T Cross Device Development] himsin:
Thank you very much for your kind reply. It's always good to hear that all concerns are being heard by devs and they are working on them behind the scenes. I am still using this rom despite my mentioned concern because this rom is simply amazing and you all have done great work on this. You guys are just awesome. :)

P.S. I had totally forgot about long press to kill :silly:. This is a good workaround for my use case. Thanks for this suggestion.
[OnePlus 3 & 3T Cross Device Development] monsterpenguin5:
Hey all,

Just FYI, the slider status bar icon bug I mentioned before is still present in the current build, even on a clean flash. Not a big deal, but still there.

Great ROM otherwise!
[OnePlus 3 & 3T Cross Device Development] drakonizer:
Um, I remember fixing it. It is not present in my end. Can you take a screenshot and show it? Also please show the build you're running.
[OnePlus 3 & 3T Cross Device Development] monsterpenguin5:
The icon being the same for both silent and do not disturb is fixed. It's the not showing the silent mode icon after a reboot part that is still not right. So, my slider is in the top position (total silence) but there is no icon in the status bar for it upon reboot. If I switch the slider manually it does work just fine. It's not keeping it after reboot tho. Here is my version screenshot.
[OnePlus 3 & 3T Cross Device Development] abalam:
Good ROM. Want to run these together with Blu Spark kernel. Does anyone experience this?
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Best pair in town.

Daily driving that setup for long time now.

Check it out, it's wild.:good:
[OnePlus 3 & 3T Cross Device Development] drakonizer:
Whoops, sorry I misunderstood.

We are actually working on a different implementation of the alert slider, but that's a WIP. Since I believe this is a relatively minor bug, I would prefer waiting for that implementation to roll out before trying to fix this, as otherwise it would be twice the work.

Thanks for reporting these minor bugs though. These are the stuff that differentiate a good ROM from a daily-driver ready ROM, and you can definitely expect us to look into it soon, if not immediately.
[OnePlus 3 & 3T Cross Device Development] monsterpenguin5:
Sounds good to me. Thanks for the update.
[OnePlus 3 & 3T Cross Device Development] bkuri:
Just wanted to drop by and say that I've been running CarbonROM as a daily driver for a few days and so far it feels super nice all around. I do miss a few features from other ROMs here and there, but something tells me that at least a few of them will be added eventually.

Keep up the excellent work!

---------- Post added at 11:52 PM ---------- Previous post was at 11:40 PM ----------

I don't know if this is the right place to post feature requests, but it would be really great if you could add an option to trigger an activity (such as a tasker task or some other shortcut) for each step of the alert slider. That way I could use them to switch among auto portrait, auto landscape, or lock device rotation altogether, which in my case is something that I would definitely have more use for. Thanks!
[OnePlus 3 & 3T Cross Device Development] himsin:
I was gonna report that sim status in about section results in phone process fc but later then I noticed that a fix is already up on Gerrit [emoji3]

BTW sim toggle change has been in Gerrit from a couple of weeks, what's holding them up?
[OnePlus 3 & 3T Cross Device Development] rowdy_83:
Does fingerprint work with blu spark kernel.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
All Carbon features are working seamlessly paired with blu_spark kernel. :good:
[OnePlus 3 & 3T Cross Device Development] SREEPRAJAY:
First time installation...with greenify, ExKM and AKT. Was on data yesterday in office, so not on Wi-Fi all the time...made a few long calls, whatsapp...NO GAMES. impressive statistics and SOT. Kernel is dabug's 13.5.

Developers...a grand salute sirs

using Android device, running 7.1.2 custom power
[OnePlus 3 & 3T Cross Device Development] himsin:
That's great, I never had this much SOT on any rom. May be its my set of apps which kill my battery (yup facebook and Instagram). BTW which kernel is that?
[OnePlus 3 & 3T Cross Device Development] SREEPRAJAY:
http://dirtyrom.com/KronicCore/

the developer is inactive these days for one plus 3 as he got himself a one plus 5. I used 13.5 which is really impressive. See my average battery stats is over 6Hrs since March this year

using Android device, running 7.1.2 custom power
[OnePlus 3 & 3T Cross Device Development] marqobazua:
Which AKT did you install? Balanced, performance, battery?.. Great SoT!:o
[OnePlus 3 & 3T Cross Device Development] SREEPRAJAY:
Battery....

if it wasn't that wakelock.... WAKE:COM.GOOGLE.ANDROID.GMS/MEASUREMENT which was around 1 hour in time...it was easy to touch better results
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Hi all.

Found a bug in the clock app.

Opening settings on the app and changing some settings, closing the app and opening it again, settings show as untouched.

I usually change start of the week to Monday and gradually increase alarm volume to 15.

They work as I set them but on settings show up as if I had not set them.

Tested on both OP3 and Nexus 5 on stock kernel.

Edit:

Testing it further and came to the conclusion that gradually increase volume will work untill opening clock settings again, seems it actually resets to default OFF state then. From there on it stops working untill a new interval is set.

Start of the week shows as Sunday on settings but on the alarm tab is still showing up as set previously (Monday) even after reopening settings so it's not reset, it seems.

This was also reproduced on a kenzo.
[OnePlus 3 & 3T Cross Device Development] bkuri:
Double tap to wake suddenly stopped working. I tried both resetting it from the settings panel and using the "OnePlus Control Center" app, but the setting won't stick. Rebooting doesn't work either.
[OnePlus 3 & 3T Cross Device Development] FloGatt:
Does the new CarbonROM build from yesterday support aptx? I spotted a commit on gerrit ;)
[OnePlus 3 & 3T Cross Device Development] drakonizer:
Thank you for your report. I'll forward it to the team.

Uhm, sorry I can't reproduce this issue on my end. If someone else reports it too, I'll flash the weekly and take a look.

It *should*. However I don't have a compatible device to check.
[OnePlus 3 & 3T Cross Device Development] FloGatt:
Thank you for your answer. I will test it with a 3T and a Sony BT headset and report.
[OnePlus 3 & 3T Cross Device Development] FloGatt:
aptX

As you can see in the screenshot attached, aptX is working flawlessly since the latest build :)
[OnePlus 3 & 3T Cross Device Development] RobotPhone:
What firmware is everyone running? I'm getting ready to switch roms to the latest carbon.
[OnePlus 3 & 3T Cross Device Development] romskii:
Wasn't this ROM based completely on LOS? It looks and feels as pure AOSP based one and this is awesome! Like back to my Galaxy S3 days.

I would love to see if you add fling, this navbar add-on :) At the moment I'm using this ROM with the HyperX kernel. Smooth as butter and absolutely no issues. Nice job. Together with DU I think my fav ROMs for the OP3
[OnePlus 3 & 3T Cross Device Development] bkuri:
I was able to reproduce it, actually. There seems to be a conflict with DT2W and switching to battery saver mode. Once I turn that on DT2W stops working. The problem is that it won't turn back on once battery saver mode is off. I need to tap on the setting switch repeatedly and after a while it starts working again.
[OnePlus 3 & 3T Cross Device Development] drakonizer:
I am not sure about the past but right now Carbon is mostly based off CAF, with some AOSP parts.

Sorry, but we have no current plans to add fling or any part of DUI. It's unlikely that this stand will change in the future.

Thank you for your kind words. I'm glad you're enjoying Carbon :D

Thanks for the extra info. I will try to reproduce it once again and get back to you on this.
[OnePlus 3 & 3T Cross Device Development] romskii:
No problem it's not a must have feature but one thing, can you make the OnePlus Camera working with HDR function?

I've tried the app myself already and it seems a bit laggy. OnePlus camera has a much better UI than stock snap
[OnePlus 3 & 3T Cross Device Development] Muhammad Habashi:
I'm now on Open beta 21 "OP 3" shall I flash the firmware+ modem again before flashing Carbon? Or I can proceed flashing only the ROM and gapps!
[OnePlus 3 & 3T Cross Device Development] null0seven:
Do a clean flash. You have the latest firmware.
[OnePlus 3 & 3T Cross Device Development] romskii:
New builds are always created on Tuesday?
[OnePlus 3 & 3T Cross Device Development] darjwx:
Yes, but we had to delay the last one. Should already be out by tomorrow.
[OnePlus 3 & 3T Cross Device Development] SomeGuy.:
Hi, I recently flashed CarbonROM 7.1.2, weekly version 20170808-1525. I also flashed one of the larger GApps .zip.

Is there support for encryption? Will my encrypted storage clash with TWRP 3.0? My device was not encrypted prior to factory reset and flash if this is relevant.

Thanks!
[OnePlus 3 & 3T Cross Device Development] MarcusYang:
Where u download version 20170808-1525 ? I can't find it on carbon website
[OnePlus 3 & 3T Cross Device Development] SomeGuy.:
I'm sorry, this is the thread for the OnePlus 3, I installed for OnePlus 2, my mistake
[OnePlus 3 & 3T Cross Device Development] romskii:
Okay I'm waiting. Maybe because of the new security patch?
[OnePlus 3 & 3T Cross Device Development] darjwx:
Some problems with servers. And a few stuff that needed to be resolved.
[OnePlus 3 & 3T Cross Device Development] drakonizer:
Just to add to this, I was working on a few changes that needed to be pushed before this week's weekly.

A quick but important announcement, all weeklies from now on will have checks to ensure you're running the correct firmware.

The upcoming weekly requires you to be on OB19/OB10 before flashing.

Ensure to flash both modem and firmware for best compatibility. Why, you ask? Because of an update to the fingerprint HAL from OnePlus that breaks compatibility with older firmware.

The weekly is building right now and should be up in a while.
[OnePlus 3 & 3T Cross Device Development] romskii:
You write which are older, how about newer Firmware than OB19?
[OnePlus 3 & 3T Cross Device Development] drakonizer:
I did not mean you need to be on OB19/10 or newer, I meant exactly OB19/10. This is because the zip checks the modem timestamp and the TZ version before flashing. If you're on the wrong firmware, you will not be able to flash the zip at all.

We will gradually update it to the latest firmware, but for now, you need OB19/10.
[OnePlus 3 & 3T Cross Device Development] romskii:
No Problem, going to flash it now.
[OnePlus 3 & 3T Cross Device Development] romskii:
Hey, I've just noticed that the flashlight tile is not working for me on latest build. Screen of gesture is working fine.

I tried to create a log file. Additional information, I switched to HAL1 but I think this can't be a problem. Firmware is also the correct one flashed.

View attachment Tilelog.zip
[OnePlus 3 & 3T Cross Device Development] drakonizer:
From your logs, I definitely see references to your switch to HAL1. This *shouldn't* be a problem, as long as it's done the right way. May I ask how you did it? Did you flash a zip or something? Also, does a reboot or clearing your camera app's data fix the flashlight tile?
[OnePlus 3 & 3T Cross Device Development] romskii:
hmm...I've used this HAL switcher apk because I'm always forgetting the code itself. https://xdaforums.com/oneplus-3/themes/mod-request-hal1-hal3-swichter-t3635266

After ticking HAL 1 I rebooted my phone.

edit: rebooted again and cleared cam data. Now it works again but I'm back to HAL 3. This option is not saved for ever, right? So I need to switch every time myself?
[OnePlus 3 & 3T Cross Device Development] drakonizer:
It's not possible to switch to HAL1 completely on Carbon, because the prop for enabling HAL3 is set during init. An app surely can't make the change, but there are some zips that people have made that get the job done.

This is probably the cause of your problems.
[OnePlus 3 & 3T Cross Device Development] romskii:
Hmm...okay, but you have no plans for implementing a built in HAL switcher? If not it's also okay. This ROM offers so many good features. I like it actually more than DU.

It would be great if you can integrate kCAL settings to the stock kernel. Definitely something I'm missing here
[OnePlus 3 & 3T Cross Device Development] Sithben24:
Can anyone tell me where the setting is to turn off the Heads Up notifications?

And has anyone had the issue where you can't add quick setting tiles that are in the third tier (not enabled ones and not system ones)? I can tap and hold them, drag them halfway up, then it messes up and they revert to where they were so I can't add them to the enabled tiles.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
I don't think there is such an option accessible on Carbon ROM, to change it ON/OFF system wide, for the time being.

There is a workaround using "Power notification controls" under Carbon Fibers/System, you can set it on a per app basis, but it's a bit painful if all you need is to set it system wide.

You can use adb:

adb shell settings put global heads_up_notifications_enabled 0

If rooted you can do it via terminal:

su
settings put global heads_up_notifications_enabled 0

Change the 0 to 1 to turn it back on if needed.

You can use a Tiles app to achieve the same behaviour with a simple tile .
[OnePlus 3 & 3T Cross Device Development] vjdennis77:
Hi guys , now I'm on latest build with blu spark kernel my op3t was flying , great works guys , just one question , do u guys recommend use AKT profile ? Any suggest pls ?
[OnePlus 3 & 3T Cross Device Development] darjwx:
Yeah, we are aware of that. That bug came with N to almost all ROMs afaik. But it's so random and I never faced it on carbon.

Du has merged a commit that kind of workaround that. We may merge that also unless we came across a different solution. Not sure now.
[OnePlus 3 & 3T Cross Device Development] Sithben24:
Thanks for the responses. I always had that bug and never asked why. This is a great ROM though. Extremely smooth and stable. Decent battery life, but I'm a heavy user.
[OnePlus 3 & 3T Cross Device Development] romskii:
I've tried it once and never used it anymore. With AKT and without I was getting around 7-8h SoT, so I don't see any need of that profiles + with that profiles the ROM was really laggy. I don't know how it behaves on this ROM and the kernel you're going to use. Just try yourself.

btw, the modded GCam for Snapdragon devices works perfectly with this ROM. Much better than built in Snap camera.
[OnePlus 3 & 3T Cross Device Development] vjdennis77:
OK the man , I'll try it
[OnePlus 3 & 3T Cross Device Development] romskii:
I'm kind of confused at the moment.

If I enable only the first and second option to pick up the device, ambient display should be shown when I pick up my device, right?

For some reason it's only working when also the 3 option is choosen

edit: I flashed DU just to check those settings and also Deso. Why is there the option for always enable? What efffect has when it's turned off (only that the Ambient Display is not shown up)?
[OnePlus 3 & 3T Cross Device Development] darjwx:
Iirc the default behaviour is to wait some seconds after the display is turned off to enable ambient display. With the always enable option, the Ambien display is enabled as soon as you turn the display off.
[OnePlus 3 & 3T Cross Device Development] romskii:
ahhh okay, so I had to wait a bit longer while I was testing. Thanks
[OnePlus 3 & 3T Cross Device Development] ryanfraser38:
So have just started with with this rom coming from RR because apparently this has better battery life. So my question, for the best battery life should stay on stock kernal that uses interactive governor or flash elemental and set it to conservative?
[OnePlus 3 & 3T Cross Device Development] bkuri:
I'm using bluspark along with Fairpark 3T and I can almost get 9 hours of SOT out of this thing. Not too shabby.

---------- Post added at 10:28 AM ---------- Previous post was at 10:14 AM ----------

FWIW, switching to bluspark finally fixed DT2W for me.
[OnePlus 3 & 3T Cross Device Development] Wilguens Joachin:
What's fairpark?
[OnePlus 3 & 3T Cross Device Development] bkuri:
It's one of the battery-focused AKT profiles. Still getting great performance, though.
[OnePlus 3 & 3T Cross Device Development] vjdennis77:
I used fairpark battery , but battery during little first then now I'm in hawkpepper balance
[OnePlus 3 & 3T Cross Device Development] nexus_vl:
Off topic but worth mentioning:

I'm using a ported android O camera with hdr+ working on this great CarbonRom.

The only thing not working is slowmotion.

This is a first betá so great work from this Ukrainian dev B-S-G (not on XDA): https://4pda.ru/forum/index.php?showuser=243055

XDA was granted permission to share his apk: https://www.androidfilehost.com/?fid=889764386195922284

Article: https://www.xda-developers.com/google-camera-hdr-ported/

Sorry for off topic!

Anyways, on topic I'm using this rom in combination with the fairly new HyperX kernel with already great results on first cycle

Thank you for the amazing development!
[OnePlus 3 & 3T Cross Device Development] kedar18:
Refer to this link for fix of Slow Motion not working on Google Camera - https://xdaforums.com/oneplus-3/one...official-lineageos-14-1-t3588696/post73372438
[OnePlus 3 & 3T Cross Device Development] nexus_vl:
Can you confirm it works on this apk also?

Cause it's far from original Google Camera!
[OnePlus 3 & 3T Cross Device Development] drakonizer:
I second this. People complaining about the camera should try it.The post-processing in this app is far better than the defaults. Unfortunately there's no way we can ship a smali-edited closed source app as part of our official weeklies.
[OnePlus 3 & 3T Cross Device Development] sasa.kljucaric@yahoo.de:
One Question please. Is DCI-P3 included in the stock kernel?
[OnePlus 3 & 3T Cross Device Development] darjwx:
We don't support dci-p3. We are looking into it though.
[OnePlus 3 & 3T Cross Device Development] sasa.kljucaric@yahoo.de:
Thank you for the quick reply.
[OnePlus 3 & 3T Cross Device Development] ryanfraser38:
Does this rom have the feature where you can lock an app in the multitasking so it doesn't close when you close all the others?

Also are you able to add lockscreen text customisation size/bold/italics etc?

Love the ROM so far ??
[OnePlus 3 & 3T Cross Device Development] darjwx:
No to both.

But you really need to close recents apps with 6gb of ram? :P
[OnePlus 3 & 3T Cross Device Development] ryanfraser38:
Just habit haha
[OnePlus 3 & 3T Cross Device Development] vampire36:
[MENTION=5258151]drakonizer[/MENTION] : Hey thanks for the amazing rom. Been using it for a week now and working great as always right since Nexus 4 days ;). There are a couple of things I have noted in my usage:

1. Adaway doesn't work. I tried applying hosts and even enabled systemless hosts in Magisk but still ads aren't getting blocked.

2. Other thing I have observed is voice calls taking too much battery. Voice calls take about 6mAH per minute drain where as 2 to 3 is normal. I remember OOS having similar problem but a few betas back it was fixed.

If you can look into these it will be great :)
[OnePlus 3 & 3T Cross Device Development] romskii:
Hey guys, I'm missing next weekly or isn't it coming this week?
[OnePlus 3 & 3T Cross Device Development] Thunderbolt:
Hope today or tomorrow.
[OnePlus 3 & 3T Cross Device Development] romskii:
Are you adding some changes? :) I'll keep watching the download area
[OnePlus 3 & 3T Cross Device Development] Thunderbolt:
same. Refresh once an hour:) best smooth and performance experience for me till now with blackbird kernel.
[OnePlus 3 & 3T Cross Device Development] romskii:
I thought ur from the carbon team :D
[OnePlus 3 & 3T Cross Device Development] DarKAngel1234:
Is this an EAS Energy Aware Scheduling Rom?
[OnePlus 3 & 3T Cross Device Development] Dhairya:
is the front camera issue solved fc ? and slow motion and 60fps recording? thats the only thing missing would be great if you could add
[OnePlus 3 & 3T Cross Device Development] Thunderbolt:
Thx God now. And im not a part of the team. Im a fan.

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[OnePlus 3 & 3T Cross Device Development] drakonizer:
I did not have any issues with my adblocker, so I'll take a look at what you're using. As for the battery issue, I'll take a look, but it mostly depends on your network and usage pattern, so I can't promise anything.

It's coming soon, something went wrong with the build server. Sorry for the inconvenience.

Nope. Its a very tedious process rebasing all the EAS commits on top of the LOS kernel, so I may or may not take it up as a project later when I've got more time.

If you're talking about the OP3T's front camera crashing in some situations, yes they have been solved. The commit for slo mo on Google Camera is already up and should be in the next weekly. I've got the framework commits needed for OnePlus camera's 1080p60, slo mo and aHDR/HQ in Gerrit already, but it may not be merged for this weekly.
[OnePlus 3 & 3T Cross Device Development] Dhairya:
ah if you could merge it would be amazing, I am loving the rom only camera fc and 60fps is missing rest is just awesome would love to see it this weekly build , it would look a complete build <3 with nothing missing

Just outstanding rom must say

Regards,

Dhairya
[OnePlus 3 & 3T Cross Device Development] vampire36:
Ok I used the magisk adblocker so guess I have found work around for that. :) The voice call thing am 100% sure and even you can check the same with your voice call should be 6 mAH. Same network and stuff OOS had 2 mAH. Take your time no issues to solv it really like your work and appreciate all the efforts :)