yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] Lucy66:
I found this, try and check:

"When I did this I found that USB tethering was already unchecked. So I unplugged my phone and got the tethering error again. Then I plugged it in again, went to mass storage mode and went back into settings and checked the USB tethering box. It then displayed "tethered". So I went to the browser to see if there was any change with the connection, didn't seem any different, so I unplugged the USB cable and to my surprise there was no error! I plugged it in again, went to USB tethering and saw it was unchecked again. Unplugged the phone and still no error."

It seems all you need to do is enable USB tethering once to fix this problem
[Nextbit Robin] bilool:
Thanks Lucy66 for the trick but I went back on the omni-8.1.0-20180527.

Other subject : my nexbit's screen don't stay awake on charge however I activated it in the developper's option... If you can fix it too ^^
[Nextbit Robin] the_bastl:
Is it possible just to flash the last nightly/weekly or should i have had a backup?
[Nextbit Robin] dr_vaice:
Bear with me please

First off special thanks to all the hard working developers that make this possible, I have a question might be a bit silly

In order to settle an argument- iPhone 6s vs nextbit Robin on Omni room Oreo, I'm asking you the all knowing developers, I do apologize if this is unorthodox or controversial.

But performance and battery wise which is the better device
[Nextbit Robin] Gandalf:
My fingerprint sensor works again.

Flash M factory images, then custom recovery, then custom ROM. Everything works just fine for me now.
[Nextbit Robin] joeminati:
Any one of you also getting a error when flash 5/29 :

qualcomm.qti.tetherservice
[Nextbit Robin] iluvatrix:
nope didnt work for me
[Nextbit Robin] wpost:
Sadly, that wasn't an option for me: the error message popup would respawn too quickly to allow me to do anything at all. What I had to do was roll back to the known good 20180520 weekly. There might be a better way, but for the sake of other newbies here's how I did that:

Download the 20180520 weekly from http://dl.omnirom.org/ether/.

Turn off the phone by simultaneously long pressing the volume down and power buttons. Given the error message popup getting in the way, this was the hardest part of the process.

Connect the phone to the computer. Depress the volume down button, then press the power button. That booted the phone into TWRP.

Go to Advanced - ADB Sideload. Do not clear the caches, just swipe to initiate a sideload. The following command on my computer worked for me; you will need to adjust them depending upon your computer's OS, where you have ADB installed, what you downloaded, and where:

bin/platform-tools/adb sideload Downloads/omni-8.1.0-20180520-ether-WEEKLY.zip

In TWRP, confirm the sideload ended with a success message. Press Reboot System and you're done.
[Nextbit Robin] cutederf:
Random reboot on 05292018. Noticed battery drain. Will do a clean install as soon as I get home. At work. Thanks in advance. Also getting cookies
[Nextbit Robin] Gandalf:
Sorry, had a small issue.

This build can be dirty-flashed over official weeklies. I tested everything, everything works. If you have problems, do a clean install.

Also, this has cpusets disabled so it should run nicely.

https://www.androidfilehost.com/?fid=962339331458995319

You can, of course, wait until the official build posts on Saturday night, or download and flash this now
[Nextbit Robin] cutederf:
Thank you some much. Will keep you posted. Dirty flash
[Nextbit Robin] Gandalf:
VoLTE worked for me on US AT&T
[Nextbit Robin] cutederf:
It worked for me on MetroPCS us. On 05292018. Haven't tried 05302018
[Nextbit Robin] Lucy66:
I didn't understand what's Flash M factory images...can u be a bit specific
[Nextbit Robin] Gandalf:
Flash the Marshmallow (6.0.1) factory images..

Awesome. Definitely update.

