yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] ACViperPro:
Is there a way to see the battery life of a Bluetooth device on this rom? If there isn't a way, maybe in the future you can add this feature.
[Nextbit Robin] Gandalf:
Please install the latest weekly from dl.omnirom.org/ether

Lag and stutter is fixed for me with that build.
[Nextbit Robin] ChackoM:
This build is much better, thanks man!
[Nextbit Robin] goaldispirited:
Do you mean omni-7.1.1-20170226-ether-WEEKLY.zip? Just tried it again, same amount of lagginess.

---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------

Also, advanced reboot not available on this weekly.
[Nextbit Robin] Gandalf:
Clean flash it please and let me know. It's fine here after a clean flash.
[Nextbit Robin] jimmyzyx:
Advance reboot has always been available on this ROM.

Settings -> Buttons -> Power Menu -> Enable Advanced Reboot
[Nextbit Robin] jimmyzyx:
QUOTE=goaldispirited;71204655]Do you mean omni-7.1.1-20170226-ether-WEEKLY.zip? Just tried it again, same amount of lagginess.[/QUOTE]

On the latest 0226 version of the ROM, I always clean flash. Still noticing poor performance compared to before. I know you mentioned that benchmarking applications are not reliable, but its results are backed by actual performance reductions. Just wondering what are the changes this time to cause such decrease in performance leading to significant worse benchmark results?

P.S I am able to boost the performance a little using a custom kernel but still nowhere near as good as before
[Nextbit Robin] Gandalf:
I will post a test build for you shortly. Please let me know if it's any better.

I re-enabled cpuset since in my testing the past month it has been fine after some tweaking. Apparently not.

Unfortunately to properly test if this is the issue I will need you to clean flash a test build since cpuset is in the frameworks as well as kernel.
[Nextbit Robin] jimmyzyx:
Thank you. Appreciate your dedication to this product.
[Nextbit Robin] Gandalf:
Please try this build

https://whatley.co/omni-7.1.1-20170227-ether-HOMEMADE.zip
[Nextbit Robin] jimmyzyx:
Traveling for work tmr, will definitely give this a try tmr evening and report back. Thank you.
[Nextbit Robin] DECHTECH:
I will also test for you ;)
[Nextbit Robin] Gandalf:
Yes, this is (clearly) public so please report back :good:
[Nextbit Robin] goaldispirited:
https://source.android.com/devices/tech/power/performance.html

Do the changes you made correspond to this?

Do you have a commit diff that I can check out on what you changed? Just curious. Am a dev and this is interesting.

-- Found it: https://github.com/omnirom/android_...15c1046#diff-18112d8ea619a9b5e78728107055646b
[Nextbit Robin] Gandalf:
That is what is in weekly. I simply reverted cpuset changes here and in kernel for test build. For some reason cpuset is killing all performance. I thought I had it figured out but clearly I am wrong (or I just missed something when I pushed to gerrit and submitted)
[Nextbit Robin] goaldispirited:
And on your own phone? Did it work?
[Nextbit Robin] DECHTECH:
Everything seems to check out on the test build. UI doesn't lag or stutter nearly as much now, apps open faster, etc. From what I read, isn't "cpusets" supposed to solve/boost performance? (Don't quote me on this I'm not a dev haha) If yes. Then that's pretty odd :confused:
[Nextbit Robin] nbferr:
Can confirm that clean flashing the 26/02 build from the omni website fixed most of the lag and stuttering for me.
[Nextbit Robin] jimmyzyx:
Still haven't tried the test build yet. On the way traveling for work, and using the GPS. Notice the phone heating up dramatically, and battery is very very poor, showing 2 hours left after 30 minutes from 100% to 73%. Hopefully the test build will be better.
[Nextbit Robin] talkingduck:
My first foray into Omni (after using the beta) was great on the 19/02 build. When I updated to the 26/02 build (through the built in updater) I experienced the lag and stuttering. I had not done so on the 19/02.

