yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] valhallen.282:
The one in general is a nightly. More importantly is unofficial. And erm no one knows what changes that Dev makes.

This is the official and a weekly and has an active Dev from the OmniROM team.

But I thought the title said all of that.
[Nextbit Robin] laidbackcloud:
really? when I use it , it was always searching for my location, it would find and as soon as I start driving it would lose signal again(location).
[Nextbit Robin] jimmyzyx:
Never happened before. Just do a clean flash.

---------- Post added at 02:51 PM ---------- Previous post was at 02:49 PM ----------

Not really sure how to do that? Can you advise? Tho it's been a couple of days since I last used it.

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

My data was also on as well, so perhaps it was using that to locate me.
[Nextbit Robin] substanceneil:
GPS/Google Maps navigation working perfectly for me. The phone does get hot, but I usually am QC2 charging while navigating and assumed it was the charge causing heat.
[Nextbit Robin] Gandalf:
Those aren't official, supported, or endorsed whatsoever by Omni. The real question is, how are those builds different than official? ?
[Nextbit Robin] jimmyzyx:
Exactly what I'm thinking.. why it's necessary to have those unofficial if official is more than capable...
[Nextbit Robin] Jushten:
Going to be flashing from Cyanogenmod 13.0, how should i go about doing this? Do I have to flash back to the stock Nextbit OS first or can I just wipe my current version of Cyanogenmod and flash Omni 7.1.1 and Gapps?
[Nextbit Robin] ChackoM:
I would advise flash stock cause you need the 1450 partitions. You don't need to boot however. Just flash it, then flash TWRP, format data, wipe system data cache Dalvik, then flash Omni then Gapps.
[Nextbit Robin] vibranze:
I just flashed the official weekly Omni last evening, found the battery drain is quite bad, left it at 64% before I went to sleep, wifi/data turned off and in the morning 7am, it left 46%. Idle drain from EXKM is about 3.6% and wakelock detector reported 92 wakeup time. I'm going to flash 0228 Homemade later. Thanks.
[Nextbit Robin] valhallen.282:
If you flashed it last evening and left it to sync is it possible that the sync and initial setup could be causing it? I have full GApps on the device. I left it nine hours ago with 51% battery. I just woke up is currently at 47%. In the meantime there have been at least 50 messages from multiple accounts. That's with ringers and alarms. Which seems fair. My one plus lost the same amount and they're basically clone devices. Could you post logs? Or wait 36 hours for all the initial selling in to finish and then post logs?
[Nextbit Robin] vibranze:
Hi, thank you for the suggestion. The phone is actually has no SIM card so you can considered it as it's in aeroplane mode, nevertheless I will wait for another day to let it stabilize.

Is Homemade version suitable to use as daily driver?

Thank you.
[Nextbit Robin] valhallen.282:
Hmmm maybe I should have asked a few questions. Before jumping the gun. Apologies. Please post a log. No Homemade are generally Guinea pig builds. Plus you cannot flash them over weeklies. And vice versa. More importantly if it's something real important you'll get a teeny tiny upgrade via Delta updater. Weekly is the more stable one. Try a fresh clean flash? I don't have that konda drain with and without GApps. Even on testing build. So something might be going on.

You need root and logcat app. That's the easiest way. Something like MatLog. Install root. Restart device. Open MatLog. Grant permissions. Recreate the problem you faced. Save log as text to device. Post it here. Sorry for not replying earlier.
[Nextbit Robin] vibranze:
I attached the screenshot from EXKM and WLD here. It just finished charging, let's see how it goes. Thank you.
[Nextbit Robin] kuduku:
hawktail or glassfish ? Which profile is giving best battery life on this ROM . No gaming just calling , social media and music

Edit -where is option to disable TOUCHBOOST in this ?
[Nextbit Robin] pseudonoise:
A few Observations and Questions

First I'd like to thank Gandalf and everyone else involved for working so hard to produce such a stable ROM.

