yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] sketchman16:
Battery life definitely seems worse than when I had LOS. Gonna flash back to be sure. Looks like it's staying awake too much with the screen off.
[Nextbit Robin] jabashque:
If you don't mind me asking, how in the world did you achieve a battery drain rate of only 7%/hr with the screen on?
[Nextbit Robin] sketchman16:
All I did was not use auto brightness and set cores 5 & 6 governor to powersave as I noticed they were coming on way too easily with interactive.
[Nextbit Robin] Tautvydas:
Close enough, thanks.

If anyone wants to go back to default time and date colour @ lockscreen options via OmniGears, full code:

FFDAD2D5
[Nextbit Robin] sketchman16:
Just checked again. Those stats I posted were not for SOT battery use. It was the percentage of phone use since last charged that SOT was. So, for instance, if I used 50% of the battery with the screen on and then it was in deep sleep for the rest of the 50%, it would show a really low percentage for SOT, because it would adjust for the total amount of time the phone was unplugged instead of battery capacity used.

Battery capacity used I can't know now unless I flash omni again. Don't think I'll do that, though.
[Nextbit Robin] jabashque:
Ah, whoops. I always thought that was battery capacity percentage use, not phone-uptime-since-last-unplug use, but turns out I'm mistaken. Thanks for clearing that misconception; now your stats make much more sense.
[Nextbit Robin] sketchman16:
Anybody getting better than 9.6%/hour with the screen on? Moderate use. WiFi and cell radio on the whole time.

That's what I'm getting from LOS. Just curious how omni compares.
[Nextbit Robin] jabashque:
The lowest I've been able to go was about 17%/hr going from 100% to 75%, using the Glassfish v1.2 tunables for the interactive governor and just doing light browsing on the reddit is fun app and Puffin Browser (draining around 300mA).

I left LineageOS because of problems where I sometimes can't wake my phone and have to hard reboot, but if you haven't had that problem at all, I might go back to LOS for the battery savings.
[Nextbit Robin] boxes:
I see "rapid charging" on the lock screen, but I'm only seeing 600ma in ampere. Charging from 95%

Earlier when charging from 85% I saw 900ma current.

Qualcomm 3.0 charger and cable.
[Nextbit Robin] Tautvydas:
Robin has QC 2.0, not 3.0.

Whether you might able to use 3.0 capability I'd say more than random, and I get around 800ma with 2.0, charging from 15% or 90% for me is the same.
[Nextbit Robin] boxes:
QC 3.0 is backwards compatible with 2.0, which should be either 10 or 15 watts. Non-rapid charging is standardized at 5 watts or 1 amp. So the fact that the charge screen says rapid charging is odd. Either ampere is wrong is the phone has a bug. I'm going to restore stock nougat and see what kind of charging current I get.
[Nextbit Robin] boxes:
How does everyone feel about the camera quality on Omni vs stock? Seems like the camera on Omni takes longer to autofocus. Open camera is a bit better. Has anyone ported the stock camera app?
[Nextbit Robin] /root:
For me on stock ROM, stock app the focus was fine on normal shots but macro never worked. It would struggle to focus on the subject in the macro shot. Third party camera app worked fine here.

The same story with most custom ROMs I've tried, the focus has always been an issue somewhere somehow but on other camera apps it works fine for some reason.

I am a fan of Footej.

And I am trying the Modded Google/Pixel Camera and when that works its great.

So for me the stock camera apps that ROMs come with haven't been that great for me.
[Nextbit Robin] boxes:
Any more info on "glassfish tunables" for interactive? Google didn't return any results.
[Nextbit Robin] DECHTECH:
https://xdaforums.com/showpost.php?p=64279960&postcount=2
[Nextbit Robin] boxes:
I just started charging from 46% and checked ampere, now it's showing at 2500ma. So it does work, the charging circuit just draws less as the battery approaches 100%, which I believe I've read about before actually.