Please try the build I posted just above. It works just fine for me with wired headphones. Thanks.
[Nextbit Robin] Lucy66:
is it mandatory to go back to marshmallow and getting back to latest build?
[Nextbit Robin] Gandalf:
no.. I only had to because my fingerprint sensor was broken.
[Nextbit Robin] Lucy66:
i flashed the latest one...everything is fine...headphone jack working fine...just one last thing....earlier we used to get a persistent notification when we turn on VoLTE.."your device is HD capable"...is it removed or broken for me? my carrier is JIO..I can make calls or texts only through VoLTE enabled...and now it is enabled but still couldnt place or receive calls
[Nextbit Robin] AnierinB:
Can't wait to flash this! Just got my dev Robin back from Javelinanddart and I've been looking forward to testing these builds out! Also, Is sig spoofing present in omni 8.1?
[Nextbit Robin] Gandalf:
Yes, spoofing is enabled
[Nextbit Robin] yumengley:
since the last OTA my PC does not recognize the cell phone
[Nextbit Robin] Lucy66:
Can we edit CSC file to get the VoLTE icon and make calls through dialer instead of Jio4g voice app?
[Nextbit Robin] iluvatrix:
Using the 30/5 build. The time in the upper bar does not update.

Any ideas?

Thanks
[Nextbit Robin] shihjay2:
Tethering

For some reason with the 30/5 build, USB or Wifi Tethering on T-Mobile did not initially work; however, removing all T-Mobile APNs with the exception of T-Mobile US Data (fast.t-mobile.com) and T-Mobile US Tethering (pcbweb.tmobile.com - which could not be deleted) fixed the issue. Just wanted to help others that might have encountered some issues with this. Otherwise the 30/5 build has been working great and VoLTE and calls are all working properly. Thanks, Galdalf!
[Nextbit Robin] Gandalf:
Hm, check the T-Mobile website. They have the current recommended APNs, make sure that's what is on the device. I'll check later and update our APN list if necessary

Since we're not on carrier firmware they can't tell how our data is being used eg. Device or tethering

Tethering/hotspot on unprovisioned devices was one of the initial pushes for custom ROMs years ago ?
[Nextbit Robin] shihjay2:
What worked were the instructions here (since I'm a new user I can't post any links), Google BYOD T-Mobile data & APN settings

Default with the ROM shows the APN type to be default,supl, hiipri, mms whereas the recommended is default,supl,mms is needed for tethering to work

Default with the ROM shows the APN protocol to be IPv6, whereas the recommended is IPv4/IPv6 for tethering to work.

Default with the ROM shows T-Mobile (IMS) and T-Mobile MMS EPDG which both need to be removed (even though they are not selected) to also make tethering work.

Hope that helps.
[Nextbit Robin] jericho7:
I'm also having issues with the Google Camera crashing, Open Camera and other camera apps not based on Google's work fine. I tried looking at the log for potential causes and this message seems to be the most relevant:

mm-camera: sensor_laser_init:117 Failure opening sensor library! Error: dlopen failed: library "/system/lib/hw/sensors.hal.tof.so" not found
[Nextbit Robin] Gandalf:
That log line is harmless. Please get a full log
[Nextbit Robin] cutederf:
Everything is going great. Bluetooth is a little choppy. But it could be my cheap jlab rewind headphones? Thanks in advance

Samsung Galaxy Tab 2*

T-Mobile Samsung Galaxy S4

Huawei Ascend Mate 7*

T-Mobile Samsung Galaxy Note 4
[Nextbit Robin] Gandalf:
Please provide logs with bug reports

Guys I'm going to ignore all bug reports unless you provide a logcat and dmesg. Guide in my signature.
[Nextbit Robin] Gandalf:
Are you using 2 or 3 wire headphones (do they have a microphone) ?
[Nextbit Robin] Gandalf:
I tested a wired headset with a mic. I'm leaving work shortly so I'll check the log soon.
[Nextbit Robin] Gandalf:
Maybe your headphone jack on the device is dirty or faulty
[Nextbit Robin] cutederf:
Thanks for the update

Samsung Galaxy Tab 2*

T-Mobile Samsung Galaxy S4

Huawei Ascend Mate 7*

T-Mobile Samsung Galaxy Note 4
[Nextbit Robin] gr3y_:
Hi guys,

in the last weekly I'm seeing a lot of stuttering... am I the only one?
[Nextbit Robin] jericho7:
I've attached a zip of the full log and dmesg

Thanks
[Nextbit Robin] AnierinB:
[MENTION=3878813]Gandalf[/MENTION]

So there is this bug that makes the status bar all distorted when editing photo's in the gallery app. Mainly happens when adding a filter to any image. I can get logs and post them if it helps although this is probably very easy to reproduce on your end.
[Nextbit Robin] NotAPerso:
Dude, this was on the previous page. ?

