yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] pseudonoise:
I'm running the latest 7.012-20170430-ether-weekly OMNI and as ever I'm most impressed - however like some users I've noticed that I cannot reduce either the "in-call" earpiece or speaker volume to below approximately 20% of full volume level.

Sometimes this means that for some calls I need to hold the phone slightly away from my ear - this sometimes means particularly in quiet surroundings others can hear both sides of my telephone call.

What i can do to fix this please ?
[Nextbit Robin] DECHTECH:
I can't seem to get the equalizer working at the moment. I don't hear any change when turning up the highs or mids, though I should quite easily. Does not work on both speakers and headphones. I have tested with many apps including YouTube, SoundCloud, AIMP, phonograph (both play store and the one packaged) and Apollo (from play store). Logcat attached...
[Nextbit Robin] laofan:
Use headphones...
[Nextbit Robin] nightfly0815:
Hey , I checked the UI tuner, but there is no setting for the battery...

I tried to activate the headset toogle, but this is just for the cable headset.

I think the problem is, that Omniarom use it´s own battery settings in the menu.

Maybe there is a a solution in the future. For now it´s not a problem but it would be nice that this function works in future builds.

Back to the GPS "problem" I noticed that it tooks very long to lock the GPS (outside). I tried the APP GPS-Test to see how many satellites are reachable from the mobile phone. I used a trick. I hold a OneplusOne phone next to the Nextbit and started the same APP. When I do this than the App finds the satellites much faster and it locks the GPS. When you drive by car it also lose the GPS lock when you lock the phone and it´s tooks some time again to lock the GPS again. You can test it, when you use google maps and start a navigation. I mean the whole GPS "bug" is bad, because when I use a fitness app to track the route it also stops from time to time and lose the GPS Signal...

I noticed that this problem don´t exist on other builds from the past...

If I can help you with some more log files or information than feel free to contact me :p

greets chris :)
[Nextbit Robin] AnierinB:
Flashlight QS toggle isn't working. Nor is my flash. Had this problem before and it always seems to come back. Even after clean flash. Can post logs if necessary, but what should I do? Start logging then try to toggle a few times?
[Nextbit Robin] ipowyourface:
Flash and Flashlight QS working fine for me. Try doing a clean flash of the ROM.
[Nextbit Robin] gr3y_:
Anyone else having problems with in-call volume being too loud? I've lowered it to the minimum but it's still way too high.
[Nextbit Robin] pintasmapila:
I have, but haven't been able to get a log from it.
[Nextbit Robin] AnierinB:
I have. The problem comes back eventually.
[Nextbit Robin] pseudonoise:
As mentioned in a previous post I also have problems with the in-call volume being too loud.
[Nextbit Robin] Luv-Kush:
Anybody got WiFi hotspot automatically connected when Bluetooth connects. I have tried all automate, micro droid, tasked etc cannot get it work. Any help appreciated. Thanks
[Nextbit Robin] bmccoy11:
I've been charging with the same Aukey QC3 charger and USB C charging cable, however quick charging doesn't seem to work with this ROM. It can't even keep my phone charged while it's plugged in and in use. Am I the only one who's noticed or is it just me?
[Nextbit Robin] VenomMOD:
Works fine for me.
[Nextbit Robin] spizzlo:
Quick charge works fine. Try a different charger and get ampere. It's an app that shows you the charge current. For me (and probably the norm) it's around 2,400 mAh.
[Nextbit Robin] Fiishbonne:
Could be just a cable problem, I had same issue. Had to change the cable.
[Nextbit Robin] Kaleshwar:
Has anyone managed to get android pay to work?
[Nextbit Robin] pintasmapila:
I didn't. :rolleyes:
[Nextbit Robin] Kaleshwar:
Okay.
[Nextbit Robin] bmac6996:
Been doing some research.. basically it comes down to this:

Looks like this needs to be modified at least in the Kernel in order for part of safetynet to pass.