This is why they advertise things like "10 hours of battery in 30 min of charging". The last 10-20% takes a lot longer.

I've been getting awful battery life on Omni. Worse than stock nougat build 108 for sure. Interactive on big/little, noop I/O scheduler, swappiness 20, z-ram turned off. Auto brightness. Used 50% of my battery for 1 hr 5 min SOT, with LTE on and off periodically over maybe 5 hours. Going to restore stock and try that again for a while, it seemed a lot better the one day I used it.
[Nextbit Robin] demeez:
From my testing of the majority of the roms available here omni was probably the best performer but as you said the worst in battery life. I guess that's the price for performance. The lineage ones all seem to get about the same battery life for me more or less. Stock was pretty consistent but I found there was more lag present plus it has the annoying bluetooth bug that was never fixed.
[Nextbit Robin] boxes:
I'm trying out crdroid now, performance seems just as good as omni really. Crdroid has a tweaked kernel, but it's bases on LOS. It aggressively puts the big cores offline, only using them under high load. I found that Omni usually had both big cores online with the phone just idle and the screen on.

I downloaded ex kernel manager and applied the "glassfish" tunables for the interactive governor. Seems like a big improvement so far.

I also started using open camera, quality is good once you enable the camera2 api in settings, and change jpeg quality to 100%. Autofocus is fast and it captures quickly.
[Nextbit Robin] NurKeinNeid:
How did you turn off Touchboost on Crdroid? :eek:
[Nextbit Robin] boxes:
Touchboost doesn't seem to turn off unfortunately. The glassfish post indicated that even on stock kernels you should see some battery life improvements with the rest of the governor changes. I need to try pop kernel to see how stable it is.
[Nextbit Robin] jabashque:
Can't turn off touchboost on stock Omni and LOS kernels, but it seems like running `stop perfd` in a root shell stops whatever is pushing the clock speed of the little cluster to 1440MHz whenever the phone detects input. Works under both Omni and LOS.
[Nextbit Robin] demeez:
Have you uploaded your Xenon kernel anywhere? If I remember correctly haven't you added touchboost to it?
[Nextbit Robin] NurKeinNeid:
Yes, you should definitely try the pop kernel. But [MENTION=8079424]jabashque[/MENTION] 's hint is good too. :svetius:

---------- Post added at 01:22 AM ---------- Previous post was at 01:14 AM ----------

Yes, I disabled touchboost by default and implemented the toggle option in all my Rom builds. I do not use Crdroid. Was just curious, because in the glassfish thread is required to turn off touchboost.

But we should rather talk about Omni here. A very good Rom. :)
[Nextbit Robin] L3R0N:
I believe he was asking you whether or not your Insanity Kernel is available as a standalone download (meaning not attached to any rom, just the kernel). I'm also interested in trying it out but haven't the means to download a full rom that has it. Now back to your point on leaving this for Omni related discussions, I agree with you that Omni is a wonderful Rom.
[Nextbit Robin] Igorperrotta:
are the cloud leds still usable?
[Nextbit Robin] JaN0h4ck:
They are usable, but all of them lighting up when charging or all of them pulsing when your battery low.
[Nextbit Robin] Tautvydas:
Howdy, is there any update on Oreo for Robin?

Checked omnirom.org, twitter, google+, no news concerning the matter.
[Nextbit Robin] /root:
Last update by [MENTION=3878813]Gandalf[/MENTION] was in late Nov.

With Oreo booted on Robin and halfway to the Oreo release.

I think the 8.1 release might have screwed up/delayed the release. I assumed they must be working on getting 8.1.
[Nextbit Robin] Tautvydas:
I'm aware of Gandalf's posts and whatnot.

Still, it's been a long time, just want (I guess most of us) to get any news related to the subject.
[Nextbit Robin] BearOfXDA:
Very few ROMs have released Oreo builds, waiting will help you out a lot. If you're that impatient, try building for yourself
[Nextbit Robin] Tautvydas:
No need to get offensive.