I have a few of observations-

After clean installing the the 7.11-20170228 weekly (and rooting with Chainfire's SR5 v2.78 SuperSu) I encrypted my phone. This had only a minor perceptible impact on performance. However the latest TWRP 3.0.3 fails to decrypt the encrypted partition.

Is there a solution ?

Does this mean that I will not be able to take incremental updates ?

Will I have to do a full re-install with every weekly release ?

I'm also not sure if the A57 big cores ever come out of sleep - I've looked at both the outputs of AIDA64 and CPU-Z which indicate they are sleeping. This is only of academic interest as I'm very happy with the speed and smoothness of the ROM.

The Automatic Rules for Quiet Hours doesn't turn on automatically as normal in "Do Not Disturb" - this is a feature I use all the time so I'd be most grateful for advice on how to get this to work properly.

My battery life seems comparable to the Stock MM Nexbit ROM.

Thanks again for your support
[Nextbit Robin] willyboi:
Hey! I just wanted to thank [MENTION=3878813]Gandalf[/MENTION] for everything he does! This ROM is awesome, smooth, and by far the best nougat ROM for the Robin! Thank you!!
[Nextbit Robin] valhallen.282:
Could you please post a log cat of the failure to activate quiet hours?

Odd both sets seem to come online for me. Do you have screenshot of the sleepy cores?

Yes, TWRP needs to update to 3.0.4.0 for proper decryption to work and that's currently a WIP.
[Nextbit Robin] zzromanzz:
I got freeze and reboot with 2/28 that i had never in 2/19.
[Nextbit Robin] Kaleshwar:
Yeah me too but it's minor. A reboot fixes it.
[Nextbit Robin] demeez:
I only installed it last night but so far it's running really smooth, definitely enjoying it over the Nougat beta that still has room for improvement. That being said I'm wondering if anyone experiences their cellular signal bouncing around compared to stock. Never had anything but full strength on stock and looking at my gf's Robin that's stock hers stays full strength while mine bounces up and down from time to time. Thanks.
[Nextbit Robin] jimmyzyx:
If by bouncing around, you mean it can't locate a signal for about 30 sec after you reboot, it happens. Otherwise in the past week, i've lost signal once for a bout 10 sec before getting connected back again. This is with AT&T's roaming towers.
[Nextbit Robin] talkingduck:
Yeah, I've had this too. In Australia on Telstra. Before on stock and beta, signal was rock solid.

One other issue I've had for the first time using this phone is that people say I'm unclear on handsfree. Again, on stock and beta never had a problem.

Nonetheless, huge thanks to gandalf for all his awesome work.
[Nextbit Robin] substanceneil:
I have noticed less LTE signal in the stake bar a few places than before, but I still get good speeds.
[Nextbit Robin] Kaleshwar:
Same here. But it's works like normal.
[Nextbit Robin] Gandalf:
Do not use the homemade builds anymore, please. I've removed them from my server for a reason. Weeklies are perfectly stable.

Regarding your battery drain,,. WTF is EXKM? I have superb idle drain with sim in.
[Nextbit Robin] Kaleshwar:
Ex Kernel Manager (EXKM)
[Nextbit Robin] goaldispirited:
Did you do anything new? I don't have good idle drain.
[Nextbit Robin] crian:
Is the charging led working for you guys? Mine does nothing.

I'm on 28.2. weekly build with clean flash.
[Nextbit Robin] vibranze:
Do we have Energy Aware Scheduling (EAS) in Robin's kernel? Thank you.
[Nextbit Robin] jimmyzyx:
It always worked, just on the back.
[Nextbit Robin] jimmyzyx:
Not sure if this is an issue specific to the ROM, as I've experienced it since I got the phone. But I'm unable to update or download apps from the app store via cellular data, but wifi is fine. There are no error messages. It just shows "downloading" as normal but never actually downloads. Let me know if someone else is experiencing the same.
[Nextbit Robin] crian:
For me it is working fine.

Have you checked your APN?
[Nextbit Robin] jimmyzyx:
Never touched it, default as always, but used to work
[Nextbit Robin] substanceneil:
Play store downloads over cellular data are working fine for me.
[Nextbit Robin] jimmyzyx:
https://productforums.google.com/forum/#!topic/play/cwWBr-tuF08

Seems like many people are having this issue for Android 7.1.1 with roaming.. Called google and the tech support is useless as usual. After an hour of wasted time holding so they can tell me to clear cache and data, they said they can't do anything and needs to refer me back to stock manufacturer. As it stands, the devs for this ROM will be my best bet at fixing this issue...
[Nextbit Robin] govno64:
Camera not working "Camera error - Can't connect to the camera."

Hi, just purchased the Robin, installed TWRP, flashed this rom, installed gapps nano and SU, but the camera isn't working. When I open the camera app, I get the error message "can't connect to the camera."

I have attached the logcat (not sure if it's helpful) as well as a photo of what the screen looks like. I see from searching this post that some other users have had this issue, but I can't seem to locate a solution.

Also, when I plug the phone into my computer and enable MTP file transfer (from the notification bar), my device isn't recognized, though I'm pretty sure I have all the correct drivers. I installed the robin drivers, and my nexus 5x connects to my computer no problem.

FWIW, I also installed the official 1450 update before doing any of this, though when I downloaded it, the built-in fastboot/adb (in the 1450 zip) didn't see my device, but if I manually specified the device -i 0x2c3f as instructed in the first post on the second page here [ https://community.nextbit.com/t5/fo...age/board-id/GeneralQA/thread-id/9411/page/2] it was able to flash, which booted and appeared to work properly and had a working camera (robin stock marshmallow).

Any help?
[Nextbit Robin] Kaleshwar:
Thts very odd.
[Nextbit Robin] ChackoM:
Just received notice of new weekly. What are some of the changes [MENTION=3878813]Gandalf[/MENTION]?
[Nextbit Robin] Saythis:
You need to use either Magisk or SuperSu 2.79 SR3.
[Nextbit Robin] ACViperPro:
I had that problem too before. Unroot your phone in SuperSU and flash magisk or supersu 2.79 SR3 using TWRP. You should be good after that :)
[Nextbit Robin] DECHTECH:
Can't install the latest weekly build. TWRP reports that the system is 'read only' despite it not being set to 'read only'. Here is the error that occurred: ApplyParsedPerms: chown of /system/bin/backuptool.sh to 0 failed: Read-only file system

ApplyParsedPerms: chgrp of /system/bin/backuptool.sh to 0 failed: Read-only file system

ApplyParsedPerms: chmod of /system/bin/backuptool.sh to 493 failed: Read-only file system

ApplyParsedPerms: removexatter of /system/bin/backuptool.sh to 0 failed: Read-only file system

set_metadata: some changes failed

Updater process ended with ERROR: 7

So confused as this WAS working before...

EDIT: I just decided to clean flash instead of dirty flashing. All I wanted to do is keep my data! Anyway, that solved the problem.
[Nextbit Robin] psychoTR2:
Installed about and hour or two ago. So far, its running smoothly. Nothing really to report. What changes came with this new build?
[Nextbit Robin] crian:
Check Gerrit or GitHub for changes
[Nextbit Robin] pseudonoise:
Weekly Update and Encrypted Phone

Hello I have a Robin which I have encrypted currently running the 28/02 weekly.

I received a notification that a new weekly was available and I downloaded it and attempted to flash it. (previous posts say it should work)

It rebooted into TWRP 3.0.3 and requested my encryption password to decrypt and mount my data partition.

Unfortunately TWRP currently doesn't support the decryption of encrypted 'phone so I had to cancel the decrypt operation and try to install the new weekly zip - however as the OMNI update appears to be on the encrypted (un-decryptable) data partition it is "invisible" to TWRP.

Has anyone found a way of updating OMNI without removing encryption (which will result in reinstalling all my apps and configuration) on a encrypted 'phone ?

Thanks,

Pseudonoise
[Nextbit Robin] crian:
The latest version of TWRP is bugged. Flash 3.0.2-1 and it should work.
[Nextbit Robin] pseudonoise:
Updating with TWRP and Encrypted Robin

I've tried TWRP 3.0.2.1 as suggested and that also fails to decrypt.
[Nextbit Robin] crian:
Have you tried to flash it manually?
[Nextbit Robin] pseudonoise:
Updating with TWRP and Encrypted Robin

I've tried to update using TWRP by hand but the update zip is unavailable as it is stored in the encrypted data partition. I've considered copying see where else in the file structure but I'm unsure if this is wise.
[Nextbit Robin] Saythis:
I believe he was referring to fastboot flashing the TWRP image.

Located here:

https://dl.twrp.me/ether/
[Nextbit Robin] Tautvydas:
Excellent rom. Fast, stable, all working. Don't want to sound spoiled, but any chance on getting pixel navbar animation on omni rom? Or is it possible via non-xposed way, since it's only WIP for nougat.
[Nextbit Robin] substanceneil:
Try booting into twrp and using "adb push newweekly.zip /sdcard/" command to copy the new weekly from dl.omnirom.com. The file will not be encrypted and you should be able to flash it.

I think I was flashing ota using delta while encrypted, but I am not encrypted at present and cannot reconfirm.
[Nextbit Robin] pseudonoise:
Sucess Updating with TWRP and Encrypted Robin

Thank you for your help using ASB push and TWRP I was able to update to the latest weekly. I had to re-root using the same technique.

The update file seems to have been deleted after the installation which is good news :)

