yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] Sparubens:
Posted this in other thread aswell:

I tried all ROM's as I received my Robin a couple of days ago. All CM-based ROM's (+ Carbon, AOSP based) have the "static display" bug (when you turn on the screen you see for a split second a static image like in TWRP), AOSPA has the audio stutter bug when playing sound through the speakers, Omni has the screen flicker bug (fixed by flashing 2/07 boot.img)...

I don't count on AOSPA fixing the audio bug as it's already present since MM for the Nextbit (just read that bug in an MM thread), and CM-based ROM's have the static bug since the beginning, and still not fixed..

I don't count on any bug fixed by CM or AOSPA as the Nextbit is a niche device, guess I'll have to settle with Omni, but I don't like the adaptive brightness icon next to the brightness slider, you can't turn it off sadly.

Here's an image: http://imgur.com/yFOf6q2

If anyone knows a way to turn it off (substratum theme maybe? any solution is welcome) let me know.

**If you flash the boot.img for Omni, Omni seems to be the only bug free ROM atm, as all the other ROM's bugs can't be fixed atm by the user. I hope I helped you guys out, because I've wasted so much time trying ROM's only to run into a bug after setting it up, so only Omni ROM is fully functional atm**

Good work [MENTION=3878813]Gandalf[/MENTION], you seem to have made the only fully working ROM. Only request would be a toggle to remove the adaptive brightness icon, but I don't think you are supposed to do that as you only provide the ROM to our device without any "in system tweaks" made by you. Also, substratum is not working in the latest build, overlay problem, even after reinstall.

EDIT: I can install substratum themes with latest boot.img. However, YouTube stops playing videos when pausing a video in fullscreen for more then 3 seconds. App is frozen until you exit it. In 02/7 boot.img this bug isn't present, but you can't install themes with that boot.img.
[Nextbit Robin] jericho777c:
Does anyone happen the have a link to the July 2nd build? It looks like the download website has been down since at least yesterday and still can't access it today. Thanks
[Nextbit Robin] kuduku:
Can anyone please upload July 02 boot.img . Dont want to download full july 02 ROM for that
[Nextbit Robin] Luv-Kush:
Tried to flash boot.img in twrp in boot section but goes into boot loop am I doing something wrong. Help please.
[Nextbit Robin] Sparubens:
Yeah do it in fastboot mode, open PC and enter in a cmd windows "fastboot -i 0x2c3f flash boot boot.img"
[Nextbit Robin] Luv-Kush:
Here is what im doing clean install july 30 rom then fastboot boot.img and it goes in boot for ever. My boot.img is 13,408kb may be that is the problem. steps would help if you can.
[Nextbit Robin] pintasmapila:
Well, I flashed boot with twrp.

First I flashed the latest rom, then I selected 'flash image', then I chose boot.img and chose boot. That's it. It worked perfectly.

You can also flash a stock rom first to be sure everything is ok.
[Nextbit Robin] Flak:
July 30th build + July 2nd boot image = theme engine errors and bluetooth devices not auto connecting for me. But at least it stops the random screen blanking. Any word on the screen blanking being fixed?
[Nextbit Robin] valhallen.282:
I'd suggest staying on the last known fully functioning build. If you follow Gandalf's github you'll know there are a LOT of upgrades coming. But they're gonna take time as with most good things.
[Nextbit Robin] rahul200023:
will the black screen bug be gone in future builds, i am a bit new to this device and dont feel comfortable flashing the boot.img yet
[Nextbit Robin] valhallen.282:
Unfortunately only time will tell. Debugging and finding the source of the problem is one thing but fixing it in a way that it doesn't mess with any other device especially on widely supported ROMs like Omni are another thing.

In short only time will tell.
[Nextbit Robin] Sparubens:
No weekly this week?
[Nextbit Robin] valhallen.282:
Doesn't seem like it. Seems real life has caught our maintainer in a Tight grip. Don't see posts on GitHub. In all probability he's stuck with work and hasn't had time. Knowing him; he doesn't want to push out another broken build.
[Nextbit Robin] sqkid89:
Just saw a OTA update, anyone give it a shot yet?
[Nextbit Robin] Gandalf:
Fixed.

Can someone check fingerprint on new build? My device may be broken.
[Nextbit Robin] Sparubens:
Flashed over 30/06 build. Fingerprint works fine.
[Nextbit Robin] WoodenMind:
Did OTA update from 7/30 (with old boot.img), fingerprint working fine.
[Nextbit Robin] pintasmapila:
Flashed over 07/30, everything is working perfectly so far. No more problems with substratum.

