yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] xBane_:
Only while streaming, I dont download media. It's been happening less often lately, but still if i'm trying to SMS/MMS it stutters constantly (until the message has finished sending) if i'm receiving a message, it stutters as well. Honestly, imo this is sorta ridiculous for a pro dev team like AOSPA to have bugs like this; but considering its one of, if not the only bug i've experienced I'll let it slide for a little while more.
[Nextbit Robin] DECHTECH:
The changes were merged before it was built, so I'm 90% sure it's patched :)
[Nextbit Robin] /root:
The notification LEDs worked after a restart but charging LED won't work.

---------- Post added at 10:03 ---------- Previous post was at 09:54 ----------

Adding to what DECHTECH said

The change log for 17 October 2017 has a lot of WPA fixes.

And the build date for Robin is 18-Oct-2017

https://get.carbonrom.org/device-ether.html

So fair to assume the new build has those fixes.
[Nextbit Robin] kushal16:
on the 18/10 build, the problem looks solved. Thank you very much!!! Now can finally make and receive calls without any disconnection!!
[Nextbit Robin] ukwizard:
Is there any way to get call recording working on this rom?
[Nextbit Robin] Sparubens:
Can anyone check if the static bug is still in 18/10?
[Nextbit Robin] /root:
I see the static screen bug for a fraction of second sometimes when I press the power button to wake up and unlock the device. But doesn't happen all the time.

I just started using this ROM, in which all scenarios had you faced it? Let me know so I can test them and tell you if it still happens.

Edit : I will keep editing this reply with the instances I see the static bug as reported by other users.

18/10 Build

- Sometimes on waking Up and Unlocking the screen using power button

- Most of the times happen when proximity light sensor auto lights up the screen after/during calls.
[Nextbit Robin] xWolf13:
No changes on Gerrit concerning the static screen bug. It's still there.
[Nextbit Robin] rahul200023:
Any oreo update?
[Nextbit Robin] Mrcactuseater:
Soon™
[Nextbit Robin] kushal16:
This question is out of this thread, but just wanted to know if there is any way to unlock band 40 in our nextbit robin. Band 40 is being used by most of the carriers in India, so I'm having issues with the download speeds compared to other phones which do support band 40.
[Nextbit Robin] /root:
[MENTION=5601531]kushal16[/MENTION]

FYI,

Bands Robin Supports

GSM 850/900/1800/1900

HSPA 850/900/1700/1800/1900/2100

LTE Bands 1/2/3/4/5/7/8/12/17/19/20/28
[Nextbit Robin] kushal16:
That's the reason I asked for a way to unlock band 40 on my device
[Nextbit Robin] j41224:
I can't find any options to set a long press on the back button to kill app. Usually that would be in navbar setup but it only has were you can add buttons. No options for long press or double tap. Anyone know if this option exists?
[Nextbit Robin] /root:
[MENTION=5601531]kushal16[/MENTION]

That wouldn't really be a reason that your speed is being limited.

Most covered bands (2,4,12)under 4G coverage have theoretical download speeds of ~40Mbps, what you are experiencing has nothing to do with the band probably.

You network puts your in the band your area has no matter how much you try if certain band isn't available in your area you cannot switch to a band of your choice it will only make it difficult for you to get any network.

Just because a mobile carrier has certain spectrum doesn't mean they have it all over India, they also have lower or higher frequency bands to make sure their coverage is expanded and as you know in India mobile carriers have spectrum based on regions too.

There are other variables when it comes to data speed. Band has very little to do if you are talking about such low speed limitations.
[Nextbit Robin] kushal16:
I have noticed on my Redmi note 3 which has band 40(2300 Mhz) getting good speeds compared to nextbit robin which was on band 3(1800Mhz) when I had run speedtest. JIO carrier uses this band 3,5 &40 in India.
[Nextbit Robin] DJ_SpaRky:
What does any of this Band 40 talk have to do with this ROM?
[Nextbit Robin] kushal16:
Read post #207. It's clearly mentioned that "out of this thread". Just wanted to know any method to unlock band 40.
[Nextbit Robin] /root:
Not sure if its the ROM issue or hardware/battery issue but device cannot stay ON after battery reaches 20%, it would shut down anytime randomly once it goes below 20%.