Again thanks for the help - It is a pleasure to be allowed to participate in such a helpful forum.

Pseudonoise
[Nextbit Robin] RaiderX303:
Seems to be the fastest nougat rom so far for the Robin, only issue i've found is USB comes up as unrecognised device when connected to windows, also the 2 performance cores don't seem to get any use.

Edit: There also seems to be a little pop when sound stops after short sounds like key presses
[Nextbit Robin] DECHTECH:
+1 I have to use ADB push/pull to transfer files xD
[Nextbit Robin] Kaleshwar:
Head over to nextbit.com and get the driver installation from the community.
[Nextbit Robin] DECHTECH:
I did.... That was the first thing I tried before using ADB push and pull to get what I needed done.
[Nextbit Robin] Kaleshwar:
Did your computer recognize the device then?
[Nextbit Robin] DECHTECH:
No. I've tried disabling ADB, I've tried different USB C cables, different ports, computers and with/without drivers.

It 'sometimes' comes up as a MTP device. I can't do anything with it though.
[Nextbit Robin] kuduku:
See a improvement in sleep and standby on latest nightly , Dirty flashed
[Nextbit Robin] Kaleshwar:
I had the issue before but I Uninstalled and reinstalled and it worked.
[Nextbit Robin] goaldispirited:
[IMG="battery life"]https://dl2.pushbulletusercontent.com/NK85s9b7CZ8B14FvqekXzz9kOcWgSngO/Screenshot_20170307-100514.png[/IMG]