https://github.com/darkeyes84/andro...mmit/edcf9b40e89d284c35b876b610badbd643d2062d

This was done from for a Nexus 5 /6p rom that I been using and with Magisk, I can pass SN and AP works.
[Nextbit Robin] Kaleshwar:
Yup it works on the nexus 6p.
[Nextbit Robin] RaS_KoR:
Since two releases LiveDisplay won't work when I set it to auto. I don't know how can I log/repair that.

(I use the Omni updater to upgrade my device), I will try clean install but before I want to know if someone get this issue too.

An other thing, there is no more shortcut from settings to OmniJAWS.
[Nextbit Robin] bmccoy11:
This seems easily doable if anyone wants to build and test a kernel with those several lines of code added.
[Nextbit Robin] pintasmapila:
Anyone noticed there's still some crackling sounds, like some 'leftover' or ghost sounds?
[Nextbit Robin] DECHTECH:
Yes that's still an issue sadly.
[Nextbit Robin] pintasmapila:
Any issues addressed in the latest build?
[Nextbit Robin] im_electronic:
https://omni.cmxlog.com/7.1/ether/
[Nextbit Robin] bmccoy11:
Actually, it doesn't seem like this is the problem - Magisk Hide automatically patches this to always send a verified boot status (currently my verified boot status seems to be green with it enabled), as far as I can tell.
[Nextbit Robin] bmccoy11:
Finally figured out what was causing CTS to fail - it was the build fingerprint in the build.prop, which seems to have been set to the 7.1.1 beta's build fingerprint (which probably hasn't passed CTS). All I did to get CTS/Android Pay working (with Magisk Hide enabled) was change this line in the build.prop:

ro.build.fingerprint=Nextbit/ether/ether:7.1.1/Robin_Nougat_91/00WW_Jenkins_91:user/release-keys

To this:

ro.build.fingerprint=Nextbit/ether/ether:7.0/Robin_Nougat_88/00WW_Jenkins_88:user/release-keys
[Nextbit Robin] RaS_KoR:
I clean flashed the last build and the bug seems to be fix.
[Nextbit Robin] adeelmysore:
Thanks this worked for me.

---------- Post added at 10:46 AM ---------- Previous post was at 10:45 AM ----------

This did the trick. Thank you so much.
[Nextbit Robin] pintasmapila:
Camera stops shooting photos after the first or second shot. Anyone noticed this.
[Nextbit Robin] DECHTECH:
I'm not using SD camera but with google camera it seems fine. Tried other camera apps?
[Nextbit Robin] crian:
Camera is bugged. Use another camera app.
[Nextbit Robin] dansaiblis:
Wiped cache & data in settings > apps. Works fine then on my device.
[Nextbit Robin] pintasmapila:
Well.... Thank you for that. It is working for now. I hope its permanent.
[Nextbit Robin] vivekraj_driod:
Unusual idle state battery drain

Noticed an unusual battery drain on the idle state for the first time. I'm using the recent build.

Anyone facing the same issue?

[IMG="Idle battery drain"]https://goo.gl/photos/6qtKWJT6cWzPyj8w5[/IMG]

[IMG="Build"]https://goo.gl/photos/Y2em6KJ3be7end2e6[/IMG]
[Nextbit Robin] RaS_KoR:
I didn't notice any drain, you can check your CPU State in Settings > Omnigears > More > Time in state
[Nextbit Robin] keredini:
This is great and works, but does anyone have Android Pay working for payments via NFC? I tried at a terminal recently and it never connected. I did check that NFC was enabled and Android Pay was set as the Tap and Pay default app.
[Nextbit Robin] xBane_:
To pass cts, you can't have an unlocked bootloader. If I lock my bootloader, will I be able to take Omni otas?
[Nextbit Robin] bmccoy11:
You don't need to have a locked bootloader to pass CTS, Magisk Hide fakes the bootloader status flag.
[Nextbit Robin] xBane_:
I flashed magisk and enabled magisk hide. I made sure to reflash omni to get rid of SuperSU first.