Anyone else facing this?

P.S. : Thread title needs to be updated to [October 18th]
[Nextbit Robin] /root:
20th November 2017 Build is up

Download link

Changelog

P.S. : Thread title needs to be updated to [November 20th]
[Nextbit Robin] frap129:
Sorry for dipping on this thread for a bit, had a lot going on with school and work and other devices. My previous attempts to port O failed, but I'm giving it another shot and starting from scratch. While I don't expect anything to be working soon, I'll throw an alpha build up as soon as its semi-working.

EDIT: O now gets to the bootanimation, which is farther than my last attempt.
[Nextbit Robin] frap129:
I know y'all hate teasers, so heres one :p
[Nextbit Robin] xWolf13:
That's crazy! Thanks for working on the device!
[Nextbit Robin] L3R0N:
? That's awesome!!
[Nextbit Robin] frap129:
Right now, WiFi is giving me the most trouble. WiFi, NFC, and Fingerprint are broken, GPS and RIL are untested. Everything else seems to work (including bluetooth and camera). I'll push an alpha build once WiFi is fixed and RIL is tested.
[Nextbit Robin] L3R0N:
I'm officially excited about this. Can't wait to test. So far on the bug list, RIL is the only one I need/make use of. Thanks for your hard work.
[Nextbit Robin] frap129:
Glad I have at least one tester lined up :p. Wifi and NFC are fixed, but RIL and Media are broken, so I'll try to get those fixed tomorrow and get a build up asap. So far I've tested 32 builds in the last two days, lets hope it doesnt take many more.
[Nextbit Robin] VenomMOD:
I am also willing to test the new build. Thank you for putting the time and effort to make an Oreo ROM for this phone :good:
[Nextbit Robin] dirtsky:
Hell I may have to take this phone back from my son and start using it again. :D I'll just let him use my OnePlus2. I'll test if I can pry the thing from him. I'm pretty sure he'll swap with me.
[Nextbit Robin] L3R0N:
32 builds? ? You've got an incredible amount of patience. Thank you for putting this amount of work into getting Oreo on this device.
[Nextbit Robin] double_integral:
Eta?
[Nextbit Robin] xWolf13:
oh no, you're gonna want to take that back..
[Nextbit Robin] double_integral:
I'm new here
[Nextbit Robin] dirtsky:
First rule: NEVER ask for ETA's on any thread.
[Nextbit Robin] googleygoggles:
Honestly, I've always wondered why people felt so strongly about ETA's... I mean, I see how it *could* be considered rude or something, etc, but it has gotten to the point of becoming a crime on XDA to ask, when you just want a general timeframe that could be used to build excitement/support.

Anyways, back on track, I'm willing to test Oreo build too, anything thrown at it to test features, etc. as I have a Robin sitting unused in near perfect condition waiting for some Oreos ;D
[Nextbit Robin] double_integral:
I'm a developer by profession (I'm sure a lot of others here are too). I get asked for etas fairly often. Unless you say put this in my hands on a specific time, I don't see what the issue is. In this forum, I suppose letting 1 person do it opens flood gates so to speak. All in all, my bad and thanks for working on this rom.
[Nextbit Robin] dirtsky:
I agree with you. I mean I've been on these forums for years and that is one of the first rules I learned here on the forums. I'm just warning as I've seen people get seriously hazed for it. And frap I appreciate the development you're doing on this very underrated device.
[Nextbit Robin] googleygoggles:
It seriously is underrated... It's an amazing phone, and I really wish NB didn't basically give up on it. I hear we're gonna get Android 7.1.2 at least.
[Nextbit Robin] dirtsky:
Hopefully. I haven't seen anything from Razer about releasing anything. I mean I know they said they would support this device till February but, who knows.
[Nextbit Robin] googleygoggles:
No it's because a Robin was seen to have an official 7.1.2 build in the wild, but who knows?
[Nextbit Robin] dirtsky:
I hope something comes soon. I like this phone.
[Nextbit Robin] witnit:
I'm hoping we at least get a security and bug fix roll-up. Also, nice to see several people from the Nexus 4 forums are on a Robin. Many thanks to the dev's for supporting it.
[Nextbit Robin] Sparubens:
Anyone else experiencing very slow charging? Like, 1% in half an hour
[Nextbit Robin] marvelljones:
Nope. I can get from 5% to at least 50% in that time. What charger are you using?
[Nextbit Robin] googleygoggles:
Wanna know what's driving me insane? My official NB charger cable now only works reliably in one orientation. It charges almost 1% an hour if I accidentally flip it over and not notice (thanks USB C :P), so I guess just try a new cable...