I'm aware that few custom ROM devs and even major companies have released full 8.x (not beta).

I'm just curious, and yes, a bit impatient. Just interested how's the rom going, that's all.
[Nextbit Robin] BearOfXDA:
Wasn't being offensive, I'm just saying that if you really just can't wait that building for yourself is an option
[Nextbit Robin] RayRay10:
That's pretty bad attitude, you know?
[Nextbit Robin] BearOfXDA:
I'm very sure I'm not the only one that thought it, but I said it
[Nextbit Robin] Tautvydas:
Well, you're a hero. I'll give you that.
[Nextbit Robin] ziellziell:
Hallo, i'm using this rom(last build), but NFC can't active. Any sollution ?

*sorry for my english
[Nextbit Robin] demeez:
NFC does not work on omni.
[Nextbit Robin] Bokort22:
Double Tap to wake

HY!

Unfortunatelly the power button of my Robin is starting to get not responsive?

So i would like to enable double tap to wake on my device?

Does this ROM support it? If not could someone tell me which one is the right for me?

Thanks for your help.

T.
[Nextbit Robin] :
I don't think it is possible use double tap to wake on this phone. However there's an app called WaveUp. You can use that instead. It uses the proximity sensor.

f-droid.org/app/com.jarsilio.android.waveup
[Nextbit Robin] ziellziell:
Oke. Thanks
[Nextbit Robin] Bokort22:
Double Tap to wake

Ohh, that is a very ba thing to hear.

Thank you anyways!
[Nextbit Robin] :
Also you can use volume keys to wake your device. I forgot to mention that.
[Nextbit Robin] Bokort22:
Double Tap to wake

Thanks!

That seems to work fine:)
[Nextbit Robin] Phone_fan:
How do I get notifications to show? It currently isn't displaying any notifications in the notification bar.
[Nextbit Robin] demeez:
Are you talking about the notification light on the bottom? If so, you need to turn it on in settings -> notification led -> applications pulse.
[Nextbit Robin] Phone_fan:
No, the normal notifications that appear in the top bar...the notification bar. Notifications from email, sms, phone calls etc. Nothing is appearing in the top bar, other than the usual right-side indicators like signal, batter etc, or on my watch when I receive email or calls or messages or pretty much anything.
[Nextbit Robin] vagaba1:
Hello my friends!

Im in need to use my NFC and im aware that the last build kernel is the one to blame why its not working. Reading through the topic, some of you got it working again by flashing an old kernel. How can i do this? Can someone help me, please?
[Nextbit Robin] Prospero.X-3:
I also wanted to get NFC working in order to be able to use Android Pay (which has just been rebranded to Google Pay). I thought I'd worked out the source of the issue in the Omni device tree and was about to build the ROM myself to test my fix, but due to the massive size of the sources download decided to try flashing this kernel instead. This fixed the NFC, in that the option in Settings can be enabled and disabled fine. I found that pairing with my Bluetooth speaker using NFC worked, but I couldn't get Android Pay or Android Beam working (the phone would just do nothing when held to the terminal in the case of Pay, or another device in the case of Beam). According to Magisk my device passes SafetyNet, and I had no issues setting up Android Pay, so I have little idea what could be preventing it from working. I did however find someone else having the same issue on Lineage a while ago. According to the thread this was fixed in a later LOS build.
[Nextbit Robin] NurKeinNeid:
I am not familiar with Android Pay but maybe it is due to release type. Usually, Roms are published as userdebug for better bug fixing. Did you try the official PA? I think the Paranoid guys publish user builds instead of userdebug.
[Nextbit Robin] Prospero.X-3:
Hey. Thanks for the kernel and sorry for the late reply. From looking at the PA thread it seems they have exactly the same problem, except that user says that Android Beam between devices is working (maybe I just need to test more). I wasn't able to confirm their buildtype, but I'll ask in that thread if I really need to find out. Right now LineageOS 14.1 is the only ROM where I know Android Pay is working, so I will try to find out what they are doing differently.
[Nextbit Robin] javelinanddart:
https://review.lineageos.org/#/c/176380/
[Nextbit Robin] Prospero.X-3:
Thank you very much! I will resume my download of the source tree (40 GiB so far...) and build Omni with both that change and my likely fix for NFC being totally disabled. It will probably have to wait until after exams though, as I'm unable to focus on this currently.
[Nextbit Robin] Prospero.X-3:
Does anyone have any idea how to fix the bootloop this ROM sometimes gets into? Today I shut down my phone, and when I tried to power it back on again it shut down during boot. Since then it displays the boot animation indefinitely. This has happened to me twice now, and having to manually copy out important app data files in recovery and then restore a nandroid is quite irritating. I have attached the console-ramoops - it doesn't look very happy.
[Nextbit Robin] /root:
On Omni, the bootloop happened only twice and both times I had to do three reboots to fix it. Odd behavior.
[Nextbit Robin] Prospero.X-3:
Does anyone know why an obscure game on the Play Store is installed as a system app on this ROM? I first noticed it in Magisk Manager - it doesn't show up under Apps in Settings. The apk can be found in /system/app/EggGame/. Extremely odd.