So I reflashed 19/02 and lag/stuttering has gone!
[Nextbit Robin] DECHTECH:
The test build is great! I feel like it's even better than the 19/2 build!
[Nextbit Robin] jimmyzyx:
Thanks for the heads up, will try tonight when I get home and update the benchmark log for y'all :good: looking forward
[Nextbit Robin] Gandalf:
I missed the actual cpuset configs -_- I was using the original from cyanogen.. when I tested over the past few weeks I was using params from Nexus 5X. New build going up with those params. Can be dirty flashed over HOMEMADE only
[Nextbit Robin] jimmyzyx:
Beautiful. Do you think this will happen in the next couple of hours? If so I'll just wait for that.
[Nextbit Robin] Gandalf:
https://whatley.co/omni-7.1.1-20170227-ether-HOMEMADE.zip
[Nextbit Robin] substanceneil:
Can get 0227 homemade you just posted be dirty flashed over the 0216 homemade?
[Nextbit Robin] Gandalf:
No, I started signing my HOMEMADE builds with personal keys on 0226.

Anyway it's fixed so I'm recommending everyone go back to WEEKLY 0227 once it posts. Building now on Jenkins. Thanks.
[Nextbit Robin] ChackoM:
So all the changes that were added to the homemade builds are being transferred to the 0227 build? Will this be a delta update if I'm on the 26/2 build?
[Nextbit Robin] Gandalf:
Yup. You should be prompted for an OpenDelta update shortly.
[Nextbit Robin] ChackoM:
*Cue clicking the Check for Update button every 2 minutes*;)
[Nextbit Robin] DECHTECH:
Will the build be posted to http://dl.omnirom.org/ether/ ??

Or do i have to flash the 26/02 build and go through OTA??
[Nextbit Robin] Gandalf:
It will post there and will also appear as OTA for those on weekly builds
[Nextbit Robin] goaldispirited:
Don't see it yet. Any clue when it will be done?
[Nextbit Robin] DECHTECH:
Still not up :(
[Nextbit Robin] Gandalf:
Fixing Jenkins problem. Please be patient
[Nextbit Robin] DECHTECH:
It's up now. Thanks for your awesome support! Really appreciate it!
[Nextbit Robin] goaldispirited:
Doing a clean flash. Will report back with results

---------- Post added at 08:30 AM ---------- Previous post was at 08:14 AM ----------

Clean flash, there are still micro stutters.

Edit: Not micro stutters, just general stutters.

Questions:

1) Is there touchboost enabled in this rom?

2) Is there a dedicated core for user interaction specified in cpuset?
[Nextbit Robin] DECHTECH:
Woah there, I was just coming back to report the wonderful experience I was having with the latest weekly. Having great performance after a clean flash. The phone is also really hot as I am downloading installing charging and running benchmarks at the same time too! Still getting great performance haha.

You can probably disable touch boost with a kernel editor of some sort.
[Nextbit Robin] Gandalf:
Look at the code

Can you describe what you're doing when experiencing these stutters?

You seem to be the only person consistently having problems
[Nextbit Robin] DECHTECH:
Too true haha.
[Nextbit Robin] goaldispirited:
:D I clean flashed it the 1 more time and it works very well!

This is close to perfect now. BTW, does anyone know how I can get HDR+ on Google Camera?
[Nextbit Robin] DECHTECH:
Haha told you! I'll have a look with HDR+. I don't use the camera often so I don't really know. Happy to help though.

From quick research the best way to get it is via a google camera mod named CameraNX, trying now: https://xdaforums.com/nexus-6p/themes-apps/mod-camera-nx-v4-google-camera-zsl-hdr-t3494435 You can download the experimental version of the app that supports other phone models other than the 5X and the 6P

Let me know if there is another way to get it working.
[Nextbit Robin] 02busa:
New here in the Robin forum, but I have to say this is by far the best ROM I've tried for the Robin so far. I bought the Midnight version as a spare phone brand new off eBay for $140 .