Just wish Nextbit still sold an official fast charger + cable on their website... They're hard to find online.
[Nextbit Robin] marvelljones:
Funny thing is that I'm using the quick charger that came with my wife's ZTE Axon 7 Mini. She replaced it with an iPhone 8 Plus, so it's my "backup" phone. I never purchased the "official" Nextbit charger because I already had access to a quick charger.
[Nextbit Robin] jabashque:
[MENTION=5051294]frap129[/MENTION] If you don't mind me asking, are you still trying to deal with the RIL with your Oreo ether builds?
[Nextbit Robin] pintasmapila:
[MENTION=5051294]frap129[/MENTION] I've just noticed the camera focuses and takes pictures much faster than any other rom.

Thank you for that :)
[Nextbit Robin] frap129:
Currently I'm trying to get it to boot. Had everything almost working, then 8.1 dropped lol

Glad it works well for you!
[Nextbit Robin] jabashque:
Oh no, back to square one D:

Wish you luck!
[Nextbit Robin] BearOfXDA:
Don't know if its been reported yet but there's an issue with a speaker clicking when you press home, open apps, etc. I have my phone fully muted and on do not disturb, so there shouldn't be noises like that. It's very faint, but noticeable
[Nextbit Robin] C0D3FRE@K:
you might want to disable touch sounds in settings.

but yes I heard the click too very faint wasn't so noticable for me until you mentioned it
[Nextbit Robin] C0D3FRE@K:
bump
[Nextbit Robin] cheezusweezel:
Can we hope for another update or is 14.1 done ?
[Nextbit Robin] rahul200023:
I'm not trying to being rude when i ask this. Will ether see carbon rom in oreo? I love the stability and performance of this rom on nougat and would love it if we could get it on 8.1
[Nextbit Robin] eisenbergw:
I don't even see the Robin listed on their web page any more (https://get.carbonrom.org), so I'm guessing probably not? :confused: :crying:
[Nextbit Robin] Raiz:
You didn't get it , this list correspond to the devices that has already get 8.1 Builds , and [MENTION=5051294]frap129[/MENTION] said :

So the Oreo build is in progress, this is coming, but it takes time.

:good: Be patient :good:
[Nextbit Robin] eisenbergw:
OK, Oreo is nice, but can you point me to the download page for 7.1.2 (which is the title of this thread)?
[Nextbit Robin] /root:
You can follow the link to the 'Archive Page' and select 'Nougat' > ether from their download page here https://get.carbonrom.org/

You will land here https://basketbuild.com/devs/CarbonROM/.OLD/Nougat/ether
[Nextbit Robin] eisenbergw:
Yep, there it is. OK, so the Jan build was the last one for Nougat. No problem.

May I suggest, then, to update the main post at the beginning of the thread so that "Get CarbonROM" takes you to that page instead of an error ( {"code":"ResourceNotFound","message":"/device-ether.html"} ), or maybe use a redirect to the proper page? Unless you're really committed to digging around archives, an error like that would just cause you (ok, me) to just shrug your shoulders and move on to another thread/ROM.