EDIT: after some searching it was added in this commit as "Easter fun". Still an extremely odd decision.
[Nextbit Robin] /root:
[MENTION=6656408]Prospero.X-3[/MENTION]

Nice find. Never noticed it.

That indeed is very odd.
[Nextbit Robin] Gandalf:
#imback
[Nextbit Robin] ytsejam1138:
Terrific News.
[Nextbit Robin] pixLzd:
wooohoooo!!
[Nextbit Robin] sabresfan:
Flash SuperSU in recovery. I used 2.79
[Nextbit Robin] telmob:
Got it! Thanks! :)

I really like how you don't need to press the power button to unlock the phone. Works everytime (well... it did. Not so much right now). This rom is really good. Faster than cyanogenmod. I only wish it had the option to chose wich apps start at boot.
[Nextbit Robin] telmob:
Does this nightly build support OTA updates?
[Nextbit Robin] valhallen.282:
Quick question. Anyone facing GPS locking issues?
[Nextbit Robin] sabresfan:
Mine locks in on my location with google maps. I changed my NTP server using faster GPS. I do this on every rom I flash.
[Nextbit Robin] pintasmapila:
Tested with Maps, Waze and Here. Working fine. It locks accurately without any noticeable delay.
[Nextbit Robin] modernbummer:
Anyone else experiencing a settings force close when trying to access developer options?
[Nextbit Robin] Nicholas6706:
Installed the 12/25 build and miscellaneous is taking up 3x more battery than the screen. Not exactly sure what the cause is. Also, developer's options force closes the settings app as previously mentioned.
[Nextbit Robin] telmob:
Yep. It's crashing.
[Nextbit Robin] shaggy5991:
I'm not able to get the camera working on the latest build anyone have it working yet keeps saying unable to connect for me sadly.
[Nextbit Robin] sabresfan:
Working fine for me. I use snap camera as well no issues so far.
[Nextbit Robin] shaggy5991:
If you don't mind me asking did you do a clean flash or dirty and what Gapps link if possible? TWRP? I clean flashed from the stock ROM I've been using with one atemp with recommend Gapps and once with open Gapps and I tried multiple camera apps.

---------- Post added at 03:54 AM ---------- Previous post was at 03:53 AM ----------

Also I flashed super su for 7.1 immediately after installing
[Nextbit Robin] sabresfan:
I always clean flash. I use open gapps pico the latest available and SuperSU 2.79.
[Nextbit Robin] Nicholas6706:
Also, it seems like the always on fingerprint scanner is quite unreliable and usually stops working after the device has been off for a while, perhaps the service is being killed.
[Nextbit Robin] shaggy5991:
Odd I flashed it the exact same way as you but no camera I'll try it again tomorrow after another clean flash
[Nextbit Robin] valhallen.282:
https://github.com/microg/android_packages_apps_UnifiedNlp/tree/master/patches

