yashsingh1/xdaforums huggingface dataset:
[X Play Android Development] Pich018:
The camera ans NFC work for this ROM ?
[X Play Android Development] Rave_r:
Cam working Haven't tested NFC coz I don't need that ****
[X Play Android Development] anil2941985:
Battery draining is there.. but m not having charging issue.. using my turbo charger.. and its getting charged normally as it used to do earlier.. from 50% to 100% within 25 mins
[X Play Android Development] akks1981:
normal Battery drain, normal charging speed, nfc works but first it go on and of..., camera works! open gapps not tested

edit: notification led works 2 ^^
[X Play Android Development] anil2941985:
Open Gapps tested, works like a charm! Using stock Gapps!
[X Play Android Development] Rave_r:
Damn idk y I'm facing this
[X Play Android Development] Pich018:
I have install the ROM on my moto x play ans it's work very well.

Open gapps pico work, camera it's ok, NFS it's OK.

But it's impossible install xda labs. But another aps it's ok
[X Play Android Development] OfficerJimLahey:
Original charger?

Battery drain doesn't seem all that different from (Moto Stock) Nougat to me - since the WiFi is a pig for battery.
[X Play Android Development] OfficerJimLahey:
Weird that one app. Does the cut-down Play version work?

If still not, have a log?
[X Play Android Development] Pich018:
Install it's ok. When i open apk in "apps download " the install it's impossible but when i go in storage and in the folders download the installation it's ok
[X Play Android Development] OfficerJimLahey:
Oh that. New in Android O, you can set other apps to be trusted in installing. Much better than Google Play or always allow unsigned apps. So the app you used to install it just wasn't trusted for the job (yet).
[X Play Android Development] Rave_r:
Yes using original charger... Anyway thanks for the great ROM its good for daily driver flash Xposed magisk both work well hope to see more builds

Thanks Dev.. ?
[X Play Android Development] anil2941985:
critical issue needs to be resolved are

1) Battery Drain & 2) Heating issue

Rest all seems good so far!
[X Play Android Development] Pich018:
Have you a bug with Android auto ? It's impossible for me to use this apps.

Error with Google play service. I don't understand.

I have tested gapps pico, nano and it's the same. Reset no work, clear my account it's the same. Impossible to start this apps. Have you an idea ?
[X Play Android Development] akks1981:
wrong posted by me ....
[X Play Android Development] methuselah:
Try to flash some older version of gapps. Maybe that solves the issue. Flash gzr gapps I guess. They work flawless
[X Play Android Development] Cyril2408:
Hey can someone help me .

I've tried to flash this rom multiple times but the first time I got a black screen with clock and navbar . And after that I just got bootloops. It seems to work fine for everybody else
[X Play Android Development] Pich018:
I have install gzr gapps and reinstalled open gapps and now it's work perfectly ?
[X Play Android Development] 1024rk:
Does GPS work? Now I'm on AOSp, everything is fine but GPS. If it's OK here, I'll switch to it for daily use. And one more, does notification LED have settings to change the color from only white (as on AOSP) to other colors?
[X Play Android Development] nainesh.vanza:
Not able to place call. Seems VOLTE is not working

Any help?
[X Play Android Development] Pich018:
GPS it's OK. I use Waze with android auto and google maps. I haven't bug.

Led no have setting color.

---------- Post added at 08:41 PM ---------- Previous post was at 08:37 PM ----------

Have you activate apps default in the setting for calls ?

---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------

+1.
[X Play Android Development] nainesh.vanza:
Yes. I have checked for phone app as default. Also tried with another phone app by making it default app. But still not able to place call.
[X Play Android Development] Pich018:
Test a reset. For me calls it's ok with Google apps
[X Play Android Development] Programmer-tm:
Report

FM radio is not found, led is not on for plug in power adapter. High battery consumption.
[X Play Android Development] anil2941985:
[MENTION=5720423]OfficerJimLahey[/MENTION] Hi there! Thanks for the Awesome Rom. When we can have the next update? I am facing few issues like, my batter doesn't goes above 80% but it shows full charged. Also sometimes it reboots at 50%, sometime at 30%. Changed the battery also but the result is the same. Any inputs?
[X Play Android Development] OfficerJimLahey:
How long did it take you to replace the battery and how was that simpler than doing a calibration first?

I will likely be running a build this weekend, to make sure I haven't missed anything preventing official status.