Whether Oreo comes or not, I'm thankful for a stable ROM where bluetooth works reliably. So thanks, [MENTION=5051294]frap129[/MENTION]!
[Nextbit Robin] linckandrea:
I have compiled cr 6.1

the only problem is that:to finish the compilation I had to set the selinux in permessive and use the media-caf repository from lineageos instead of codeaurora

for those who want to try

Download
[Nextbit Robin] rahul200023:
tested the rom, couldnt test volte

Bugs i found:

fp is still active for a few seconds after the device locks

no visual indication the phone is charging not even on the ui, only way to tell is the batter percentage going up

Otherwise this rom is sooo smooth just like its nougat variant, best rom out for this phone right now
[Nextbit Robin] linckandrea:
thanks for the feedback, I did not found the problems you have exposed:eek:

i just compiled a new build with the fp problem fixed

Download

maybe I should create a new thread, I would not go OT ...
[Nextbit Robin] frap129:
I'm talking to some other devs about it. This build uses prebuilt GPS (The same as lineage and omni) so there's no reason that it shouldn't work, and nothing in the log would indicate that it isn't. Pretty stumped on this one
[Nextbit Robin] :
Oh ok I thought GPS would not work at all because you said it is broken. So I never really tried GPS :D
[Nextbit Robin] frap129:
The GPS itself doesn't work, but you can still use location in google maps and other apps as long as you have high accuracy mode enabled
[Nextbit Robin] :
Alright thanks for the clarification. Will switch to Carbon then :)
[Nextbit Robin] mlboss:
phone randomly wouldn't turn on today when I needed it (at a wedding) I tried forced restarting but no luck I had to charge it for a sec then force a reboot for it to come on by then it was too late :/ but everything else works fine
[Nextbit Robin] valhallen.282:
Volume Down + Power did not work?

That's the actual force reboot.
[Nextbit Robin] DECHTECH:
Ah another bug that were found on LOS is here too. After receiving a text message, the notification light came on and stayed on. Can anyone test and confirm?
[Nextbit Robin] :
Same here. The camera is also buggy. I can only take pictures randomly. Most of the time nothing happens when I press the button. It also does not let me focus manually.
[Nextbit Robin] DECHTECH:
Use google camera or another 3rd party camera app for now, as the camera seems to work 95% of the time with google camera.
[Nextbit Robin] frap129:
Confirmed, will look into.

Built in camera works fine for me, on issue I've found that is that shutter is a little slow
[Nextbit Robin] :
Thanks for the advise, google camery works well.

Strange, built-in camera is kinda broke on my device. Maybe I need to redownload/reflash the rom.
[Nextbit Robin] frap129:
Lights bug fixed, GPS might be fixed (gets a lock now, needs more testing to ensure stability), test build should be up later
[Nextbit Robin] happy3777:
I Hav problem with VOLTE i can make calls from non volte sim but volte network as soon as i do a call call ends....
[Nextbit Robin] pintasmapila:
I've actually posted in Carbon ROM Google + page asking for a ROM release for Nextbit.

Couldn't be happier ;)

Thanks. Gonna try it now :P
[Nextbit Robin] frap129:
Logs?

:cool:
[Nextbit Robin] frap129:
Sorry for going MIA for a sec, been working on some stuff you all might like...
[Nextbit Robin] DECHTECH:
Take all the time you need. I'd rather wait for large, awesome changes anyway! :)
[Nextbit Robin] sykomaniac:
Yep definitely looking forward to a custom kernel!
[Nextbit Robin] frap129:
Huuuuge updates

The latest build of Carbon contains full EAS support via the Vox Populi power HAL courtesy of [MENTION=6745491]joshuous[/MENTION] and my port of EAS to the kernel (based on Googles bullhead tree with some upstreaming from op3 thanks to [MENTION=5438598]RenderBroken[/MENTION]).

