yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] AnierinB:
Thanks for the quick response. Look into amaze file manager.. Its open source and i believe crdroid uses it as their built in alternative
[Nextbit Robin] hairycheez:
going to Settings->Storage->Explore opens the file manager for me but the downloads app doesn't.

Just got Amaze from f-droid tho so I'm set.

Also I flashed stock N108 7.1.1 the proper way hoping might fix my NFC but no luck

Still this is the best rom for the Robin. Great work!

Thanks
[Nextbit Robin] frap129:
We did. We refuse to ship or support Amaze because it includes smb v1 supoort, which is nothing but a sack of vulnerabilities that allows malware to infect your device with ease. Nothing against the Amaze devs, Amaze is a great fm, but including samba v1 support is the main reason we wont include it. More info on the issue can be found at https://arstechnica.com/information-technology/2017/05/a-wormable-code-execution-bug-has-lurked-in-samba-for-7-years-patch-now/
[Nextbit Robin] xBane_:
Fastest rom I've ever used. Great job, just wished it had as many customizations as RR.

Only gripe is performance in games like real racing 3.
[Nextbit Robin] AnierinB:
I noticed the github for the kernel returns a 404.. Are you waiting until things are more complete/stable to release? Or planning a custom kernel? Been pretty excited about eas for the Robin. I've noticed a great improvement on heat and battery life without sacrificing performance and I must say you've got me stuck on carbon. Great rom, thanks a lot. Probably gonna make a splash for the ROM today :)
[Nextbit Robin] frap129:
I guess I forgot to update the URL. Fixed now. I'm currently working on a custom kernel, but most of that source is kept local for now
[Nextbit Robin] rabrol:
Hey All.

I'm currently running a Nextbit on Lineage OS official build from about a month ago. Considering switching over to Carbon. This is for the wife's daily driver. Having read through all the posts, it looks like this ROM is stable enough for that.

She uses DATA only (all voice traffic being routed through VoIP). I'm hoping EAS would not mean that the device would sleep, and thus she would miss incoming VoIP calls.

I am also wondering if this ROM allows adjustment of when the phone switches from LTE to 3G. For VoIP I need it to grip as tightly to LTE as possible before reverting to 3G. Or I might consider setting to LTE only. Does this ROM allow either configuring the threshold of changeover, or forcing LTE only? Lineage only permits preferring LTE over 3G. I cannot seem to force it.

Thanks for the help, and hoping I get to try this ROM soon!
[Nextbit Robin] AnierinB:
I have not experienced any notification delays while using carbon ROM as far I can tell. As for your 2nd question, You can choose your preferred network type (LTE,2g,3g) but I believe that's as far as it goes for now.
[Nextbit Robin] ashirviskas:
I accidentally started screen recording when I wanted to make a screenshot and my phone just froze. It either needs to be removed or fixed. Otherwise, it's a great ROM!
[Nextbit Robin] frap129:
Thanks for pointing this out, I'll look into ir
[Nextbit Robin] AnierinB:
So this morning before I went to work I woke up to my alarm going off and when I ended the alarm I got up to get ready. After I was done, I checked my device and it was stuck with the screen off. The only way to fix the issue was to hard reboot the device. I'm going to try and reproduce the issue while logging it here soon.
[Nextbit Robin] frap129:
This has been reported a few times, but for some reason I cant reproduce it. Every time I think it happened, the screen just turns on a second or two later
[Nextbit Robin] nydmt:
Yea i did this a few times by accident, the phone moves incredibly slow (almost frozen) until you can manage to stop the screen recording. An option to disable the volume up+power shortcut would be great.

Same thing happened to me an hour ago, after a few minutes of not looking at my device the lock screen just eventually came back.
[Nextbit Robin] pintasmapila:
Also happened to me last night. I thought it was something I installed, but apparently not.
[Nextbit Robin] xBane_:
New issue: fingerprint sensor. It was working great on Resurrection Remix N, but on this rom it's basically nonexistent. Constant "fingerprint hardware not available" or "fingerprint hardware not available" and whenever I enroll a finger it never detects the finger.
[Nextbit Robin] frap129:
Log? Works fine for me on the 3 devices I've installed it on.
[Nextbit Robin] AnierinB:
Try to get logs people.. The dev can't do much about things when you just say "it also happened to me" not that I'm one to talk just trying to be of help here.

https://play.google.com/store/apps/details?id=com.tortel.syslog
[Nextbit Robin] :
Here's something I noticed.

1. The "Blurred Expanded StatusBar" toggle in CarbonFibers->Displaytweeks does not blur the statusbar. It toggles transparancy.