Any big changes?
[Nextbit Robin] ytsejam1138:
Fingerprint also works on mine with the new 8/10 build.
[Nextbit Robin] Gandalf:
Darn, I need to RMA my device then. My fingerprint sensor is broken.

I have a new kernel I'm going to ship soon, it's just the bare minimum OEM changes for everything to function, no other superfluous changes in there. I'm also going to start going down the CVE list and get it completely up to date on that as well.
[Nextbit Robin] WoodenMind:
Before anyone asks, this week's build (8/13) is running great. Check out the new built-in theming at Settings - Style.
[Nextbit Robin] FlamieFox:
Nextbit stopped all warranties on the 31st of July. I have to send mine too (have a weird patch of overlit pixels at the bottom of the screen) but only because I opened the rma request before the 31st.

You can still find them on amazon though. Here in Italy it costs 120€ for a new one on amazon.
[Nextbit Robin] Tautvydas:
Is the blinking dark screen issue fixed?
[Nextbit Robin] :
Is the minimum volume for calls still quite high in the current build(s)?
[Nextbit Robin] Tautvydas:
Excellent job, thank you!
[Nextbit Robin] enterflux:
Thank you for all your hard work on this! It's a great daily driver.
[Nextbit Robin] aoleg:
NFC is still not working in the latest build. One can't even turn it on from the quick tile.
[Nextbit Robin] xWolf13:
Yup, I'm having the same issue here
[Nextbit Robin] nydmt:
NFC not working. Also, just a minor annoyance, why is the battery icon smaller than the rest of the quick settings toggles?

Log attached.
[Nextbit Robin] Gandalf:
Ok, I'll check NFC today. I thought it was working. I have a new kernel anyway, it is just bare minimum OEM changes for hardware functionality on the latest CAF kernel. I'm also going to bring in all CVE changes to harden it a bit.
[Nextbit Robin] pintasmapila:
My stereo is gone. Only the top speaker is working. :(
[Nextbit Robin] Gandalf:
Works fine for me on latest weekly. Make sure it's not a hardware issue.
[Nextbit Robin] :
I mentioned this already in the thread and I don't want to be annoying but how do you guys have phone calls when the min. volume is so loud? I literally have to hold the phone like 10cm away from my ear because even the min. volume is as loud as the max volume on stock or other roms. I really like omni but so far I haven't found a way to adjust the volume and to lower it with the hardware keys is just not possible.
[Nextbit Robin] aoleg:
NFC not working on the latest weekly. Had to flash July kernel to make it work.
[Nextbit Robin] pintasmapila:
Oh boy. It appears you are right. I've tried stock rom and its not working either.

Is there an easy way to test it?
[Nextbit Robin] gr3y_:
As said before, I have the same issue. Hoping for a fix someday.
[Nextbit Robin] :
Would be strange if we were the only people with this problem :)
[Nextbit Robin] rahul200023:
I know this is extremely early, but when do you think we will see a working build of android oreo (january or feb maybe?)
[Nextbit Robin] Gandalf:
When it is ready. And this is the only time I will answer that question. Source just went up today. Still need to wait for CAF to go up before we can do anything.
[Nextbit Robin] rahul200023:
Also do you think 3rd party development for the robin will stay alive through oreo?
[Nextbit Robin] ipowyourface:
Yeah looks like it. I came from another ROM and it was working. I flashed stock to make sure and it works there as well. Using the newest build the NFC toggle won't stay on.
[Nextbit Robin] Gandalf:
I'll fix it with the new kernel.
[Nextbit Robin] Dishe:
Call volume hasn't been an issue for me, but I'm usually using my phone in noisy environments so I always found stock volume too low. NFC is not working and that's actually annoying because I use it at work with my Sony camera to send samples to social media.

One thing I don't see mentioned is the charging LEDs. I use them to determine if my charger gets unplugged. This morning I woke up to a dead phone that I thought was charging all night. The led on the bottom which lights up on the stock ROM for notification and charging only lights up for notification now. The lights on the back turn on with the charger at first, then it seems to time out and shut off.

Otherwise super happy with the ROM!
[Nextbit Robin] Gandalf:
Noted.

All focus is on Oreo now
[Nextbit Robin] Shattermatter:
Seems like there's a problem while downloading the newest version. OTA Updater can't download the newest version "omni-7.1.2-20170827-ether-WEEKLY.zip". Any changelog available?
[Nextbit Robin] WoodenMind:
No problem updating to 8/27 via OTA here. You can use the gerrit to see changes for this week, nothing specific for ether as far as I know. Can you download the full zip from DL.omnirom.org?
[Nextbit Robin] Shattermatter:
Yes, download from website is working. I guess I'll try updating manually with TWRP. Do I need to wipe cache / dalvik cache or reinstall Gapps?
[Nextbit Robin] WoodenMind:
No, dirty flash should be fine. You only need to reinstall gapps if you wipe the system partition.
[Nextbit Robin] JaN0h4ck:
Is anyone else having trouble with the Google App?