The battery life isn't very good. Here you can see, 3% battery drain per hour with the screen off.
[Nextbit Robin] kuduku:
Try with stock governor profiles .
[Nextbit Robin] goaldispirited:
It's actually stock. I'm only using the battery monitor of the app.
[Nextbit Robin] laidbackcloud:
I did a clean flash and gps is working fine.
[Nextbit Robin] Gandalf:
Yea I need to look into that sound. It's audio hal or the amplifier so it shouldn't be difficult to narrow down. Disabling sound on touch stops it though.

I don't use Windows so .. maybe you need to install the Robin drivers from nextbit's site.

I'm going to just use the prebuilt GPS Hal again from stock since it was completely reliable with no drifting until I figure out the GPS config file changes we need. I've been working on our server's lately (check g+) and now I'm going to be updating ROM base to android-7.1.1_r24 (March security update)
[Nextbit Robin] pintasmapila:
There's one thing that still bugs me from time to time.

When i have the 'Wake and unlock' option selected, to unlock the phone with the screen off, i press the button to lock the phone and i have to quickly remove my finger, or else it gets unlocked almost instantly.

Is there a way to disable the fingerprint scanner for a couple of seconds, immediately after the phone is locked?
[Nextbit Robin] matthew5025:
A better way would be the way google implemented it; that is only unlocking it after the finger is lifted from the sensor.
[Nextbit Robin] pintasmapila:
Yes, that would be perfect. :)
[Nextbit Robin] talkingduck:
Is there a way to re-implement the charging light on the bottom? The charger in my wall socket sometimes slips out, so it's easy to see if it's charging or not when I walk past.