I'm running 5/27 build and can't reproduce this issue. So perhaps it was an added bug in the new build. In any case always include logs. Even if it seems easy to reproduce it's best to include logs as well as steps to reproduce.
[Nextbit Robin] Darkstar_Devil17:
Can anyone confirm whether VoLte is working or not with Jio on the latest build? As it was not working on 6/6 build.
[Nextbit Robin] hairycheez:
I can confirm that VoLTE is working for T-Mobile.
[Nextbit Robin] Lucy66:
No luck for jio....I couldn't use VoLTE
[Nextbit Robin] aminfri:
I am having the same issue. Its very notable. I dont quite know how to log this one since its everywhere.
[Nextbit Robin] cutederf:
The phone will freeze for a few seconds when you plug it into charge. I work in a freezer. Temperatures below zero. I've notice it will shut off after about 10 minutes in cooler. Not sure if this happens to any other phone or just Robin
[Nextbit Robin] Gandalf:
okkk

VoLTE is *actually* working now. I just started a build on Jenkins so I'll post the link when it's done. Safe to dirty-flash over Official Weeklies.

Edit: just have to clean up a few small things before shipping a build
[Nextbit Robin] kushal16:
can anyone please confirm whether VoLTE is working on Reliance Jio in India?
[Nextbit Robin] Gandalf:
Hopefully today I will post a build.

New OTA is building now.

New OTA is up, 20180619. Have fun with your new VoLTE powers
[Nextbit Robin] avreddy1996:
I have installed the yesterdays build and volte is not working yet

I have installed the yesterdays build but volte is not working yet
[Nextbit Robin] Gandalf:
Can you get logs for me? The matlog app that's built-in works great.

It works perfectly fine here on US AT&T. I checked the IMS registration records and switched to LTE-only and made some calls.. so it's working here
[Nextbit Robin] avreddy1996:
I have tested on reliance jio India here i am providing the log i got and screenshots

i couldn't attach in thread so i am giving drive links

dashttps://drive.google.com/open?id=1dA28g0aJiErQA2jzt6s9M56gfxejOi35***

https://drive.google.com/open?id=17FV7kEUWJiWdJ980rZ2a96__4tpkOFck

https://drive.google.com/open?id=1hISlxuAWoMJmPck7D5c5HP83yA1LlnZJ
[Nextbit Robin] Gandalf:
Ok this is probably just APNs or something. It works fine on US AT&T, so IMS is functioning correctly.

Can you dial *#*#4636#*#* and then go to Device Information. Then in the overflow menu, select IMS Service Status and post a screenshot
[Nextbit Robin] Gandalf:
cant access any of them, and the first link is broken
[Nextbit Robin] avreddy1996:
here you go

https://drive.google.com/file/d/1dA28g0aJiErQA2jzt6s9M56gfxejOi35/view?usp=sharing

https://drive.google.com/file/d/17FV7kEUWJiWdJ980rZ2a96__4tpkOFck/view?usp=sharing

https://drive.google.com/file/d/1hISlxuAWoMJmPck7D5c5HP83yA1LlnZJ/view?usp=sharing
[Nextbit Robin] NaterTots:
My wife's phone is the Robin and I checked hers this morning after updating and VoLTE is working on it with US T Mobile.

Thanks [MENTION=3878813]Gandalf[/MENTION]
[Nextbit Robin] avreddy1996:
I am using reliance Jio in India,

I don't know anyone else is facing the same issue but I couldn't make volte calls ins service is broken
[Nextbit Robin] boxes:
Any noteworthy bugs with Oreo currently?
[Nextbit Robin] Gandalf:
Please take OTA to 6/21 and check that.
[Nextbit Robin] cutederf:
On 6/21. Ota. Didn't read sim. Went back to 6/19. I'll give it a try tomorrow after work. With a clean install. Thanks in advance. Keep up the great work.
[Nextbit Robin] Gandalf:
That's wild, I made ZERO changes, I just re-fired the Jenkins build.