I didn't care for the factory Nextbit OS, so I tried Lineage OS as I've been used to CM. It was a mess, and lag central. So I tried the 2-26 Omni weekly, and it was a lot better; but still had some lag. I've since flashed the 2-28 weekly, and it's been beautiful so far. Very very smooth. Thanks to the Devs, you're doing a great job. ????
[Nextbit Robin] pintasmapila:
A bit off topic, but is there a way to install MigroG (No Gapps) with working blank store with Omni?
[Nextbit Robin] kuduku:
hows the battery life on this compared to stock ?
[Nextbit Robin] jimmyzyx:
If you read the earlier posts or did a search in this thread, you'll see, but I've attached a screenshot. You'll be lucky if you see more than 20hr left ever on stock.
[Nextbit Robin] kuduku:
Have been getting 3/3.5 hours SOT with LTE only data always on,, in stock .

Have been following the thread but with homemade and official builds people have been clean flashing very few have posted battery stats with prolonged usage

Must have missed yours
[Nextbit Robin] jimmyzyx:
No worries. Regardless, battery life is much better on this ROM compared to stock. Performance is incomparable, as it makes stock look like a joke.
[Nextbit Robin] valhallen.282:
Yes there is...

1) Download the latest testing MircoG from their site. Plus the latest Blank Store. I suggest getting FDroid as well.

2) create two individual folders one called MicroG for the GMS all and Phonesky for the Blank Store all.

3) CLEAN FLASH Omni.

4) mount system in TWRP.

5) via TWRP file manager copy both directories you created to /system/priv-app

6) navigate to /system/priv-app chmod0755 both directories and their respective apks. No 0644 didn't work as well.

7) Boot ROM.

8) Go to Settings>Apps>Gear Icon>App permissions>Signature Spoofing and turn both of them on.

Not done yet

9) Find store and MicroG and activate all permissions. Go to Location and switch to anything except device only.

10) open MicroG Self Check and activate Cloud Messaging if you want it. (Suggest you do)

11) Open downloads in app list click hamburger button>Robin navigate to and install FDroid.

12) Update repos. Wait for a minute. Now search and install NLP providers. (use more than one)

13) Under MicroG Go to UnifiedNLP and configure your newly installed NLP's. Now reboot.

14) Login to your Gmail account.

Congrats successful install of MicroG and all services. Have a cookie.

I get 4.5 hours SOT on this ROM. But i have no the gapps used above. And i mainly watch NetFlix and use this device as an expensive GPS unit.
[Nextbit Robin] kuduku:
Are google contacts synced with MicroG ?

I primarily require gmail , calendar and contacts from google . Maps is a plus but not requirement
[Nextbit Robin] nbferr:
This latest patch from today, although it made the phone very very smooth, is also killing my battery a lot faster. Went from morning to lunchtime and had to recharge, while I normally make it to the end of the workday without any problems...
[Nextbit Robin] Gandalf:
Awesome! Glad to hear it's running better for you.

As far as HDR goes.. I need to play with some camera stuff but it definitely works with HAL v1.
[Nextbit Robin] jimmyzyx:
What kind of activities are you doing on your phone? Can you send a screenshot of the battery activity usage?
[Nextbit Robin] dnp77:
Running smooth here on the latest update, I do believe this is the smoothest my phone has been since I purchased it ! Thanks a lot for your efforts ! Do you think we'll ever get any type of navigation bar tweaks like double tap home button to sleep?
[Nextbit Robin] jimmyzyx:
There is no plan in the pipeline for navigation bar tweaks but that is possible for the future. Double tap status bar to sleep is available in the ROM.
[Nextbit Robin] Gandalf:
Just checking to make sure you guys are entering Deep sleep?
[Nextbit Robin] pintasmapila:
I followed every step and i still have fc when doing anything in BlackStore.

I didn't quite understand the steps bellow:

1) Download the latest testing MircoG from their site. Plus the latest Blank Store. I suggest getting FDroid as well.

I downloaded and installed GmsCore, GsfProxy and BlankStore. I also installed FDroid. Is this ok?