I thought someone had said it was in the settings but I am unable to find it..

thx!
[Nextbit Robin] jimmyzyx:
That's not yet implemented.
[Nextbit Robin] Saythis:
Only the back lights unfortunately.
[Nextbit Robin] Gandalf:
Screen-off fingerprint scanning can be enabled of disabled is settings. I made no modifications to be code other than adding that setting check, so this is how Google implemented it.
[Nextbit Robin] ToHellWithGA:
The performance on Omni is leaps and bounds ahead of Lineage OS, especially with respect to battery use. Is there a toggle somewhere in settings to activate ambient display for notifications when the phone is removed from a pocket or picked up?
[Nextbit Robin] goaldispirited:
How is your battery life like?
[Nextbit Robin] jimmyzyx:
No, its not available on this ROM. Again I and many have confirmed that this is hands down the best ROM in terms of performance and battery life, but definitely not the best features wise.

---------- Post added at 02:15 AM ---------- Previous post was at 02:15 AM ----------

I can easily last 2 days of normal use per charge.
[Nextbit Robin] talkingduck:
I use gravityscreen. https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree for when i take my phone out of my pocket... or run my finger over the proximity sensor to wake it up...
[Nextbit Robin] pintasmapila:
Is there any way to remove the default launcher's search bar?
[Nextbit Robin] Kaleshwar:
Just putting this out there. It seems the A57s just shutdown just after my first boot.
[Nextbit Robin] Saythis:
Mine shut off until heavy load. They're extremely inefficient.
[Nextbit Robin] jimmyzyx:
My substratum started force closing today every time I open it. I was able to use it fine and install themes yesterday, but I haven't been able to open it since. Tried reinstalling and rebooting. Anyone else having this issue?
[Nextbit Robin] Saythis:
I believe there was an update to the app recently
[Nextbit Robin] jimmyzyx:
You think the recent update is causing the force close?
[Nextbit Robin] Saythis:
It could be. The only issue i've had was it forced closed ur first time opening it when it began compiling a huge theme, but after I reopened it, it fully compiled and installed the theme.
[Nextbit Robin] Gandalf:
Go to settings > search "gestures"

Not being used until NEEDED is one thing, not being used EVER is another.