Android pay still gives me the "can't be used on this device" error.
[Nextbit Robin] xBane_:
Do i also change the ro.build.description to "ether-user 7.0 Robin_Nougat_88 00WW_Jenkins_91 release-keys"?

EDIT: I did this and it still doesn't work.
[Nextbit Robin] ipowyourface:
Make sure you change ALL the "91"s to "88"s, not just the "7.1.1" to "7.0".
[Nextbit Robin] xBane_:
Yes. Attached is a screenshot of the changes I made.
[Nextbit Robin] ipowyourface:
Strange... do you have Magisk installed and have Magisk hide on?
[Nextbit Robin] xBane_:
Of course. Magisk hide is working, it hides root from a root checker I installed.
[Nextbit Robin] bmccoy11:
Only thing I can think of is to just factory reset or at least reflash OmniROM, then flash Magisk and replace that one line in the build.prop.
[Nextbit Robin] xBane_:
Wellp, it seemed to fix itself. I went into the magisk app for one last attempt, and it screamed at me that magisksu wasn't installed. I went into recovery and reflashed magisk and it passed safteynet.
[Nextbit Robin] DECHTECH:
Hey I mentioned this before but it caught no attention. Can anyone get the equalizer to work? Since (I think the 7.1.2 upgrade but I'm not sure) I can't get it to work at all. Can anyone confirm?
[Nextbit Robin] DECHTECH:
After flashing the latest weekly, substratum (The app) wouldn't open. If this occurs to anyone else: Open google play, uninstall, and re-install.
[Nextbit Robin] RaS_KoR:
I use the 2017-05-14 version and the equalizer works without issues.
[Nextbit Robin] DECHTECH:
Super odd :\ I'm on RR anyway now for the time being.
[Nextbit Robin] carguy303:
So I am looking at the build fingerprint and it seems like this is still using the beta build 91 for the proprietary blobs. Would there be any advantage to using the newer builds? Build 102 specifically addressed a lot of things that would be nice if they weren't already in Omni.
[Nextbit Robin] valhallen.282:
For that NextBit needs to release sources. As of now available sources are only 7.0
[Nextbit Robin] DECHTECH:
Build 108 sources are going to be up next week.
[Nextbit Robin] jimandroidnerd:
Hey everyone. i just updated to the new build and whenever i reboot it says system ui crashed. Is it the new build or is it just my phone?

Cheers, Jim
[Nextbit Robin] vivekraj_driod:
No issues on the latest build (2017/06/04). It's perfect expect the substratum app crash which can be fixed by re-installing it.

Try a clean flash.
[Nextbit Robin] jimandroidnerd:
Very wierd. I just wouldn't work for me. I'll just wait for the next build.
[Nextbit Robin] xBane_:
There is one issue I have found- the settings pop up shortcuts are messed up.

Other than that, it feels smoother than last week's build.
[Nextbit Robin] Fiishbonne:
If you used Substratum, then disable/uninstall all overlays and then update after that you can reapply all overlays. Or better yet, uninstall and after update reinstall all overlays.

Worked for me ;)
[Nextbit Robin] jimandroidnerd:
thnx man. ill try that:good:
[Nextbit Robin] bmccoy11:
Looks like build 108's kernel source is up, finally! https://modders.nextbit.com/robin-7.1.1_build-108-kernel.tgz
[Nextbit Robin] AnierinB:
[MENTION=3878813]Gandalf[/MENTION] I'm trying to find the settings icon for system ui tuner on github to help a theme developer add that settings icon to his theme VALERIE. We cannot for the life of us, find it anywhere. Can you help me out with this? I'd assume the icon is universal to all roms and not just Omni but I could be wrong.. Either way, some help would be much appreciated in finding it's .XML
[Nextbit Robin] bmac6996:
Thanks to this post. Now CTS passes. (haven't checked lately though)..

Anyone got Arise/Viper4Android to work lately? Last time I installed, drivers wont' install properly and wouldn't work.
[Nextbit Robin] FlamieFox:
Does the latest weekly (11 06) need the stock 7.1.1 firmware from Nextbit?
[Nextbit Robin] XxXPachaXxX:
7.0 and 7.1.1 firmwares are the same
[Nextbit Robin] FlamieFox:
Thank you :good:
[Nextbit Robin] XxXPachaXxX:
If u asking, here you go :)