2. I have "Blur StatusBar Background" turned on. When I turn off screen with power button while statusbar is expanded, next time I turn the screen on, lockscreen background is changed to a blurred image of what I had on screen when I turn it off.
[Nextbit Robin] Flak:
Any plans for OTA?
[Nextbit Robin] frap129:
Thanks for saying that!

Blur is bad, will be removed in our O release

All the rom side stuff is done, waiting for [MENTION=1523205]PhaseBurn[/MENTION] to set up the server side
[Nextbit Robin] jabashque:
Hey [MENTION=5051294]frap129[/MENTION], is there any additional info you need to help deal with the NFC problem? I'm one of the people whose NFC isn't working, and wouldn't mind running things on my phone to help, since you said you haven't reproduced that issue on your own phone.
[Nextbit Robin] frap129:
I think I may have fixed it, I'll try to get a build up later once I confirm.
[Nextbit Robin] frap129:
New test build! This one has NFC fixed, updates to the power HAL, an improved kernel, and some other misc things. Please note, this build contains features that aren't in the official Carbon source and are just things that I'm testing locally, so don't expect this to reflect a true official build.

https://www.androidfilehost.com/?fid=745425885120753470
[Nextbit Robin] DECHTECH:
Awesome! NFC working here :D

I noticed that you've added the colour engine from PA, noticed the green as soon as I started setting up the phone! ;) Thankfully I won't be missing it once this rom goes out of testing, I use substratum anyway.
[Nextbit Robin] L3R0N:
Thanks for the update. Battery seems same, I love the color engine thats added in tho...
[Nextbit Robin] AnierinB:
When enabling custom header my device went into a system ui crash loop. I did have a substratum theme enabled with custom headers but even installing the substratum recovery.zip I get the same outcome. [MENTION=5051294]frap129[/MENTION]

Clean install 8/4
[Nextbit Robin] frap129:
Known issue, working on it
[Nextbit Robin] valhallen.282:
Thank you for all the hard work and time you've put in...

My main use for the Robin is watching videos; YouTube/twitch/Netflix. Unfortunately I am not able to get past roughly two hours of videos without a full to 10% fall. Is it something that you are aware of?
[Nextbit Robin] jabashque:
Hey, my phone was starting to run slower as I was having more tasks running at a time, until it eventually froze up and did (I suppose) a "hot reboot". Fortunately, that means the relevant logcat entries are still there, and as such, I've attached a logcat from the last hour before it rebooted here. (08-06 22:50 is around where it finishes rebooting)

Problem is, I do not know what led to the hot reboot, so I can't really give any hints as to what caused it to happen. Sorry about that. :(
[Nextbit Robin] frap129:
Is that something your able to do on any other ROM? Not to be rude, but any more than 2 hours of streaming seems a little bit unreasonable of a goal for a phone like the Robin.

Thanks for the log! Will look into it
[Nextbit Robin] valhallen.282:
Actually sir, I have. I manage to watch an entire movie of 2hr 30 minutes(Hindi movie) at 60-70% volume easily.

I watch the Dota2 championships on live stream and normally get through two full average matches before needing a charge. This time I was out only half way through the movie so I tried again with Dota 2. I was out just after the first match and commentary.

I have two accounts synced. One Gmail and one EAS outlook. I only test 48 hours after installing a ROM and completing all sync. The other apps are WhatsApp, telegram, Instagram, Facebook and messenger. No betas of any of them. Typical install uses either Mini or full gapps from Open Gapps. Nova Launcher is used. Substratum with Swift Dark theme. Testing is ALWAYS done from 100% to 5%. Only over Wifi. No data. Router is roughly ten feet away with clear line of sight.

I hope that is enough detail.
[Nextbit Robin] frap129:
Wow, I'm not sure that I could even due that on my 6P! I'll look into it, though this seems like an issue that may need to be solved via a custom kernel (once I get around to releasing mine)
[Nextbit Robin] jabashque:
Another hot reboot again, this time while in Snapchat. I forgot to mention that I'm rooted with Magisk--would that invalidate any of my complaints? Reboot happened at 08-07 11:27 and finished at 08-07 11:30--logcat is truncated to start at 08-07 10:27
[Nextbit Robin] Syndor:
So far so good.

I installed this on Saturday and I've been using it heavily.

The thing that impressed me the most was idle battery over night it took away 1 %.

SoT is around 4 hours for me of various use, some YouTube some Facebook some browsing and some streaming.

Considering I always have my quickcharger on me this is amazing battery life.