2) create two individual folders one called MicroG for the GMS all and Phonesky for the Blank Store all.

I made two folders. MicroG with GsmCore and GsfProxy inside, and Phonesky with BlankStore inside. Is this right? I feel there's something missing here...

Also, i login in BlankStore account with my Google credentials, plus the ID, right? I got the ID from a batch file in my pc.
[Nextbit Robin] Kaleshwar:
Yup
[Nextbit Robin] raddatt:
Do I check like this?
[Nextbit Robin] valhallen.282:
I use BlueBird or something for my email. I just tried Gmail. It works from the looks of it

But quite honestly without actually using full gapps nothing will work (you will be missing the contacts and calendar sync adapters)

Gapps only account for about an additional half hour or so in the form of sync and apps they run.

Let me recreate it a little longer ->

1) download this testing gms app from here Put it in a folder called "MicroG" on your storage.

2) Download this -> Blank Store Put it in a folder called "Phonesky" on your storage.

3) create an android id. Look here if you don't know how -> LINK Copy this plus your userid and password EXACTLY to a safe location. Make sure you use a VALID build.prop preferably from a functioning OMNI rom. [EDIT - IF you are using two step authentication. This userid/password will NEED TO be an "APP PASSWORD" that you have NEVER used before]

4) Install OMNI. DON'T RESTART.

5) Go back to TWRP main screen. Mount> system.

6) TWRP File manager go to sdcard/MicroG copy folder to /system/priv-app

7) go to sdcard/Phonesky copy folder to /system/priv-app

8) Navigate back to /system/priv-app find both the MicroG and Phonesky folders in there and change the permissions for BOTH folder AND APK to 0755 otherwise it wont work.

9) Check permissions mentioned in previous post for signature spoofing. WITHOUT THIS IT WON'T WORK.

10) REBOOT

11) LOGIN to google account AND Play Store account. (google account will show as a "G". Play Store account shows like the play store icon this needs your android id .) YOU NEED BOTH OF THEM.

you should have a working account.

GSF PROXY AND DROID GUARD ARE NOT SYSTEM APPS!!!
[Nextbit Robin] pintasmapila:
Fantastic! Thank you so much.
[Nextbit Robin] Gandalf:
Cool. I'm going to add the overlays so we can see each cluster individually
[Nextbit Robin] jimmyzyx:
Is this a new version of the ROM or a test build?
[Nextbit Robin] valhallen.282:
If it helps. Hit the thanks button! Always a pleasure. Credit to the MicroG guys
[Nextbit Robin] Gandalf:
No more test builds unless absolutely necessary. It's just a huge PITA for everyone with wiping and backing up etc.

I recommend everyone stay on official weekly builds
[Nextbit Robin] tlxxxsracer:
Attached are logs for my issues

Camera not working and closing when swiping to video recording mode

Torch not working

Screen not auto rotating in youtube
[Nextbit Robin] Gandalf:
Thanks. Will look tonight.

Also, I will be replacing the aosp camera with the CAF Snapdragon Camera anyway which reportedly works fine on other caf devices (op3, opo)

Also, reportedly, Google Camera works 100%, so this can be a workaround for now.

How worried about NFC are you guys? I am not worried about it as much as implementing a proper power hal for better power management, performance, and battery saving. I will prioritize my work based on community needs
[Nextbit Robin] sabresfan:
I don't use NFC. I'll try and get a log tomorrow for the proximity sensor when calling. Thank you for all your hard work.
[Nextbit Robin] tlxxxsracer:
Don't ever use nfc.. Not worried about not having it at the moment.

I was using Google camera btw.

Can't wait for the next update :) again, good job!
[Nextbit Robin] tlxxxsracer:
Here's a log for proximity sensor not working on calls.
[Nextbit Robin] Empty2k12:
As a avid Ingress player I can confirm GPS is working. I used the app Gps Status to debug if Gps is working while it didn't work in Ingress initially. With the app installed GPS works instantly in Ingress as well.
[Nextbit Robin] moosefist:
power management, performance, and battery saving definitely over NFC for me
[Nextbit Robin] Empty2k12:
I noticed another small bug: When using a headset and unplugging it, the notification from "Call Management" that says "Headset is plugged in." persists. I will test if this is a bug with Call Management or if the headset is still "plugged in" systemwide.
[Nextbit Robin] valhallen.282:
Mobile Settings FC