The changes are at system and boot/kernel level
[Nextbit Robin] Jacobwitt:
I see updates are actually just patches now rather than entire rewrites 49m < 500ish m gg
[Nextbit Robin] Jacobwitt:
Still works gg
[Nextbit Robin] the_rooter:
so is the developer implementing the CTS fix from above or is it still failing out the box?
[Nextbit Robin] Jacobwitt:
The picture attached is after doing the modifcation stated in his comment + Installing Magisk Hide + root.

Out of the box fails always, every time because the boot loader is unlocked
[Nextbit Robin] the_rooter:
I guess that's not what I meant. Aicp after installing and turning on magisk hide it passes, stock as well passes with magisk hide. So I installed this rom immediately turned on magisk hide and still failed. What I meant out of the box for this rom is after installing and then turning on magisk it fails. That's why I was asking if the developer was going to implement the mod fix.
[Nextbit Robin] FlamieFox:
Thanks :good:
[Nextbit Robin] Jacobwitt:
Not sure, I installed magisk just to run a few apps, *cough androidpay* and to use Greenify as well.

I Just did the patch myself using build.prop editor and Wallah it worked.
[Nextbit Robin] raddatt:
Thanks. Asking as a noob, does this mean I should flash those to be the most up to date? Are our proprietary blobs all up to date?
[Nextbit Robin] valhallen.282:
You realise you have answered most of your own questions. Magisk is required for Pokémon Go and Android Pay.

Battery life is a YMMV situation. I get fantabulous battery life and I've been a tester so I know just how much abuse this ROM handles. (READ - A LOT)

CAMERA is SnapDragon Camera it works reasonably well for most scenarios. I use Open Camera as it's a lot more powerful.

Connectivity? This ROM has been the be all end all of the Robin's capabilities and connectivity. For me it's either stock ROM or this.

The updates are timely the corrections of issues are on point and the ROM builder is super interactive. I don't think anything else is needed.

Hope that answers your question.

YES - THE UPDATE to the latest build(Robin sources) is due but CAF sources are already up to the latest tag for this device.
[Nextbit Robin] DECHTECH:
1. The camera slowness can be fixed via another camera app like Google Camera or something of the like, just don't use open camera as it were also slow for me (Though very powerful).

2. I've found the battery on Omni is way better than stock, most would agree.

3. All custom roms don't have the 100GB cloud storage

4. The LED's on the back are used on boot with a cool looking animation thingy, also the lights are enabled (all of them) when charging, and if you've got a low battery.

5. I don't have a smartwatch, but BT works fine for audio and file sharing for me on Omni. LTE/4G connectivity is great here.

6. To get apps that do that kind of thing (Netflix, snapchat, Pokemon GO) you need to edit the build.prop file in system, and find "ro.build.fingerprint=Nextbit/ether/ether:7.1.1/Robin_Nougat_91/00WW_Jenkins_91:user/release-keys". Then changing it to "ro.build.fingerprint=Nextbit/ether/ether:7.0/Robin_Nougat_88/00WW_Jenkins_88:user/release-keys".

I've also tried setting ro.build.fingerprint to "Nextbit/ether/ether:7.1.1/Robin_Nougat_108/00WW_Jenkins_108:user/release-keys" and worked fine, bypassing safety net without issues.