Look into battery calibration, and compare with a Nougat ROM if necessary.
[X Play Android Development] anil2941985:
Thanks buddy for the prompt response. I already tried few calibration apps but i dont think it worked for me hence left with no other option than to replace. Can you suggest any best calibration method?

Thanks in advance for the upcoming build.

Cheers!
[X Play Android Development] theARE:
Does Carbon ROM supports signature spoofing for MIcroG?
[X Play Android Development] iBURGER:
Thx for the awesome support, but I am wondering if it is possible to flash it w/o the need of flashing the stock room 1st?
[X Play Android Development] anil2941985:
Really? Was that needed to flash stock Rom before flashing carbon Rom? I don't think so. I had official lineage OS and then i flashed Carbon Rom. And its working Flawlessly...
[X Play Android Development] iBURGER:
I tried flashing after lineage 15.1 unofficial by althafvly (clean flash) but I keep getting boot loop, with or without gapps, even tried zero gapps but no luck
[X Play Android Development] OfficerJimLahey:
Clean flash + system wipe?

Only other thing I can think of is how old your stock was before going custom. But if you had Lineage 15.1 before, that shouldn't be an issue.

Also...

Just uploaded a build from this morning. Unfortunately it's only an ASB bump (my upstream did a rebase - and could not get any benefit out of them so I rebased back).
[X Play Android Development] iBURGER:
Yes clean flash+system wipe..I think last time I had stock rom about 3 years ago ?
[X Play Android Development] thezibrail:
I'm having the same boot loop. From lineage 14.1, don't know why. Tried to clean install with data and system wipe.:crying:

The carbon room logo comes at first, then after quite a few minutes it goes back to TWRP
[X Play Android Development] akks1981:
I use the ROM daily and have no problems!

Try this TWRP:

TWRP from [ROM][9.0.0_r21] LineageOS-16.0 [SEP-VENDOR] [lux] [UNOFFICIAL]

or the original TWRP from the DEV

...and make a clean install!!!!
[X Play Android Development] thezibrail:
Thanks. Will give it a try today
[X Play Android Development] thopiekar:
Did it work? Have the same issue :rolleyes:
[X Play Android Development] akks1981:
bei mir gehts mit beiden TWRP versionen!
[X Play Android Development] thopiekar:
Großartig, probiere es gleich mal aus!

Danke! :)
[X Play Android Development] thezibrail:
Unfortunately I had the same issue:eek:

The only difference is, this time after using this TWRP carbon rom logo came again, it vibrates intermittently for a few minutes, (the vibration is new) then again rebooted back to the TWRP on its own. Don't know why carbon logo is coming but not progressing after that ?
[X Play Android Development] bhanuagarwal73@gmail.com:
Better if you flash stock rom 7.1.1 first then come to 8.x.

I am guessing you have already used other custom roms. So, flash stock ones. Definitely it resolves your issues.

Make sure that you are using twrp given by dev.
[X Play Android Development] akks1981:
have with the original TWRP of the DEV again made a clean install. Is working! something is wrong with your phone. how do you do a clean install? Try this: Start the recovery mode, delete Dalvik / Art Cache, System, Data, Internal Memory, Cache! If you have an SD card, delete the folder Android on the SD card with TWRP! then install only the ROM and start the phone! For me it works so 100%! If it should not happen to you, maybe your phone is broken....or "Better if you flash stock rom 7.1.1 first then come to 8.x."
[X Play Android Development] Rave_r:
Volte not working in latest build
[X Play Android Development] OfficerJimLahey:
Are both from LOS 15.1, and/or both your Lux devices dual-SIM?
[X Play Android Development] OfficerJimLahey:
Probably not the previous one either. I would be surprised if otherwise.
[X Play Android Development] bhanuagarwal73@gmail.com:
Are you going to merge VoLTE?
[X Play Android Development] OfficerJimLahey:
If referring to the upstream commit, not at this time. As in, I have added those changes already, but it broke my build (and fixing the build errors crashed my device via telephony).