What EAS is:

Energy Aware Scheduling (EAS) is an enhancement to Linux power management, unifying CPU power control under the Linux kernel. EAS extends the Linux kernel scheduler to make it fully aware of the power/performance capabilities of the CPUs in the system, to optimize energy consumption for advanced multi-core SoCs including big.LITTLE. With EAS, the Linux kernel will use the task load and a CPU ‘Energy Model’ to control task placement to select the optimal CPU to run on.

tl;dr: EAS chooses CPU frequencies based on power consumption and scheduler input rather than estimated CPU Load, resulting in better battery life.

From my own testing (kernel part the last 2 days, ROM part the last few hours) this is completely stable and results in lower idle drain as well as lower temperatures.

I hope you all enjoy it. Please report back on stability, battery life, and performance.

Get CarbonROM
[Nextbit Robin] sykomaniac:
Any chance we can have just a boot image please.
[Nextbit Robin] frap129:
You could extract the bootimage from the ROM zip, however, I plan on releasing a custom kernel that should get everything up and running in a week or so
[Nextbit Robin] sykomaniac:
Haha I know I could but I'm lazy and was off to bed. I'll sit tight and wait for the standalone release.
[Nextbit Robin] frap129:
EAS Fixes

This test build contains some fixes for EAS, as I'm continuing to port the Vox Populi power HAL to ether. Also, this build fixes a bug where big cores we're getting stuck on the performance governor, so battery life should be much improved in this build

Get the latest build here
[Nextbit Robin] L3R0N:
Thanks for this. I'm new to the Robin and have mostly been using stock but decided to try carbon out and the battery life is great. I came here to report that the big cores are stuck on the performance governor even after changing it it'd go back to performance. But it seems you're way ahead of me and fixed it already.

Edit: with the new update, battery is even better. And the best part is that battery life is good without sacrificing performance.
[Nextbit Robin] frap129:
Expect future updates to further improve both, since much of the power HAL is still intended for the Snapdragon 820
[Nextbit Robin] L3R0N:
Looking forward to those. I tried Lineage but the battery life wasn't the same as Stock (didn't really expect the same battery life but something close to), tried AOSPA and it was good but setup crashed when setting a fingerprint. Now I'm on Carbon and I think I'm gonna stick with it for the long run. Thanks for the great ROM. According to the benchmarks of other ROMs posted here its not so good performance wise but it performs well enough for me. Keep up the good work.
[Nextbit Robin] L3R0N:
[MENTION=5051294]frap129[/MENTION] I found a bug. When the screen is off for a while and you turn it on, the fingerprint scanner doesn't work. It says "fingerprint hardware not available". To fix I turn off the screen and turn it back on and all goes well. Will see about getting a log later on.
[Nextbit Robin] frap129:
I haven't experienced this, but if you grab a log please post it so I can look it over
[Nextbit Robin] DECHTECH:
Having issues with NFC, attempting toggle on does nothing. Got log attached.
[Nextbit Robin] frap129:
Can't reproduce, works fine for me. Could you send the full logcat? Neither of those contain NFC toggle stuff
[Nextbit Robin] L3R0N:
Clean flash of the July 29 build seems to have fixed it. Will surely send a log if it starts happening again.
[Nextbit Robin] anupritaisno1:
If allowed to ask, where's the kernel source even?
[Nextbit Robin] frap129:
Check the first post
[Nextbit Robin] hairycheez:
I am having the same problem

I've clean flashed the July 29 build and still can't get NFC to work.

Other than that ROM has been awesome. Battery lasts all day so can actually use my phone.
[Nextbit Robin] L3R0N:
I was referring to an issue I was having with the fingerprint scanner when waking the phone from sleep. I have no problems with NFC...mine turns on fine.
[Nextbit Robin] frap129:
I'll look into the NFC issue. Glad you like the ROM, more battery life improvements coming in the next build :p