Edit. Only bug I've had was the notification light stayed on , but I know you guys already know about that and a reset fixed that .
[Nextbit Robin] frap129:
This is really confusing me, since no one else has experienced this, especially as frequently as you. Its not likely, but it could be an app you have installed or the gapps (or microg) you used. Any suspicious ones?

Glad you like it!
[Nextbit Robin] jabashque:
I was using an application that is not regarded highly here so that I could repackage a new apk of an app with the Location permissions disabled for my dad, who's running Android 5.1 and as such can't disable it on runtime. I hadn't granted it root access, but I uninstalled it after the 2nd hot reboot that I've posted here, in case it actually had something to do with the instability.

Otherwise, I'm rooted with Magisk with the "BusyBox for Android NDK" module installed, and i have Stock GApps from Open GApps. I did a clean flash to upgrade to the 08/04 build, flashing Open GApps Stock immediately after it was done.

I might try to look at the logcats I posted here and see what sort of conclusions I can draw. Can't really promise anything since I don't have experience with that, though.

EDIT: If I do get another hot reset, I'll post the log here and redo a clean flash with the 08/04 build again. Still plan on putting Magisk + Stock Open GApps, but if it does repeat after that, I'll know for sure it's something on my side.
[Nextbit Robin] frap129:
At least you have a valid reason for using the app that shall not be named :p, but unfortunately I can't help if thats the issue (which it most likely is).
[Nextbit Robin] jabashque:
Well, it'll be disappointing if removing that software doesn't do anything about the hot reboots. In any case, I ought to learn more about the Android watchdog and understand the conditions that lead it to kill the system process in both times I've posted the log, cause it doesn't seem like there's much info you can really get from the two logcats I posted, other than the ActivityManagerService getting deadlocked (?)
[Nextbit Robin] carguy303:
I had a hot reboot using Snapchat but it happened once and now the app runs fine.
[Nextbit Robin] TheC92:
I'm curious about the current progress of the custom kernel. And is LOS also supported?
[Nextbit Robin] valhallen.282:
4 episodes of Star Trek Deep Space 9- 45 minutes each + couple of YouTube videos. It's been 22 hours since charge. This is from yesterday. I'm on aicp. I love your ROM. But I watch stuff on this device more!
[Nextbit Robin] Syndor:
Here are my SoT , at the end of the day.

Edit.I don't think I could manage 5 hours, but it would be close with battery saver on fr 15 to 0%
[Nextbit Robin] frap129:
The kernel is pretty much done (for ROM's that use LOS based kernels), but I need to work out some stuff with the PowerHAL before I can release it.

Wow, thats quite a lot!
[Nextbit Robin] jabashque:
I do have to say, thank you frap129 for getting CarbonROM running and bringing EAS to the Robin. It's what makes me not regret getting the Robin, since it resolves the overheating and battery draining issues for me.
[Nextbit Robin] cmb6:
Since switching to Carbon, my phone rarely exceeds 38 C. In addition, my battery life has undoubtedly improved.

Thank you, frap129.
[Nextbit Robin] jabashque:
[MENTION=5051294]frap129[/MENTION] I've done a clean flash just now with the 08/04 build and tried casting my phone screen to a Chromecast 2nd gen device. Unfortunately,

it still has the video corruption issue, as shown here. At the beginning of the casting, the TV screen updates fine, aside from the corruption at the top flickering on and off. However, once I leave the quick settings window, the TV output freezes, either with the corruption at the top or not depending on what frame the Chromecast was on before freezing. Nothing happens until I disconnenct from the Chromecast. I casted multiple times, but the session that I took a picture of happened at 08-09 22:14:14.461 in the attached logcat.

The logcat probably won't help much, to be honest. You'd have to find a way to replicate it on your own devices. Or, if you don't have a Chromecast, you'd probably have to tell me what else I'd need to run so that you could collect enough data.
[Nextbit Robin] WewLolz:
Flashed the latest Build yesterday.

Battery Life and standby is kinda hard to tell, i get random 4-5% drains on this rom within an hour sometimes. Around 3.5 hrs SOT with moderate to slightly heavy usage with brightness turned down to 25% on WiFi and using Data Saver. But when the battery isnt draining, Its probably the best standby I've seen on any ROM so far ( 1% or less in an hour on wifi).

Performance-wise, its probably the worst i've seen in a while on any ROM. ( I know the devs are working hard to make this ROM happen, but I think it's better to be honest so they can fix this issue.) The boot time is the fastest on any ROM here and thats sweet.