Hope this helps ;).
[Nextbit Robin] :
Omni is my favourite ROM so far. There is only one thing which keeps me from using it as my daily ROM. The minimum in call volume is way too loud and i always have to use my headphone when I want to call someone or somebody wants to call me. Since this is a very popular ROM and a lot of people are using it I am wondering if anyone has the same problem. If so is there a way to decrease the volume? I would really love to use Omni as my standard custom ROM.
[Nextbit Robin] DoobyDroid:
Best ROM I have tried very smooth good battery keep up the good work
[Nextbit Robin] Dishe:
Ok thanks guys, downloading now!

One more Q- is there a stable vs weekly release? All I'm seeing are the weeklies.

Edit: Also, for gapps, 64-bit or 32?
[Nextbit Robin] RaS_KoR:
No stable version but weekly are very stable.

Arm64bits for gapps.
[Nextbit Robin] spizzlo:
So that code to get safety net pass on magisk has been amazing. The problem for me is that it's been kind of wonky. It will be working and then it won't. I don't change anything but safety net just fails. I don't get it. Is anyone else having this issue?
[Nextbit Robin] the_rooter:
was there an update the the playstore or something? magisk worked yesterday and now i it fails...this is on stock as well. magisk still work just the CTS fails
[Nextbit Robin] XxXPachaXxX:
No need to flash the latest 7.1.1 images if you are using a custom rom. As you can see the firmware (bootloader, radio, etc.) are the same of the 7.0 build.
[Nextbit Robin] noonebhargav:
Safetynet updated,

Use magisk core only mode to make CTS pass for now.
[Nextbit Robin] gr3y_:
Same problem here.
[Nextbit Robin] Dishe:
Playing with it and have been really happy so far. Battery life seems improved, connections like BT are definitely not crapping out like the stock 7+ roms did. Amazing work!

I'm confused about the notification LEDs, though. I notice now that the original notify light on the bottom doesn't light up for charging anymore. Now only the 4 lights on the back do. But, they light up and then turn off and don't come back on again unless I toggle that option in settings. Then it will shut off again as soon as the screen times out or the phone goes to sleep. I was hoping that they would show percentage of the battery charged since there are 4 lights, but I'd be happy enough if it just worked as a charging indicator like the bottom used to. Right now, all LEDs shut off while charging, and I can't seem to get anything to consistently inform me whether or not my phone is currently charging. As someone who has forgotten to plug the phone in at night, I like being able to check on it in the middle of the night and see the glow informing me it is charging. Is this a known issue with the ROM, or are my settings messed up? I have to admit I don't fully understand the notification LED settings or how they are supposed to work. But I did try resetting it to defaults, and it still isn't working as expected.
[Nextbit Robin] the_rooter:
The updated beta for magisk works fine without core mode only.
[Nextbit Robin] bobahgnaoush:
Battery Life

I installed Omnirom last night hoping it would improve battery performance however it seems worse than stock. I was at 95% and woke up this morning at 67%, something seems wrong. I checked my battery usage and nothing stood out as the culprit. There is no way there should be that much idle battery drain. Any ideas? Also I have the same call volume issue, it's super loud, I only notice that when it says "HD" when on the phone (VoLTE?)
[Nextbit Robin] Dishe:
Interesting, hey that sort of makes sense with the HD voice thing. I was nervous about the audio quality after reading someone's complaint, but when others didn't seem to have it, I figured it didn't effect everyone. Sure enough, my audio volume has been fine on calls. But, my carrier doesn't support VoLTE. As I understand it, I've heard some people don't like "HD Voice" on some handsets, as it sounded louder and more "skype-like" versus traditional GSM phone calls. Turns out, if I understand this correctly, the hardware inside the phone often uses a special audio DSP for calls, and the regular one for generic audio. Most VOIP systems are processed by software rather than hardware, and therefore don't use the same DSP as phone calls. I think the reason people sometimes don't like HD Voice is that those handsets aren't using the phone audio processor, but rather the system one.

So, two questions for you: 1) Did HD Calls sound better before the ROM? I wonder if Nextbit originally had the routines to route audio through the phone system on VoLTE, and this ROM doesn't. 2) If you turn off HD Voice (toggle Enhanced LTE services off), does it sound better?