When I try to access my feed the app stops working for ≈20 secs and then it works fine. Same thing happens when I switch back into the app from an amp.
[Nextbit Robin] AnierinB:
So when I first got my Robin I was using omni for quite sometime and then when AICP became official I switched. When I returned to omni ROM (after full wipe) my device would boot loop, shut off, then boot fully. I just recently got a new robin for myself and I noticed it did the same thing.

Now I'm gonna try my best to get a log of it but I wanted to know if anyone is experiencing it as well? I really like this ROM (especially because of their built in substratum interface) it's just that bug for me.
[Nextbit Robin] Gandalf:
Go into recovery after the reboot and get /sys/fs/pstore/console-ramoops
[Nextbit Robin] AnierinB:
When I'm off work I'll reflash both of my devices to omni and post the file you mentioned from them after the bootloop occurs. Thanks for the response!

Edit: flashed both devices with the same exact setup and gapps package but haven't experienced it at all yet. I'll update this with the logs if it happens to occur.
[Nextbit Robin] jabashque:
Out of curiosity, Gandalf, has your device's fingerprint sensor been repaired yet?
[Nextbit Robin] Gandalf:
Somehow it magically started working again after leaving the device off for a day or two. WEIRD
[Nextbit Robin] dodbanz:
I have solved the signal issue. Developers are half right in that their work did not create the issue. However some developers have boldly said it's just reporting , this is not true at all. The issue happens when any dialer is installed with gapps. It switches your preferred network type in dialer test mode or better know as engineering mode. The other thing to remember is Android doses signal. i

In this case after the fix reporting is correct. Android now doses radio power to conserve power aggressively. So seeing it move after the fix is normal don't freak out it's a good thing. I have TMobile and had the persistent issue data drops out completely no signal bars no lte etc no network data state disconnected. First check your apn settings and make sure the are 100 percent right for you carrier. Make sure enhaced lte is enabled. Network preference is lte. Next open your dialer and punch in this code you do not need to hit send. *#*#4636#*#* A screen pops up it says testing on top with a gear icon. Click on the phone information tab . A new window opens scroll to set preferred network type . Chances are it's on some random network type no mater what rom I have installed this was always wrong as it's not stored in the rom. Select LTE/WCDMA. You need to wait a few seconds as your meter goes out and lte drops completely. When it comes back up you will see on the phone information screen that lte is voice network type and lte is data network type. Hit ping test ipv4 and ipv6 and http client test will show pass exit the screen square key swipe app closed. In this testing mode you will see signal db matches stock but the signal bars will not again normal the signal is dosed when background processing and up front processing stops i.e opening an app that uses data. Speed test this mode you won't be dissapointed. Fun fact I noticed WCDMA only is hspa which was perfect signal bars on indicator but after speed test results you would clearly see why you set lte/WCDMA. I think Robin's indicator as well as others show the WCDMA only in the signal bars with data as lte label which may be why we see full signal all the time. Any how this should fix actual preformance issues on gsm networks. Reporting could be tweaked but this is the right mode.
[Nextbit Robin] rahul200023:
any update on the progress of android oreo?
[Nextbit Robin] WoodenMind:
Follow the gerrit or Google plus group. Apparently they have some devices booting so far, but doesn't look like any work has begun specifically on the Robin yet.
[Nextbit Robin] rahul200023:
everything i found on gerrit from the robin seemed outdated with the latest update being in july, thats why i asked on the forum
[Nextbit Robin] jabashque:
I've noticed that there haven't been any new weekly builds for ether since 8/27. Anyone know what's going on? I'm a bit worried about support for ether being dropped.

EDIT: Just realized only a few devices got a 9/3 build, and that none of them got anything this week. Is there something going on with the OmniRom project as a whole?
[Nextbit Robin] WoodenMind:
Yes, they're working on Oreo. No new development for Nougat so I guess they stopped the automatic weekly builds for it since there wouldn't be any changes anyway.
[Nextbit Robin] FlamieFox:
They have focused all work onto Oreo. I guess we won't see anything new until October at the very least.

The 27/8 rom works perfectly though so you can use that without problems.

ps: doh! Using the phone app and didn't see you already got an answer. Sorry ^^
[Nextbit Robin] jabashque:
Hm... I was hoping Gandalf would've been able to push out his updated kernel with the NFC fix. Ah well, guess we'll have to wait in that case.