edit: ok, I found the problem. Something slipped past me
[Nextbit Robin] dbearsfootball:
This is by far the best nougat ROM for this phone. Everything works great. Acasional lag and force closes but other than that for beta ROM it's good. Thank you for your hard work and time.
[Nextbit Robin] pintasmapila:
I must say, the thing that is bothering me the most is the fact that the fingerprint reader stops responding to touch-only after being idle for some time. Then it is needed to press the power button for it to 'wake-up'.
[Nextbit Robin] shaggy5991:
Are you guys just flashing the 1450 updater zip in TWRP right before you flash Omni?
[Nextbit Robin] pintasmapila:
I installed 1450, then i installed CM14.1 and then OmniROM.
[Nextbit Robin] shaggy5991:
Did you flash the full 1450 stock zip or use the 1450updater zip, haven't been having lock with the camera and want to make sure this go I get it working
[Nextbit Robin] pintasmapila:
I followed this procedure:

https://help.nextbit.com/hc/en-us/articles/218638257-How-to-flash-back-to-the-stock-Nextbit-OS
[Nextbit Robin] valhallen.282:
I wipe the ROM from inside TWRP. or rather i wipe -> Data, System, Dalvik/ART Cache and System Cache. Reboot to bootloader.

Flash 1450 updater zip from xxxNextOSxxx

Flash the OmniRom followed by Gapps + 2.79SuperSU

Edit- confirmed GPS is not functioning. With and without GApps. Attached satstats images. With GApps the system uses cellid for locations but after a while it goes nuts. I can't really see in my logs why it isn't working. I let each rom sit for one hour in an open space before checking. Here and Waze report location but don't work well while driving I was wondering why and Satstats from F-Droid told me the right story
[Nextbit Robin] Gandalf:
nfc fixed in next build
[Nextbit Robin] valhallen.282:
Are you using the same audio and bluetooth drivers as the 7.0 builds?

That build solved a lot of my Bluetooth audio issues with the Robin though it lost some perceptible volume (possibly because of missing. ARKAMYS libs)

Also speaker volume control does not work. 6.0/7.0/7.1 all have the issue. It registers a volume reduction in the UI and on log. But volume output remains the same. I can record a test call for you and upload it if necessary.

(P.S. I have working builds of all three roms and I swap between them for testing.)
[Nextbit Robin] Gandalf:
Hm, haven't tested volume changing

Im currently using the CM implementation of smart amp and audio amplifier but I plan to return to the stock implementation.

As far as Bluetooth goes, the Bluetooth HAL is inline with the latest CAF tag for the platform, as is the media, audio, and display HAL -- LA.BF64.1.2.3-01210-8x92.0

Unfortunately CAF hasn't updated 8992 tags to 7.1 yet but they have a. 7.1 tag for 89xx and 8x96 so I am going to try those out, even though the 89xx is intended to be a commonized tag for all platforms 8996+

I started the device tree with CM tree but I am slowly migration to more stock-based configs. The kernel is completely new and totally my own stock+CAF, no CM changes in it.

My ultimate goal is to have a CAF-only device tree that can be easily updated with each CAF tag release with no other dependencies anywhere else
[Nextbit Robin] GoToHealth:
Very good ROM at the moment. This is the only real working 7.1 ROM since CyanogenMod is God awful and now discontinued. Been testing for about 12 hours now and I can say I'm satisfied. Will report more when bugs are discovered.
[Nextbit Robin] Gandalf:
I left my device idling on my desk for a day or so and it was at 84% after over 24 hours when I picked it back up (not sure what it was at when I left it) , but regardless I've narrowed down the battery drain some people report (especially on CM) to the RIL (this build had a broke, and therefore not running RIL). Now I just need to figure out WHY it's draining..
[Nextbit Robin] Kaleshwar:
Can I I use substratum on the ROM?
[Nextbit Robin] sabresfan:
I do. Just make sure you are running a compatible theme. Also make a nandroid first in case something goes wrong.
[Nextbit Robin] sykomaniac:
Is it legacy or full masquerade support?
[Nextbit Robin] Kaleshwar:
Thanks you. Install swift dark and its working fine.
[Nextbit Robin] Gandalf:
OK I'm going to post another build with working NFC as soon as I get home from work in a few hours. Next up is GPS
[Nextbit Robin] telmob:
Nice! :) Thank you.
[Nextbit Robin] GigahurtzUK:
Thank you.
[Nextbit Robin] TestSpecimen:
Just literally installed the 25th December release (fresh install from scratch).