I will revisit, since lack of doing so may be impacting dual-SIM users (unless as per a previous post their issue is due to LOS 15.1's partition mapping scheme).
[X Play Android Development] iBURGER:
Yeah I am from LOS 15.1 as I mentioned earlier and my device is a dual SIM indeed
[X Play Android Development] OfficerJimLahey:
What say [MENTION=5340674]thezibrail[/MENTION] on this? Could it be one factor and not the other?
[X Play Android Development] thezibrail:
Yes, my set was previously on some lineage 15.1 roms as well and is a dual SIM one (xt1562). For battery reasons i came back to lineage os 14.1. After flashing carbon rom it can't get past the logo, reverting back to TWRP. Now I tested with other 15.1 ROMs as well. Now this is happening to all these ROMs too.. can't get past to the logo. But previously it was going okay with 15.1. ( I actually tested with 15.1 Oreo build provided in official 14.1 thread) I got some old builds of lineage 14.1. tested with it. But they are booting fine. Not any 15.1 anymore. All these were done with the TWRP that was provided in this thread.

Btw, this is my secondary phone. So I'm open to any testing.. no complaining at all. ?
[X Play Android Development] methuselah:
I was on the same 15.1 build. Except some overheating issues and flashing the very same twrp given in this thread I flashed the ROM. There is not even a single that I have faced with this ROM. Have you changed your data partition to ext4 or f2fs? Because this may create issues sometimes.
[X Play Android Development] thezibrail:
Not that I recall. Haven't touched anything except wiping with TWRP. Does it do anything automatically? And how can I actually find about the data partition type.? Oh ok I'll Google it

Edit: I checked, it's system and caches are ext4, but data is f2fs. Is that the cause of the problem? What is it supposed to be?
[X Play Android Development] thezibrail:
If you're already out of your warranty period, you may give it a try. Google can help you find the "many" reasons to choose a custom rom over very old stock ROMs.

I, personally shifted to custom rom in this Moto x play just after marshmallow.. the reason: official nougat came out too late for this device, let alone monthly security updates. And lineage os since been serving very well. These developers, better should I say, these "Gems ?" , actually put a lot of hard work wholeheartedly to squash the bugs. In deed, I can't put enough word together to thank them.
[X Play Android Development] anil2941985:
Hi ! Just wondering When we can expect the next update? Probably with night mode!
[X Play Android Development] methuselah:
Let the July security updates comes out. What else you require? The ROM is working perfectly fine. Just few overheating issues.
[X Play Android Development] akks1981:
Android Security Bulletin—July 2019

https://source.android.com/security/bulletin/2019-07-01
[X Play Android Development] anil2941985:
Personally, i need the theme feature like what we have in Resurrection Remix rom like choosing light and dark theme, accent color etc along with the latest security patch.

I wish if that can be done with the upcoming update, then it will be great.
[X Play Android Development] OfficerJimLahey:
Carbon has that with Pie, but this is Oreo.
[X Play Android Development] anil2941985:
SAD! Neither there is any nearly stable RR Rom available nor anybody working on Carbon Oreo!
[X Play Android Development] methuselah:
You work yourself and share the build with us then ?
[X Play Android Development] anil2941985:
Haha! Sure! If common people like me had the power, we would not have looked upon Avengers like you all devs. Thanks Anyways!
[X Play Android Development] methuselah:
I am not developer but I know when to stop at asking stuff buddy.
[X Play Android Development] akks1981:
[MENTION=5720423]OfficerJimLahey[/MENTION] Thank you for the great Rom! Can you please update the rom to the Android security patch for July 2019?
[X Play Android Development] OfficerJimLahey:
Last I checked there were no new tags for the July ASB in AOSP 8.1. Though that was a few days ago now. I may have time today to give a more appropriate look, but it will be the late end of the day (whereas now is morning for me).

I also want to update some info on this thread as well.
[X Play Android Development] OfficerJimLahey:
A day late to look, but still no July tags. Only June as the latest.

Seems like El Goog is winding down on Oreo. Since I have been unable to sort out the dual-SIM / LOS 15.1 issue (whatever was the cause), the fact the that I struggled (without success) the upstream RIL updates (which may help dual-SIM if that was the issue, but I could not get any benefit from it), et cetera, I will be shifting focus (come August) on ...

CarbonROM 7.0 Opal (aka Android 9 Pie).

I have a couple other projects I want to get into a forward state first, hence my delayed start.
[X Play Android Development] deguzz322:
Hello! Im glad to test this rom!

Install Stock MM in my Moto X Play then install TWRP 3.3.1 and then install Carbon ROM and the truth is that I dont see it fluid. Even the transitions in the opening of the app drawer and the quick setting panel is relatively slow. This is normal?
[X Play Android Development] methuselah:
Install Nova launcher. And rest assured everything is fast. Or lawn chair.. but I would suggest Nova launcher. Best since it was born
[X Play Android Development] deguzz322:
But then, is it normal for the interface not to be fluid? :eek:
[X Play Android Development] methuselah:
What you expect from 615 processor with 2 gb ram?
[X Play Android Development] deguzz322:
In my moto g 2015 runs more fluid even android 9 pie. Why? SNP 410 with 1 gb ram
[X Play Android Development] Sr.Jagger:
Less density and resolution than our moto x play... Maybe this plays a huge rule in performance.
[X Play Android Development] methuselah:
Well everything is fluid for Moto X-Play. As soon as you change this launcher lol . So change it.
[X Play Android Development] PlayerEmers:
got some problems while trying to install gapps, but i did what Pich018 said:

and it worked just fine

for now it's a very solid rom, simple and fast, still no issues so far

just a small question: when updates are released, do i update from the update settings on the phone?
[X Play Android Development] methuselah:
Please read the thread. Op has stated his views about updates.. and no these are unofficial builds and you need to flash manually until they are officially supported
[X Play Android Development] PlayerEmers:
ok
[X Play Android Development] icecoldsipra:
I installed this rom yesterday and I must admit its buttery smooth. Everything is working fine. I just have one problem. My phone keeps rebooting every now and then. It initially used to reboot once in few hours. It didn't really bother me much. But after using the rom for almost 24 hours, the frequency of reboot has increased. My phone now reboots at least 2 to 3 times every hour. Anyone has this problem? I did a complete clean install.
[X Play Android Development] PlayerEmers:
i had a very similar problem like this but with the official lineageOS rom

first few weeks/months it was fine, but after a while, soft reboots started happening... i never found what was causing this but some people blamed lineage itself for never finding this bug/fixing it

usually my phone would soft reboot 1/2 times a week, but sometimes the phone rebooted 2 times a day

i installed the carbon rom a couple days ago just like you, but i still haven't suffered with any soft reboots like yours (or like when i was using the official lineageos rom)

if any random reboots happens to me, i will post an update here
[X Play Android Development] icecoldsipra:
I never had any soft/hard reboot issues with Lineage OS 14.1 rom. But I did have some problems with apps like Android Auto not working well with my car recently and I was forced to look for alternatives. I have no complaints about this Carbom rom as it is lot more smoother than LOS in my phone. Plus, Magisk, Xposed and Viper4Android all of which are the first things I look for work really well. I also had a similar problem like one user quoted rom shutting down with battery at around 50%. I too had the same problem today. Now, I am scared to leave my phone without charge.

I noticed there is a Carbon rom with Android 7.1.2 updated with March 2019 as the date. I will give it a try and see if the performance is similar.
[X Play Android Development] PlayerEmers:
edit: nvm, i did a factory reset
[X Play Android Development] OldUncle:
Is video recording working in this ROM?
[X Play Android Development] OfficerJimLahey:
Have done this very thing a month ago.
[X Play Android Development] OfficerJimLahey:
Providing an update since my last, and because I had been asked privately how my progress has been for Opal on Lux.

In general, I have hit burnout. Because I use the Moto G5 (Cedric) as my DD, I am more interested in resolving the remaining annoyances while others are still focused on Pie. But I have not seen much energy for that even, as of late.

The Lux problem (which comes up via the Moto G5 series as well) is that Pie is, when you look at the numbers, not a very good idea for a 2GB RAM device. Task switching does not seem terrible on Cedric, but my post-install config is inherently a tight ship which still leaves me with around 60MB memory free or used for cache. Compare that to Oreo where 'free -h' will note an additional 200MB available. Granted, the test also has a change in architecture, so that difference could have a lot to do with aarch64. Both scenarios involved two different devices (to make a total of four) where for avoiding some bias, included a fresh install on a Cedric, and other tests saw app histories cleared and devices rebooted before getting the memory information.

Because I have had people complain of an unusable device (in this case, the Moto G5 Plus, aka Potter), 2GB of memory would make for a tough sell. I personally find it difficult that the 2GB wall could be hit this easily, but perhaps I am taking the numbers too much to heart.

I am going to rethink the Lux strategy (again), as well as consider my options for Cedric. If by some miracle the Android Q base system has a better control of memory (which is a difficult concept since part of memory management is about using it when you can, and setting aside the unnecessary when it is needed - the free command may not reflect the best storyline), I will want to try it out myself.

At this point, I just don't know where this leaves me with Lux.
[X Play Android Development] methuselah:
Well afaik pie is concerned I would like to see towards the honor 5x. It has got pie lineageOs. The developers is now working with the ram management. There are glitches here and there. Honor 5x just got 16gb internal. Whereas lux got 32gb. I don't know too much how Linux swap works. But they are trying with lmz compression in the device trees. I would really like to you to talk to him and see his device trees. Maybe you can get answers. The thing is we are having a lot issues. Now I use messenger , Hangouts, xda and chome on honor 5x. It works but makes device hot. But where ever you take lux we are thankful to you for working on this device and giving carbon.
[X Play Android Development] OfficerJimLahey:
Interesting take. It would be something to look into. Though I should mention (since the playing field is a bit more level), Lux varies between 16GB and 32GB (the XT1563 I have is of the 16GB type). Based on the specs, Honor 5x kinda follows Cedric (Most to G5) for having the rare 3GB variant, except all the Honor variants have the same storage (Cedric's lone 3GB model has the 16GB mmc though).

A lot to sift through, but I got to get post-burnout first. The next month is going to be much of the same stress however. Hoping beyond that, some key barriers will be resolved.
[X Play Android Development] OldUncle:
[IMG="Error"]https://pasteboard.co/ItJ0afn.jpg[/IMG]

Tried to install on wiped everything except internal storage.

I know that was wrong since it is required to flash over the latest stock ROM.

But I can not find the latest Stock ROM + proper guide for reflashing to Stock.

I would appreciate if anybody gives me links for ROM and Guide.

Thanks in advance.
[X Play Android Development] OfficerJimLahey:
Yeah, standard TWRP wipe + System is enough. Also hoping this will set in a habit to back up as much as you can in TWRP (for the initial backup, don't even flash TWRP...boot it instead so you can back up your stock recovery as well), maybe having a couple different copies, before doing anything.

That said, finding full stock with the same version or slightly newer for your model should not be too hard to find but to get the right region as well may not happen.

Example, I have the XT1563 that had its final version 7.x, but my RGRCA region (or even RETCA) was an impossible task (this all happened in my failed attempt to relock the bootloader). I settled for RETLA, and this Latin American version still seems to support the same bands.

https://github.com/motoxplay/stock

...may help in your quest.

In a note not related to this post, I have been tasked to keep the security bulletins up to date on Noct. Considering I have one CAF device set up to test Noct (Lux) and one non-CAF device (shieldtablet), a side effect of checking the monthly updates means I have Noct builds again.

For those who had the dual-SIM bootloop before, device-wise nothing has (yet) changed. At some point I will look at the upstream IMS changes again, but in the meantime more attention is needed to look into that issue (which I still want to blame on the partition mismatch since the logs I have previously received talk more about failed keymaster than any IMS).
[X Play Android Development] plb-dev:
5.1 or 6.1

Which version must I install on my Dual SIM XT1562 to use as my daily driver? Which one has fewer issues?
[X Play Android Development] OfficerJimLahey:
For dual-SIM, stick with Nougat. Unless you want to prove or disprove the existing theory that this ROM will bootloop on dual-SIM.

If you are willing to do that, expect to provide a lot of logs for it and that it will be your responsibility to get back to a ROM that does boot (as in, do a great job on backing up everything you can before proceeding, as you will most likely need it later).
[X Play Android Development] tyamamoto:
I've clean flashed 25 August version onto my XT1562 dual SIM, and haven't seen any bootloop for now.
[X Play Android Development] OfficerJimLahey:
Great to hear. So I have little idea why others have issues unless they are really that abusive to their partition tables.

If this was to affect you, it would have happened by now. ;)
[X Play Android Development] tyamamoto:
Agree. I was from unofficial LOS 15.1 built by squid2. Wiped and flashed Carbon with your TWRP this time.

I would suggest starting from stock including partition to anyone experiencing issues.

Thank you very much for your contribution!
[X Play Android Development] crazy4jack:
So i flash this ROM - recommended by the many ppl on forum - and at start phone heats up, and i settings in have FC when i try open root settings for installed magisk ;)