I was already on the latest 1450 based NextOS. For whatever reason my mobile settings seem to FC and then the device goes in to no sim card mode. Should I not be a knob and do a full reset (my computer died and I'm on a fresh install hence the laziness) or would these dmesg and logcat be of help?
[Nextbit Robin] tlxxxsracer:
Confirmed. I had this yesterday. Reboot gets rid of the persistent notification.
[Nextbit Robin] Gandalf:
Right now we're using a hybrid aosp-caf mix of repositories for telephony (mainly for msim support for op3) so I'm not surprised there are telephony relates problems. I'll look into it. This will certainly be resolved and on a proper plan once nightlies start.
[Nextbit Robin] valhallen.282:
Thank you for your time and wisdom. Also. No root. Or rather it installs cleanly but does not function. I assume this is down to missing implementation?
[Nextbit Robin] Gandalf:
No, we do not include root because some users do not WANT root. You must install root yourself :highfive:
[Nextbit Robin] valhallen.282:
I'm sorry if I wasn't clear sir. I'm using TWRP. It's a fresh download of SuperSU. I've flashed the SuperSU zip. TWRP installer cleanly completed the install.

Attaching screen. This is from within the settings app. Still I have No root. I've been around long enough to know that for the sake of most users Su is not included. (I just don't post much)
[Nextbit Robin] tlxxxsracer:
What version of SU zip are you using? Root Works fine for me. Try downloading the latest
[Nextbit Robin] valhallen.282:
Using the one from the original guide to Root and Install TWRP. Beta 2.68 you should be able to see it in the screenshot. Updating with the latest one from the chainfire site killed the ROM. Pretty much fresh installing right now. FML. Last dmesg attached. Sorry no logcat.
[Nextbit Robin] makbomb:
Newest SU 2.78 BETA working fine here. Try that.
[Nextbit Robin] Gandalf:
Use the LATEST version of SuperSU. That version is quite old and probably doesn't even work on N.
[Nextbit Robin] mousse04:
Hi dev, ROM link send a 404 error ;). Looks like flashing the Nextbit camera all works ... Anyone has it?
[Nextbit Robin] tlxxxsracer:
Just delete the file name in the address bar.

https://whatley.co/ether/
[Nextbit Robin] substanceneil:
Camera NX (experimental build for non Nexus devices) from the link above works, but does not add HDR functionality. It does add a pretty interesting Lens Blur feature as well as a 60 fps video. I did get a force close switching between the 30 and 60 fps, though.
[Nextbit Robin] 02busa:
Yep, running great so far. Thanks!
[Nextbit Robin] DECHTECH:
[IMG="my screen was off...."]https://cdn.discordapp.com/attachments/238580369530683393/286248742313787394/Screenshot_20170301-075211.png[/IMG] Uuuhhhbhh... This normal?? My screen was off and all while I was sleeping and sitting still. This is odd
[Nextbit Robin] jimmyzyx:
Look into misc. That's the issue. Most of us don't have that, so you must have some kind of underlying application running in the background draining the battery.
[Nextbit Robin] XxXPachaXxX:
[MENTION=3878813]Gandalf[/MENTION] are the fingerprint and performance fixes kernel side only? (Comparing to LOS i mean)
[Nextbit Robin] Gandalf:
No. Check our gerrit.
[Nextbit Robin] gr3y_:
What app are you guys using to check if the phone's deep sleeping? Mine's draining faster than usual since a couple days ago, I think...
[Nextbit Robin] pintasmapila:
Do I need to flash GApps to have gps capabilities? I clean flashed and can't seem to get Waze or any other location related apps to work.
[Nextbit Robin] baurez:
I think you could use: Parameters > omnigears > more > Time in state
[Nextbit Robin] gr3y_:
Thanks! Looks like it's sleeping well (78% in deep sleep), after all :)
[Nextbit Robin] valhallen.282:
Did you install NLP providers and activate them? I did say use more than one.
[Nextbit Robin] sabresfan:
deep sleep working great here. Awesome job.
[Nextbit Robin] substanceneil:
Thank you. Latest weekly is great, with minimal or no lag. I have to say, though, that the 0216-homemade, once switched to the interactive governor, was running less hot with better battery.