We will most likely be merging native OMS tonight or shortly after, just waiting to confirm March security merge is OK (I'm building it now).

Everyone still complaining about performance #facepalm
[Nextbit Robin] jimmyzyx:
Thanks Dev. I noticed that Lift and check feature isn't on my phone, perhaps thats a new feature for the next release thanks!
[Nextbit Robin] pintasmapila:
I amso don't have lift to check option.

I will not complain about performance, that's for sure. It's fastest that it ever was. Thanks!
[Nextbit Robin] laidbackcloud:
Im happy brother, but if theres room for improvements go for it :)
[Nextbit Robin] Gandalf:
Always room for improvement, it just takes time :) I just went and played ingress for 2 hours and it worked perfectly fine. Better than my Nexus 5X. I also am using a home build with prebuilt GPS, which will be in the next weekly build along with the march security and caf updates
[Nextbit Robin] DECHTECH:
Man I have been using the latest build of the rom and found the performance crazy! Little to no stutters and app loading time is also great! Battery life is more than good and everything seems to work fine. I have no complaints about this rom for the time being and can't wait to see what you do next! Thank you for taking so much time and effort into this rom. It makes me feel much better about purchasing this phone :)
[Nextbit Robin] Gandalf:
I would recommended moving to official, there are no changes unique to the homemade build anymore, and I'm not going to push any more homemade builds since we have a completely stable base now. Thanks :good:

I'll try to get ambient display pickup sensors working by next weekly but I just bought Blackwave on steam and have been in pirate naval warfare all day after work :laugh:
[Nextbit Robin] DECHTECH:
Oh soz, I meant I am on the latest 'official' build of Omnirom haha.
[Nextbit Robin] RaS_KoR:
The version available on the Play Store (2017-03-07) works at first start but didn't ask root permission and always FC after, the version 563 works well.
[Nextbit Robin] Gandalf:
OMS is merged and will be in the next weekly.
[Nextbit Robin] Jacobwitt:
Cant wait for the update Sunday, Anyone get Assistant w/o using a patcher via roll-outs? Just wondering if I need to patch anymore when it officially rolls out.
[Nextbit Robin] Kaleshwar:
Awesome!
[Nextbit Robin] Saythis:
I've been using Opengapps to enable Google assistant. It has an option on the last page that throws a line in the build.prop to enable it.
[Nextbit Robin] DECHTECH:
For those who don't use Opengapps. The google play store has an app that is called 'get assistant' I think. That'll do the exact same thing.
[Nextbit Robin] demeez:
No, more that the signal drops from full strength to half and on the rare occasion drops off for a second. On stock I have full strength at all times while on this rom it can't seem to hold a constant full strength signal.
[Nextbit Robin] jimmyzyx:
What carrier are you with? I'm roaming on AT&T and have perfect signal
[Nextbit Robin] RaS_KoR:
[MENTION=4468902]Saythis[/MENTION] , [MENTION=7084266]jimmyzyx[/MENTION] : Lastest playstore version (604) works pretty well.
[Nextbit Robin] jimmyzyx:
It still FC for me.
[Nextbit Robin] Saythis:
Tried clearing the app data/cache?
[Nextbit Robin] jimmyzyx:
Yes. I've done that and reinstalled, and can't get it to not FC.
[Nextbit Robin] JXRT190:
The ROM works really well for the most part, but I keep having this issue where the in-call UI won't show up for me at all. I call somebody from the phone app and the call starts, but the in-call UI doesn't show up. I have to use the accessibility setting to end the call with the power button. I also have to hold the phone away from my face so that I don't hit something with my ear because the screen doesn't turn off when the call starts. I also can't answer calls because of this. I've tried re-installing the ROM, updating everything, re-installing Gapps, I don't know what could be doing it at this point.

EDIT: I finally figured out the issue. For some reason, it didn't set Phone as my default Phone app. I went through so much work for nothing hahaha. Sorry for the false alarm.
[Nextbit Robin] Gandalf:
Oh man.

99% of posts are user error. For my sanity PLEASE do some searching and Googling before posting.
[Nextbit Robin] pintasmapila:
That also happened to me several times after flashing. Not sure why, maybe it's because I didn't make a clean flash.
[Nextbit Robin] JXRT190:
I'm not sure either. I clean-flashed multiple times.
[Nextbit Robin] Gandalf:
you need to go to settings > apps > default apps and choose whichever Phone app you will be using as default here. this is not a rom problem, but user error.