The first thing I noticed is that the developer options menu does not work. It appears after tapping build number, but I can't get into the actual menu (black screen only).

Anyone else having this problem?

On another note CM was indeed a bit of a nightmare after my initial positive impression (constant freezing, strange multicoloured screens etc)...and now it seems dead anyway!

Glad to be able to come back to this ROM, keep up the good work!
[Nextbit Robin] luygrous:
..

How can I go back to 6/19? I have the same problem.
[Nextbit Robin] NaterTots:
Download it from the Omni website, boot into TWRP recovery, flash the 6/19 build.

That should do it.
[Nextbit Robin] luygrous:
It worked. Thanks!
[Nextbit Robin] Gandalf:
https://drive.google.com/file/d/15QKRsJdC0-Fg12Y_QewJjZ9uhdJH1Tpi/view?usp=sharing

[MENTION=3986423]cutederf[/MENTION] [MENTION=9127010]avreddy1996[/MENTION] please try 06/22 OTA
[Nextbit Robin] avreddy1996:
Thank you [MENTION=3878813]Gandalf[/MENTION] gonna give it a try today
[Nextbit Robin] cutederf:
not sure if I did this right.

https://drive.google.com/file/d/1dJOys78dx0_l9T1DSLFmVTuHCwGnwdAZ/view?usp=drivesdk
[Nextbit Robin] Gandalf:
looks like it works for you :good:
[Nextbit Robin] Gandalf:
I think [MENTION=9084517]zephrCypher[/MENTION] has a cool video to upload for Jio users :cool:
[Nextbit Robin] zephrCypher:
Jio VOLTE working completely

Jio VOLTE is finally working completely on this ROM, the first Oreo ROM for Nextbit Robin (Ether) to work with VoLTE. :o

Very much thanks to the developer Gandalf ( Jake Whatley )

:angel:

:good:
[Nextbit Robin] cutederf:
I'm not any good a building. Wouldn't even know where to start. But I can test what ever you would like. And I could log the shoot out of it. Thanks for the hard work.
[Nextbit Robin] Gandalf:
Join the Telegram group: https://t.me/joinchat/DnX7jUkQWGK6WfH9xCS56g

They get hot fresh ROM goodies almost daily

I'm focusing on flipping the switch to my kernel now:

https://github.com/jakew02/android_kernel_nextbit_msm8992/tree/android-8.1-new

Update: Jenkins is done. No Delta since the date is the same. The new 06/22 build it up to date with working VoLTE
[Nextbit Robin] zephrCypher:
VoLTE video

Posting video showing incoming & outgoing calls made on Jio 4G VoLTE which LTE only. [MENTION=3878813]Gandalf[/MENTION]

This is the link to video uploaded on Google drive

https://drive.google.com/open?id=1V-BugPoI3gqNTdKvfUhE5mj3CvuUcriT

Enjoy :D
[Nextbit Robin] advaithk:
OmniROM 8.1.0 not installing over 7.1.2

Hey guys,

I'm currently on OmniROM 7.1.2 NJH47F (omni-7.1.2-20171120-ether-WEEKLY), with TWRP v3.1.1-0.

I'm trying to install the current version of OmniROM, i.e., omni-8.1.0-20180624-ether-WEEKLY.zip, over OTA, and the updater has downloaded the proper zip file and kept it in the /sdcard/OpenDelta folder.

The problem is I get this error when I try to flash it once it reboots into recovery.

Installing zip file 'sdcard/OpenDelta/omni-8.1.0-20180624-ether-WEEKLY.zip'
E3004: This package is for device ether; this device is .
Updater process ended with ERROR: 7

Any ideas? Am I doing something wrong? It's a little bit alarming that TWRP thinks my phone is named '.', instead of 'ether'.

Also, after the above scene is sorted, do I need to flash 8.1.0 GApps as well before restarting into 8.1.0?
[Nextbit Robin] jabashque:
Update your TWRP to version 3.2.1.