Some Games like clash royale make the phone overheat and stutter, more demanding ones like lonely are playable. Sometimes lags when i get notifications from apps like WhatsApp ( even if its one or two notifs). Occasional slight stutter/lag when pulling down the notif drawer or going through recent apps or opening the app drawer on nova launcher.

I disabled the notification LED on first boot since i find it annoying so I can't really say anything regarding that. Camera Quality seems to be the same as any nougat ROM.

Overall this ROM has REALLY GREAT POTENTIAL. I was considering to switch away from the robin due to the awful standby but ROM's like these could fix that.

Looking forward to [MENTION=5051294]frap129[/MENTION] fixing these bugs and releasing that sweet kernel :) .
[Nextbit Robin] Syndor:
I had to go back to paranoid android :(

I LOVE this rom, and I want to be able to use it as a daily driver, but as of now the bugs don't allow me to, I got some missed alarms, and some other bugs that are just too much for me to take, while watching some videos I would get random reboots.

Some of the pros, best standby even with weak signal, my phone never got hot, and it was generally snappy while using it.

And one thing I really, really miss in paranoid is the brightness adjustment from swiping the statusbar (native)

I hope you can fix a couple more bugs, and I would be HAPPY to use this as a daily driver.

Just a little bit more bugs fixed.
[Nextbit Robin] haroldf1racing:
REPORT: The Rotation Screen setting doesn't work.
[Nextbit Robin] cmb6:
Those bugs seem idiosyncratic. I haven't experienced random reboots, missed alarms, or trouble with the screen-rotation settings.
[Nextbit Robin] Syndor:
I don't have a logcat, because I don't like to rush anyone, but I was watching youtube while wearing headphones, and I got a bootloop until i removed my earphones.
[Nextbit Robin] frap129:
Many of the reported bugs (some of which I have experienced myself) all seem to be kernel related and thus, likely a result of the EAS implimentation. This was a nice experiment, but I think its time to move on to something more stable. Next build won't have EAS built in.
[Nextbit Robin] AnierinB:
How's it looking? Should I edit it some more is it good the way it is? [MENTION=5051294]frap129[/MENTION]

I might add the cow going "moo" in the letter B in "robin"
[Nextbit Robin] frap129:
As stated previously, this build does not include EAS, though it does have improved boost settings, Shadow Scheduling enabled, and some other under the hood improvements that should keep battery life and performance up. No unknown bugs in my testing. Unless major bugs are found, official ether builds will roll out next tuesday.

Download: https://www.androidfilehost.com/?fid=961840155545589446
[Nextbit Robin] jabashque:
If you don't mind answering, what is Shadow Scheduling? A google search didn't yield anything useful. (and has screen casting via Chromecast ever been an issue for you on your CarbonROM test builds? Might make a nandroid backup of my current Omni install to test out CarbonROM again)
[Nextbit Robin] frap129:
Haven't had an issue with screen casting personally, though I haven't tried on ether. Shadow Scheduling is a proprietary Nextbit/Razer/PA technology that extends the existing HMP task scheduling in the kernel, allowing programs that run in the OS to determine when and when not to move a task from a little core to a big core, optimizing performance and power consumption on a per-task basis.
[Nextbit Robin] jabashque:
So, thus far, core 5 and 6 show up as offline in Kernel Auditor, and NFC can't be turned on. It's 5:30 am here and I have work, so I'll provide logcats + dmseg logs for both later tonight. But I wanna know if anyone else who's trying the latest builds are running into the same issues.
[Nextbit Robin] frap129:
Forgot to redo my NFC fix after getting rid of EAS. Will do in another build. Cores 5+6 should only turn on when needed.
[Nextbit Robin] Sparubens:
Can anyone check if the static screen bug (noise) is still there when waking the phone?
[Nextbit Robin] jabashque:
For NFC, that's good to know--at least it wasn't another bug that cropped up, haha. For cores 5 and 6, I was just afraid when Kernel Auditor showed them as offline, but what you said makes sense. (EDIT: Didn't notice Kernel Auditor shows uptimes for the big and little clusters, and I noticed my phone's big cluster was up for 3/5 the time the little cluster was, so now I know that it's working as intended; thanks. Is this a new addition? Earlier builds had core 5+6 online all the time.)

Now, for the screen casting, I still have the same kind of bug I mentioned about back in this post, from build 08/04. I'd like to know if you have the same bug if you cast your screen from ether, since AOSPA 7.2.1 and OmniROM 08/13 worked fine on ether.

Yes, it's still there, and as usual, it lasts for only about 1/10th of a second.
[Nextbit Robin] frap129:
Ether will begin official builds tomorrow! The lights bug and NFC bugs were fixed, only issues that remain are static screen and screen casting.
[Nextbit Robin] jabashque:
Honestly, among Omni, AOSPA, and Carbon, I've been sticking with CarbonROM because you're the most reachable device maintainer of them all. Gandalf seems to be busy due to real life obligations, and TheCrazyLex doesn't seem to respond to concerns directly in the AOSPA forum. There's definitely more to polish up, which is a given since the ether port started only a month ago, but I value the fact that my voice can actually be heard. Thank you!
[Nextbit Robin] xBane_:
Hey, can anyone tell me about battery life on the current build compared to the 07/28 build?
[Nextbit Robin] jabashque:
Personally, I don't think I've noticed much of a difference--my phone's battery drain rate varies pretty widely. In both builds, my phone drained from ~15-25%/hr with screen on and ~1-3% with screen off.
[Nextbit Robin] willkane:
So which build is the last version including EAS?

Is it possible to add EAS support in a version?

Thanks.
[Nextbit Robin] frap129:
No, EAS is not stable.
[Nextbit Robin] willkane:
Ok, thanks ;)
[Nextbit Robin] :
I already look forward to flashing the new build as the notification light is fixed now :). Does the camera work properly regarding the manual focus?
[Nextbit Robin] frap129:
Yep, at least in stock camera and camera NX
[Nextbit Robin] xBane_:
Hey, checked the official CarbonRom download center, and Robin isn't there yet. When will it be up?
[Nextbit Robin] frap129:
The first official build is here, get it while its hot! Because this build is signed, you must clean flash, ie wipe data or it WILL NOT BOOT. I've tested this build, so any reports of it boot looping will be deemed user error. That being said:

Download: Get CarbonROM
[Nextbit Robin] DJ_SpaRky:
It is there now.

https://get.carbonrom.org/device-ether.html
[Nextbit Robin] frap129:
ninjad
[Nextbit Robin] DJ_SpaRky:
Just coincidence, I just happened to be checking for it too and found the link, figured I would share. :D

I will try it once I have time to go through a MegaWipe (complete reload).
[Nextbit Robin] iluvatrix:
what is this "MegaWipe (complete reload)"?
[Nextbit Robin] DJ_SpaRky:
Backup everything that you can, then boot into TWRP, Wipe System/Data/Cache/Dalvik/Internal Storage (SD Card), then reboot back into TWRP and install ROM/GApps/SuperSU.

The difference is the Internal Storage. I have found that it helps start with a clean slate, no residue.
[Nextbit Robin] Sparubens:
Will the staticnscreen bug be fixed in future releases? Can't wait to use this once it is fixed
[Nextbit Robin] frap129:
No, it most likely won't be fixed. A small flash that randomly occurs when waking that lasts one tenth of a second that happens across devices and roms isn't really a priority issue, and shouldn't deter anyone from trying a rom
[Nextbit Robin] L3R0N:
I use Carbon and it doesn't bother me one bit. Thanks for making this official.
[Nextbit Robin] AnierinB:
I'm not entirely sure but I think this may be the fix

https://review.lineageos.org/#/c/185230
[Nextbit Robin] rahul200023:
i came from this aokp to this rom, its my first time flashing carbon rom and it is smooth. It absolutely killed geekbench with scores slightly higher than the nexus 6p. This is an amazing rom, keep up the good work (its also great to see the working led notification light)
[Nextbit Robin] akeemk:
I'm testing out this ROM and loving everything about it. I'm thinking about making it my daily driver due to its stability and features (the static screen isn't a bother at all)

I have a feature suggestion and forgive me if it's there already, but is it possible to disable notifications peeking while keeping the vibration and sound?
[Nextbit Robin] DECHTECH:
I had a break off of Carbon due to EAS causing various issues. But I've flashed the AUG22 build and it's very stable, and super smooth! I won't a comment on battery life though as my battery is kinda fried, gotta buy a new robin xP.

Keep up the good work! And I hope we see CarbonROM 6.0 soon ;)
[Nextbit Robin] till22:
I'm new here, last time I had Carbon ROM installed was on the HTC One m7. Already downloaded everything to root my Robin and install Carbon; it's arriving Thursday and I'm excited to see how it fares!
[Nextbit Robin] Sparubens:
Just saw new build is up. Thanks to [MENTION=5051294]frap129[/MENTION] for the continuous work.
[Nextbit Robin] rahul200023:
Does the new build also require a clean flash with data wipe or is a dirty flash ok?
[Nextbit Robin] L3R0N:
I did a dirty flash from the previous build (no wipes done) and all is fine. So you should be fine with a dirty flash as well.