Note that I did clean flash, but I restored apps with settings using Titanium Backup. This may be causing an issue... I may try resetting the phone and loading my (36) apps manually via playstore without restoring settings to see if it makes a difference. With things more stable, hopefully we won't be flashing between homemade and weekly builds as much.
[Nextbit Robin] pintasmapila:
Silly me. :) Somehow i thought the location providers would be needed only for a no-gapps (MicroG) scenario. I wonder why location providers are not part of the rom... Working perfectly now.

The latest rom release is absolutely perfect. Fantastic performance and great battery life. I'm still fighting Google. I just need to find a way to get my contacts back (from Google) and to sync them and i'm all set :) Calendar is working nicely with aCalDav.
[Nextbit Robin] jimmyzyx:
That might not be the case. I did notice with the latest weekly that the phone is getting hotter than before with clean flash and no apps installed yet.
[Nextbit Robin] fromeister2016:
Omni 7.1.1 download

I have been trying*for three*days to download the Omni*7.1.1 rom from the website*that is listed on this forum.*Each time*it takes me to the website it does not load and I am unable to download the rom. I would rather be able to use the official rom*versus the unofficial rom. I have tried to download the rom*from the website on*three*computers and two phones and still have not been able to access the website.*Any help*would be great. Thanks.
[Nextbit Robin] derdjango:
Just ordered the phone, should be here Friday. Really good to see an actively developed ROM for this device here, thank you for that!

Works for me. Try this direct link for the latest weekly.
[Nextbit Robin] Gandalf:
I probably need to make a few more tweaks.

Just stay on weeklies for now. I'm not doing anymore homemade tests since the base is completely stable, it's too much of a hassle
[Nextbit Robin] jimmyzyx:
Agreed. Very nice build, battery is still very decent even with the heating (and battery drain as a result), though this is not a pressing issue. Thanks.
[Nextbit Robin] laidbackcloud:
have you looked into gps? its unstable when using ro navigate to destination.
[Nextbit Robin] Gandalf:
It's pretty bad right now but it's not unusable. I haven't looked yet. On my list.
[Nextbit Robin] jimmyzyx:
I used it fine earlier this week when navigating using Google Maps. Though it does drain a lot of battery and make the phone heat up quite a bit, but thats the usual case with most phones/GPS apps.
[Nextbit Robin] valhallen.282:
Odd. Could you post a log of using gmaps. I was using Here Maps and OSM+ last week on an rather long drive and I didn't face a lot of battery drain. Heating yes. Drain no. My data was off at the time though.
[Nextbit Robin] whd5015:
The phone seems to restart 75% of the time within the first 5-10 seconds of making / receiving a call, regardless if it is made through WhatsApp, or the Phone App. Otherwise, there haven't been any pressing issues since I started using the ROM approximately two weeks ago!
[Nextbit Robin] DECHTECH:
Doesn't happen to me.
[Nextbit Robin] substanceneil:
Clean flashed the latest weekly. ROM is still smooth but warmer than on the 0216-homemade. I just had a random reboot while browsing google calendar (desktop version) in chrome. I'll post logcat posted to Jira in a minute.

---------- Post added at 07:00 AM ---------- Previous post was at 06:51 AM ----------

@Gandalf, JIRA ticket is here. I could not figure out how to assign it to you as you had asked.

http://jira.omnirom.org/browse/OMNI-1361
[Nextbit Robin] vibranze:
How is this different with the one posted in Robin General?