EDIT: I have no idea if you can actually dirty flash OmniROM 8.1.0 over 7.1.2, since I know that for LineageOS, they have to prepare special transition builds that upgrade various databases or whatever. But, if dirty flashing does work, then yes, you would probably want to replace the GApps with the ones for 8.1.0 before booting into the update.
[Nextbit Robin] Gandalf:
DO NOT dirty flash between Android versions, and upgrade your TWRP version.
[Nextbit Robin] valhallen.282:
I might get myself another Robin just to play with this. Such a beautiful phone. I miss it! Great work [MENTION=3878813]Gandalf[/MENTION]
[Nextbit Robin] PielunA:
Internet connection goes unresponsive daily. System does not indicate 'No Internet' Wi-Fi connection.

It needs a reboot to have connection again.

AC1900 ASUS router, using Wi-Fi.
[Nextbit Robin] advaithk:
Thanks! One more Camera issue, though

Hey thanks so much, guys! I ended up flashing after wiping all partitions.

I now have a really weird issue. The camera doesn't seem to be opening at all. Any fixes for that? Everytime I open the camera app, I'm greeted with the "Camera has stopped working" window.

I flashed OpenGApps ARM64 8.1 "stock" after I flashed the OmniROM zip, if that's any help.

Everything else is working fine. Great job on the rom, otherwise! :D

Thank you so much [MENTION=3878813]Gandalf[/MENTION] for this amazing release!

EDIT: I realised after going through few posts in this thread, that I wasn't supposed to install Google Camera from the OpenGApps zip. Is there any way I can go back to the stock OmniROM Camera now? Or do I have to flash the ROM again, and download the "aroma" version of OpenGApps so that I can not install Google Camera?
[Nextbit Robin] jabashque:
Delete /system/addon.d/70-gapps.sh, then dirty flash OmniROM and a GApps package that doesn't include the camera (or the aroma version, if you untick Google Camera).

Easiest way would be to boot into TWRP, mount /system, then delete 70-gapps.sh using the file manager.
[Nextbit Robin] Gandalf:
I'm going to add Snapdragon Camera back soon as well
[Nextbit Robin] Natatud:
Is WiFi Calling ever going to be functional? It's the only thing keeping me away from using this room.
[Nextbit Robin] Gandalf:
Did it ever work? It's provisioned on my account with US AT&T but it has never worked for me, even on stock. It works just fine on any device I buy from AT&T and nexus devices, but nothing more.

What ROM are you using with what carrier that wifi calling works?
[Nextbit Robin] Quantify:
Thank you for building a ROM that works so well! I have an Ember Robin which I still use as a daily driver. I was on LOS but wanted a reliable Oreo ROM...This seems to be it! VoLTE is working nicely on T-Mobile, and no crashes/bugs so far. Much appreciated!
[Nextbit Robin] Gandalf:
Switched over to my kernel. It'll be in the next official build this weekend
[Nextbit Robin] Darkstar_Devil17:
I'm facing issues in last two builds with Bluetooth and Cast, anyone else facing this?

If yes, is this fixed in upcoming build?

Thanks for keeping our Robin alive. ?
[Nextbit Robin] Gandalf:
Logs pls
[Nextbit Robin] Gandalf:
Can you make a jira ticket with logs?

jira.omnirom.org

Thanks
[Nextbit Robin] Natatud:
I'm on T-Mobile and while it didn't work for long, it briefly worked on stock 7.1.1 but I haven't been able to recreate that with any other room or version of stock.

I don't know if it's possible to get it working, it would just be really awesome for it to work as well as VoLTE.
[Nextbit Robin] Quantify:
One very low priority bug I just noticed...charging to 100% does not reset the battery timer for "time since last full charge". Happy to submit a log if it would be helpful...would I charge to 100%, pull off charger, and then capture the log?

---------- Post added at 02:53 PM ---------- Previous post was at 02:50 PM ----------

It worked for like a hot minute on a beta build of 7.0, I think. I remember this garishly huge "VoWIFI" indicator in the status bar. AFAICR, it never worked on an official build of anything.
[Nextbit Robin] Gandalf:
Open a ticket at jira.omnirom.org pls :good:
[Nextbit Robin] gr3y_:
This looks to be fixed in the last weekly!
[Nextbit Robin] boxes:
How has battery life been for the latest build?