EDIT: I just checked, and OmniRom doesn't seem to have the option for Enhanced LTE services in settings. It was definitely there on the stock rom!

As far as battery, I'm getting mixed results too. The first day this past week, it was excellent. First, within an hour or two of being off the charger with light use, it predicted I still had enough battery to make it until tomorrow. Later that day, I had to sit through a fundraising event with lots of boring speeches (hours long event). I had a pretty decent amount of screen on time and plenty of network access, and my battery did a lot better than I remember the stock rom ever doing in that scenario.

But a couple of days later, it doesn't seem to be doing as well. Now an hour or two into the day it reports only about 6 hours left to the charge, and the battery chart shows a pretty steady decline over time. Like you, I don't see anything that would particularly be the culprit from the data there. I have no idea why it was so good one day and then so bad the next. Very strange.
[Nextbit Robin] bobahgnaoush:
I think you're right it has to be something to do with VoLTE, makes perfect sense. I installed Omni right out of the box so I never tested it with the stock rom to see how calls sounded. Just to test I installed Res Remix and I'm getting similar battery drain while the screen is on, however I'm noticing very good standyby battery life. My phone is on standby 90% of the time so I'm going to see how it lasts with this Rom.
[Nextbit Robin] earlgrey_44:
Settings/wireless and networks/more/cellular networks /enhanced 4G LTE MODE
[Nextbit Robin] valhallen.282:
Three things. First - Androids new power management interface that comes from the AOSP tree is all the same across ROMs. The only thing kernel Devs change are CPU frequency scalers to suit their needs or what they think is right for a Rom. Stock ROM from the OEM will ALWAYS have better battery life unless it has a butt load of bloatware.

Second - power management only kicks in once the system learns your usage pattern. So if you change something. Like watching a butt load of YouTube one day it switches to reflect that. Use it the same everyday and you'll have the same power consumption everyday. Simple process.

Third - if you are truly having issues with power management. Get a log.... It makes it easier to debug. Sorry. I'm not being rude. Just pointing out that apart from one or two of workarounds being used. This ROM is damn near perfect. And the back forth of battery discussions sort of gunks up the thread.
[Nextbit Robin] Dishe:
Yes. That's where it was on stock. But like I said, its missing on omni. I just checked again.
[Nextbit Robin] bobahgnaoush:
Updated to the latest build 6/17/2017 and the battery life seems really good now. Did a clean install with gapps (pico) had (stock) before maybe that had an effect. Anyway, seems great now, Also you can disable VoLTE calling which I did, didn't seem to fix any of the loud speaker issues.
[Nextbit Robin] bmccoy11:
Permanent SafetyNet Fix

Here's a small fork of Deic's universal SafetyNet fix module with a modified build fingerprint for the Nextbit Robin. The original module should also work, but it changes your build fingerprint to one from a completely different Xiaomi device, which may or may not have side effects.

No need to make build.prop edits manually anymore, just install this module through Magisk or TWRP. https://github.com/bmccoy11/nextbit...es/download/v1.10.1/nextbit-safetynet-fix.zip. The module should stick through updates as well as long as you move the Magisk installer ZIP to your OpenDelta/FlashAfterUpdate folder.

If you still can't get SafetyNet to pass after installing this, grab the latest Magisk uninstaller at tiny.cc/latestuninstaller and run it, then install the latest Magisk beta and reinstall this module.

Also, in case Google updates SafetyNet again with stricter testing, this fix may very well not be permanent, but it should get this ROM to pass CTS for now.
[Nextbit Robin] Dishe:
Question, sorry if this sounds dumb but the weekly update notifications... If we accept and install, it won't wipe our data will it? I just got everything back the way I like it!

Also, will it overwrite buildprop? I fixed up mine so that certain apps would work, if the flash preserves user data, will it also preserve buildprop changes? Thanks!