I got it. [MENTION=3878813]Gandalf[/MENTION] thank you for the Reminder and happy holidays.

Whenever you are back the patch above needs to be in the frameworks section of the ROM for unifiednlp to work.

[MENTION=4467583]sabresfan[/MENTION] Thanks for the reply. I should have mentioned that I am not using GApps at all. Since Omni comes with signature spoofing I prefer MicroG the Foss version of GApps.

EDIT - ANYONE facing camera issues flash 1450updater zip. That was the only thing that solved camera issues for me.
[Nextbit Robin] Gandalf:
For the record -- I have flashed the N beta (1st one, haven't gotten the 2nd one yet) but the betas only include system, boot, and recovery.

The 1450 (last 6.0 release) contains all the partitions and other stuff from the manufacturer, which I have flashed.

If you haven't flashed the latest 1450 FACTORY IMAGE, do it, so we're all on the same page.

Thanks [MENTION=5272042]valhallen.282[/MENTION] for pointing this out :highfive:

I'm going to add us to official weeklies here shortly, before the next batch hits.

In light of that, I need ALL logs for ANY bugs you guys are encountering. Omni has the first public nougat release for robin and I want to make sure it's the BEST release for robin :laugh:
[Nextbit Robin] valhallen.282:
that's thanks to [MENTION=6204913]n76[/MENTION] over at UnifiedNLP

Mine seem to be rather broken. Can't flash any of their Beta builds without softbricking my device.

Had to go back to 6.0 considering the broken location backend. I think I'll try again. Also please note. Exchange services is completely missing from this rom. ExchangeServices.apk (Flashing the 6.0.1 apk from anywhere on the web does not solve the issue. Will try the one that is in the 6.0 rom now and report back. Be great if it is there though. BlueMail for exchange is awful. And k9 does not function with ActiveSync.)
[Nextbit Robin] pintasmapila:
I flashed 1450 stock image. Then i flashed CM14.1 and then OmniRom and OpenGapps Stock. Exchange works nicely. The Nexus Gapps are incomplete. Pixel launcher is not fully working. The only thing i can say is broken so far, is the developer options. I also find the device to lag a bit, but it's still faster than CM14.1 I don't think all cores are working, but maybe i'm wrong. Need to test it further.
[Nextbit Robin] dnp77:
So far this ROM is smooth, only issue for me is developer options. Camera froze once when I opened it from the recent apps screen. I was on stock with stock recovery, and no root before. So I formatted right before I installed this ROM. I went from stock, didn't even spend 5min on it, went straight into recovery and flashed ROM and Gapps. Pretty smooth, pixel shortcuts work on all the Google apps, except the dialer, maybe there's a way to install the Google dialer for that to work, thanks for the ROM, really enjoying it, haven't even installed my go to, Nova launcher

Edit: yep installing Google dialer from the play store did the trick
[Nextbit Robin] EAT_CHICKEN:
This is probably the best ROM I've tried on this phone. Stable, fast, and everything works.
[Nextbit Robin] pintasmapila:
Thank god! :D
[Nextbit Robin] modestos:
bootloop

I have exactly the same problem. I use the Unicornblood Kernel and got a boot loop twice in a month.

Any ideas in fixing this withought full recovery?
[Nextbit Robin] buzzywaw:
Omni with unicornblood looks fine here in my device, try to flash omni kernel via twrp maybe could help your bootloop problem
[Nextbit Robin] pintasmapila:
How is camera focus on latest release? Still slow?
[Nextbit Robin] igjrn:
Does anyone else get random reboot?
[Nextbit Robin] jabashque:
Hi Gandalf, I don't know what happened over the last few months, but we're glad you're back and that you're working on bringing up ether for OmniROM Oreo, at least from what I'm seeing on your personal GitHub account. Thank you for your efforts!
[Nextbit Robin] /root:
How often and when? Does it happen while using or just standby?

I don't experience much of random reboots but happens once in 4-6weeks maybe. Nothing to annoy me.

I do experience weird bootloops though, when I manually reboot the systems the device sometimes goes in a bootloop and only after 3-4 boots it will finally boot in the system. I don't have to do anything but its a bit annoying. This happens once in 4-5 boots maybe.
[Nextbit Robin] igjrn:
Like once every few days. It usually happens while using. I don't get bootloops tho. It randomly restarts but boots right back into the system.
[Nextbit Robin] wpost:
Security updates?

Are there security updates for Omni on Nextbit? The download page (dl dot omnirom dot org slash ether) suggests that the most recent build is from November of 2017. I ask because I'm still on the factory ROM at security patch level April 1 2017, and I am looking for a stable ROM that gets regular security fixes.
[Nextbit Robin] Gandalf:
8.1 is booting. Just fixing up some stuff before posting
[Nextbit Robin] iluvatrix:
Would this be official?
[Nextbit Robin] pintasmapila:
Nice!

Can't wait to try it.
[Nextbit Robin] Michael_Kuhhh:
Thank goodnessss ive been dieing to get Omni on 8.1:victory:
[Nextbit Robin] /root:
For now yes its on 7.1.2 and November 2017 update. This ROM is very stable and worth the switch.

The ROM maintainer was busy I guess and since most ROMs are porting their ROMs to Oreo builds its been difficult for them to provide security updates too . But hes back and is working on 8.1 check this thread now. So a new update is coming which means likely with March or April 2018 security update.
[Nextbit Robin] Gandalf:
Yes it will be official. RIL (IMS and all those goodies too) is working, as well as audio.

Remaining bugs:

- Bluetooth

- wifi

- nfc

- camera

- DSPManager

Made good progress so far tonight

Also FYI I'm testing with Project Fi and AT&T SIM cards.
[Nextbit Robin] ziellziell:
Wow!

Can't wait to try it. Thanks Gandalf
[Nextbit Robin] Gandalf:
This also now uses my bare bones kernel. It deep sleeps like a baby ?
[Nextbit Robin] bdeals:
Wow, less than a percent per hour.. that is impressive.

Can't wait

thanks
[Nextbit Robin] Gandalf:
It should work with 7.1 but I haven't tried it. The only real difference is it has the binder changes

Update:

Just camera left
[Nextbit Robin] jabashque:
please name it after a lotr character thanks
[Nextbit Robin] AEmma:
Can someone shed some light as to which one is the stablest of all Omni builds? I've been on the November build for a week now but it's been a bit glitchy for me. I've had a lot of random reboots and a bootloop as well. Help appreciated :)
[Nextbit Robin] earlgrey_44:
I've used the Nov build since it came out, until the last week or so since functioning oreo builds appeared. Not one reboot or bootloop in that time. So, are you worried about an unstable ROM or something else?
[Nextbit Robin] /root:
Your update now feel like a tease. I am not complaining.

Can't wait for the OTA to pop up.
[Nextbit Robin] oshane126(jamaican):
I suddenly realized that 2 of my cpu cores have come to a sudden stop and only 4 of them are running. Usually when i checked cpu z or any cpu monitor app i would see all cores active. Is it that they have stopped completely or is there a way to turn them back on? Also my phone is a bit sluggish too and my geekbench scores are very low. Is there anyone else experiencing this problem?
[Nextbit Robin] jabashque:
[MENTION=3878813]Gandalf[/MENTION] would it be possible for you to create a chat group of some sort for testers or something?
[Nextbit Robin] Gandalf:
Sure. I'll create a Telegram group and post a link.

Have fun with the first test

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

Known last 2 bugs:

- Can't enroll fingerprints

- Torch tile doesn't work