(I have another issue with the WiFi suddenly displaying an old list of visible networks and me not being able to connect to any network or even turn off the WiFi, but they've all happened when I wasn't near a computer to dump the logcat + dmesg. Hopefully I can get that posted soon once it actually happens while I'm near my computer.)
[Nextbit Robin] bmccoy11:
I was also experiencing the same issue here myself when I was travelling, haven't noticed it recently (now that I have a computer to dump log messages to, go figure)

Other than that, I've also had to reboot my phone at least once a day to clear out some kind of memory leak - when I leave my phone running for a day or so, Android System takes up 1.5-1.9GBs of my RAM and leaves barely nothing for apps, so all apps running in the background end up closing and apps in the foreground get laggy as heck. Oh well, even despite that, OmniROM still runs much faster than Paranoid Android and Nextbit's OS in my experience.
[Nextbit Robin] DerHoggz:
Needs a Blueborne patch.

https://youtu.be/LLNtZKpL0P8
[Nextbit Robin] giraffelol:
Yes please. I use Android Wear daily.
[Nextbit Robin] WoodenMind:
Announcement on Google+: 7.1 with September security patches will be released in a few days.
[Nextbit Robin] rahul200023:
are we going to be seeing oreo development soon, i have noticed that weekly builds for ether roms have been becoming less frequent, is this because of beta testing for oreo?
[Nextbit Robin] hobbit19:
pls

make final firmware . error correction for 7.1
[Nextbit Robin] jabashque:
Would there be any chance that we'd be able to get an update for 7.1.2 with the BlueBourne-related exploits patched for the Robin? I'm not sure if it's being delayed because you have real life burdens you have to deal with (if so, I wish you luck).
[Nextbit Robin] xBane_:
Its been delayed because all omnirom development has moved over to Oreo.
[Nextbit Robin] AnierinB:
delete
[Nextbit Robin] clu1688:
Remove Persistent Google Search bar

Hi All, I just switched from Stock to Omni yesterday and really like it. Previously I was using Nova Launcher prime on stock ROM with root.

I am not very familiar with Omni ROM, and searched in this forum to find a way to remove the persistent Google search bar on the home screen, so far there was one post, but no answer.

With Nova you can choose to hide the Google bar.

I usually put my favorite widget on the top space of my default home screen, and this Google search bar is now in the way,

ANy suggestion is greatly appreciated,

EDIT: I installed pico Gapps so there is no Google App to remove.

EDIT #2: Found it, and fixed. Press and hold on home screen, choose "Setting" there is an option to turn it off.
[Nextbit Robin] cmb6:
I recommend that you use Nova Launcher with OmniROM
[Nextbit Robin] gr3y_:
Does anybody know why there's no HDR setting in Google Camera when installed on Omni? Any way to enable it? Not talking about HDR+, just normal HDR.
[Nextbit Robin] rahul200023:
Any update on oreo?
[Nextbit Robin] Gandalf:
I'm going to start working on it Monday
[Nextbit Robin] pablomancera:
There is no way of supporting vulkan api, right?
[Nextbit Robin] DECHTECH:
Unfortunately, there isn't Vulkan support on the SD808.

AFAIK the A530 GPU on the SD820 was the first Qualcomm GPU to support Vulkan.
[Nextbit Robin] pablomancera:
I can't listen my flac music, neither from Phonograph nor Google Play Music :(
[Nextbit Robin] marvelljones:
Google Play Music converts flac to MP3. Maybe there's a problem with the conversion. I don't use Phonograph, so my best advice is to try VLC (free) or PowerAmp (3.99 last I checked).
[Nextbit Robin] pablomancera:
Yep, is working with VLC, many thanks :)
[Nextbit Robin] bdeals:
Yay thats exciting. I see that Nexus 5x release seems to be working well.

Hope the same for Robin.

Thanks! Looking forward to it
[Nextbit Robin] modestos:
So is there a kernel with NFC support?
[Nextbit Robin] bmccoy11:
I just went back to the kernel from several months back, before the screen/NFC problems came along (sometime around late June), and it's working with the latest build without issues. Be warned that since that kernel is several months out of date, it will probably be far behind on security patches.
[Nextbit Robin] Gandalf:
Halfway there with oreo :good:
[Nextbit Robin] dcarter:
Thank you for your work. 2 questions. Can I support you with a bit of a donation and can I help beta test a pre build for you?

p.s. I CAD designed an awesome nextbit Robin case and can share the .stl if anyone is interested and able to 3D print.

DC