Same here, which is why I find this bug odd. Could be a firmware issue
[Nextbit Robin] hairycheez:
First I had AOSPA but since GPS wasn't working I clean flashed to Carbon. Since NFC didn't work I tried restoring my phone to stock using the official N108 image and flash-all command and reinstalling the 7/29 build but no difference.
[Nextbit Robin] valhallen.282:
Flash all in stock image does not work correctly. There is another way to do it. Check my signature.

Good work on Carbon frap. Sadly my Robin was in a really bad shape so I swapped it out for a Zuk Z2Plus. Maybe I'll chew your brain on how to build this for that device. I've been meaning to get my hands dirty a while now.
[Nextbit Robin] frap129:
Z2Plus has an SD820 CPU, so it shouldn't be hard to port if you have very basic git+code knowledge. Feel free to PM me :p
[Nextbit Robin] nydmt:
Tried AOSPA, Omni, but this ROM looks promising. Clean flashed yesterday, I can confirm that my NFC toggle is stuck off. Not really an issue for me because I don't use it. This ROM looks good, will test it out over the next week. Btw, does anyone else get that second long flicker right when you wake your device up? It kind of looks like that grey and black static noise you'd see on a TV. I've seen it on other ROMs too, only for this phone though. Not a huge issue, just wondering if there's someway to get rid of it.
[Nextbit Robin] :
When I turn on 'Use custom header image' in Settings --> CarbonFibers --> Status bar --> Header, SystemUI crashes. Because of that I had to wipe data twice.

And the NFC toggle problem is here too.

Everything else works fine for me. And battery life is very good.

Also I would really like an option to use animated back LEDs for notifications. Is it possible? :)
[Nextbit Robin] DECHTECH:
Can confirm that attempting to use the Custom Header Images causes SystemUI to crash and die, needing a data reset to fix it.

I'm going to flash N108 official the "working" way now to see if I can get NFC working on carbon, will report back later.
[Nextbit Robin] frap129:
Header crash will be fixed, I know the exact change that broke it. NFC is currently being looked in to.
[Nextbit Robin] AnierinB:
E.A.S on the robin? What a dream come true!!
[Nextbit Robin] valhallen.282:
Turns out the guy who took my Robin has no idea how to use it. Seems I'll be back to the Robin very soon! Bye bye Z2PLUS
[Nextbit Robin] ron580:
battery life is awesome on this rom. thanks!
[Nextbit Robin] alexnikone:
how much sot hours?
[Nextbit Robin] Knospi:
I get 46000 points in Antutu, not as much as LineageOS or Omni, but I guess since It's in testing, I can't complain much.

As for Battery Life, even after recalibrating, I don't really feel the SOT Difference, but Standby is amazing.

Looking forward to seeing what the Rom will be like, when It's fully finished.
[Nextbit Robin] frap129:
Glad you like it!

Don't ask that. SOT is an extremely unreliable stat to gauge battery life with

I'm quite confused by the benchmarks. In real world performance, its on par with omni, yet benchmarks terribly. Glad that battery life is somewhat improved for you, even if its only in standby.
[Nextbit Robin] Knospi:
Antother Question I have:

Is it normal that only the 4 Cortex A53 Cores are Active ? Core 5&6 are always sleeping, is what CPU-Z says..
[Nextbit Robin] frap129:
They tend to stay at very lo frequencies. Check kernel adiutor to see if they're actually online or not
[Nextbit Robin] L3R0N:
You're right. The benchmarks are confusing. I tired crDroid which benchmarks at around 68000 and this ROM (Carbon) is way smoother. App launches are faster and overall performance is better. So benchmarks don't really tell the complete story here.
[Nextbit Robin] hairycheez:
Is there a way to add a shortcut to the File Explorer to the app drawer? Seems to be missing
[Nextbit Robin] AnierinB:
Can confirm that file manager Is not accessible from downloads app
[Nextbit Robin] frap129:
There is no built in file manager. We are currently working on a custom solution for Carbon. For now, download one from the play store.