edit gifted you ad free....did it work?
[Nextbit Robin] bmccoy11:
I'd love to check out your model! Hit me up or maybe post it in the Robin Accessories section.
[Nextbit Robin] Gandalf:
I don't see anything on PayPal, but I forward any donations I receive to the Omni server infrastructure. Thank you!

Can you post pictures of your case, that sounds AWESOME
[Nextbit Robin] dcarter:
check accessories section ;)

DC
[Nextbit Robin] jabashque:
To anyone who was following community development for ether back when Android Nougat was the hot new thing: how stable was OmniROM 7.0 for daily usage back when Nexbit hadn't released their stock 7.0 firmware? Based from previous post history, I saw that the LineageOS maintainers ran into bug after bug trying to get CM/LOS 14/14.1 running back when they were using the Marshmallow sources before they eventually gave up and restarted from the stock Nougat sources instead. However, for OmniROM, I didn't see as many issues; for example, Gandalf was able to get the big cores in the SD808 working when other rom maintainers struggled.

But I'd like to ask for people's personal experiences. Reading can only tell me so much when I'm missing the context of how long people had to wait for certain fixes and such.
[Nextbit Robin] substanceneil:
[MENTION=8079424]jabashque[/MENTION]

Omni was solid back then. Nearly perfect, although I cannot recall exactly what the imperfections were. I never was able to get Android Pay working with Omni back then. And there was a bug with wifi-tethering for a bit.
[Nextbit Robin] sketchman16:
Shapeways, might be an option.
[Nextbit Robin] substanceneil:
[MENTION=5637619]bmccoy11[/MENTION] or others: do you have a sense of which security updates are rolled into the kernel vs into the non-kernel software? For example, if I were to flash the most recent Omni, then then flash the kernel from a June build to restore NFC, will the KRACK patches released recently be rolled back? It is hard for me to tell from the changelogs which changes are in the kernel vs not.
[Nextbit Robin] jabashque:
If you look at the changelog for 20171018 at https://omni.cmxlog.com/7.1/ether/, you'll see that all the KRACK related fixes were for android_external_wpa_supplicant_8. wpa_supplicant is a userland application--it's not part of the kernel. As such, you will still have KRACK patches if you were to roll back the kernel.

Now, I'm not sure about Blueborne. I know that for LineageOS, they fixed the vulns by patching the kernel itself for each device. For OmniROM, i think (?) that they patched it on the userland side instead? At least if https://gerrit.omnirom.org/#/q/project:android_system_bt is anything to go by. I don't see any bluetooth-related patches for OmniROM's ether kernel.
[Nextbit Robin] Gandalf:
#progress
[Nextbit Robin] bdeals:
:good::fingers-crossed: Much Appreciated update!
[Nextbit Robin] modestos:
Is this a cookie??! :)
[Nextbit Robin] Gandalf:
Yup! Lots of fixing to do but it's moving quickly now
[Nextbit Robin] Jacobwitt:
Wowza, Thats lookin great!

Too bad I sold my Robin for a Pixel I would have def wanted to see where this was headed!

Luckily I sold it to a close mate so I should be able to flash it on his phone when you drop it!

:D
[Nextbit Robin] modestos:
Super sweet!
[Nextbit Robin] muhrizky:
Donation send with confirmation number 28K049092H252590E
[Nextbit Robin] boxes:
What kind of screen on time are people getting on the latest releases? Also, what settings are you using?
[Nextbit Robin] tlxxxsracer:
PM me if you need an extra tester for bugs. Robin is still running strong. Once stable I can make a video directing viewers to your work.

Congrats on the progess!
[Nextbit Robin] sketchman16:
Just clean flashed 11/20 an hour ago. Opened a CPU app to see cores 5 and 6 are working. In LOS they were not even with the latest builds. So, that's awesome. I'll report on SOT and whatnot as I use it some more.

Would be nice to have a bit more of the customization from LOS, but xposed and gravitybox took care of most of what I was missing, and then some.

I'll update in a few days.
[Nextbit Robin] DECHTECH:
In LOS the big cores are only enabled when heavy load is present to save battery...
[Nextbit Robin] sketchman16:
Ahh. I kinda thought that might be why. But I didn't know.

I'm not sure how good this is. I was using GPS nearly the whole time and hotspot for my tablet for probably 2 hours.

3 hours SOT @ 13%
[Nextbit Robin] Tautvydas:
Hey guys, ran into quite small but tricky problem:

Was messing around with the lock screen options, and did set some random colour on time and date.

I want to go back to 7.1.2 default colour, could anybody, who haven't played with this setting, give me the FF code for it?

Did some research on google, haven't found anything.

Thank you.
[Nextbit Robin] double_integral:
#ff69b4