yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] keredini:
Indeed, no issues at all ..
[Nextbit Robin] zibo29:
One more strange request for [MENTION=3878813]Gandalf[/MENTION]

How about making the on display button more like the one on stock nextbit? I think that they were really cool and "different" - no other roms are proposing that :)
[Nextbit Robin] Gandalf:
What button?
[Nextbit Robin] Kaleshwar:
He means the on screen buttons . Requesting to include the stock Macaroni like ones.
[Nextbit Robin] Gandalf:
Use substratum, apparently it works ;)

It will also be usable without root soon.

But otherwise no plans to change that aspect of UI
[Nextbit Robin] bmac6996:
Just noticed something and wondering if you guys are having same issue? Physical volume buttons dont' work for me no more. The GUI slider doesn't pop up and pressing up and down doesn't change the volume.

One of the last things i did was check the option to use the volume buttons to skip tracks while the screen is off and that function does work, but not sure if doing that broke the volume gui.
[Nextbit Robin] Saythis:
Works for me. You may want to try a clean flash.
[Nextbit Robin] bmac6996:
Yeah it was a clean flash.
[Nextbit Robin] Gandalf:
that may be a hardware problem
[Nextbit Robin] bmac6996:
The buttons work. That's proven by the fact that I can change the tracks of what I'm playing using the volume buttons when the screen is off.

I'll reflash a lil later again
[Nextbit Robin] bmac6996:
Switch Access was on. Doh!
[Nextbit Robin] zzromanzz:
Could anyone teach me how to reduce height of navbar? Thank.
[Nextbit Robin] sabresfan:
Interesting question. You could change the dpi but that specifically I would like to know. Possible edit to setting somewhere.
[Nextbit Robin] sykomaniac:
[MENTION=3878813]Gandalf[/MENTION] has anything changed in the build setup recently? Can't seem to get a complete homemade build as framework is missing quite a lot of files. Also seems to be deoxed. Thanks
[Nextbit Robin] Gandalf:
No, you must be missing something somewhere. What are the errors
[Nextbit Robin] sabresfan:
No errors for me. Make sure you clean flash to avoid problems. I go back and forth between my robin and v10. Same SOC but omni beats my v10 running LG software with a gig less of ram.
[Nextbit Robin] sykomaniac:
No errors it completes the build which is strange. Only thing is it's about 80mb smaller as the arm and arm64 folders in framework are not added as part of the build. I've no idea why :(
[Nextbit Robin] Kaleshwar:
I've noticed in snapdragon camera that the front facing camera shoots at 3.1 megapixels. Is there a bug that prevents it from utilizing the full 5 megapixels?
[Nextbit Robin] Saythis:
I would venture to say that performance-wise, the newest nightly (02-19) is the best yet. Got 74k in Antutu :good:
[Nextbit Robin] Gandalf:
Homemade builds are deodexed

If anyone is willing to test a build for me for performance -- I've been using this for a bit now and it seems great. You MUST clean flash, and you MUST provide feedback. So make a backup.

https://whatley.co/omni-7.1.1-20170216-ether-HOMEMADE.zip

And for those who consistently ask about OMS - our OMS maintainer has everything on gerrit and we are in the process of testing; and NO, it is not in that build I just posted here.
[Nextbit Robin] jimmyzyx:
Just flashed and tested the newest build (0219), and it appears to be a little laggier than the 0212 version, but that could be take some time for the ROM to adapt. Once again, when benchmarked with other popular ROMs, Omni rised up by far. Attached are the results. With this ROM, appreciate [MENTION=3878813]Gandalf[/MENTION] for your efforts to add in the "wake and unlock" feature, though the finger print scanner seems a little bit buggy overall (hit and miss often).

The notification lights aren't working, and additional actions (double tap/long press actions) with the Navigation buttons are missing... Would be awesome for those to be added.
[Nextbit Robin] goaldispirited:
Thanks for this week's update.

My feedback is similar to [MENTION=7084266]jimmyzyx[/MENTION], by which the rom seems to be laggier/more jittery. The fingerprint sensor that is supposed to be on all the time doesn't seem to work as expected. It works momentarily after I turn off the screen. However, after leaving the phone alone for a while, the fingerprint sensor doesn't seem to work.

So 2 things:

1. Performance deproved with this recent release

2. New always-on fingerprint sensor does not work as expected
[Nextbit Robin] Gandalf:
I noticed that I "bulge" my finger when using the fingerprint scanner.. And when I replicate it properly from how I recorded the fingerprint, it works EVERY time without fail. Try reassigning your fingerprint and make sure your finger pad is flush to the scanner and you are not pushing from the back of the device over the edge.

If you're having performance problems make a backup and try that test build. Thanks.
[Nextbit Robin] Gandalf:
Oh and My homemade builds are ~410mb
[Nextbit Robin] sykomaniac:
Cool thanks. I'll take a look at your homemade build setup. Once OMS is merged I don't need my homemade builds anymore anyway ;) thanks for taking the time to reply!

---------- Post added at 09:03 AM ---------- Previous post was at 08:44 AM ----------

Looks like it's worked OK and I'll just flash it and see. Think the issue is that the build box doesn't have enough ram. Usually when building I'll have to kick it over at least twice. This results in a zip being produced simply labelled Omni.zip. This time it completed without needing a reboot which actually gave me a homemade zip. Thanks again
[Nextbit Robin] DuelistRaj:
Hi, remember the 2x A-57 cores. They are still inactive. I wanted to know will the cores be up and running soon or will it take some time. Thanks.?
[Nextbit Robin] goaldispirited:
I just clean-flashed your test build.

My feedback:

1. Jitters still exist

They occur when

a) I first flashed the rom and was performing the setup for GApps

b) After the setup is done and the Play Store was busy updating stuff

c) Randomly when the phone is busy with lotsa background tasks or a single heavy task (like the first second when loading a heavy website)

2. Jitters are mostly eradicated

That said, it is mostly smooth now. That initial jitter when you first scroll anything is now gone. Most scrolling are now smooth. This is very very nice! Mostly because my expectations are now met.

3. The fingerprint sensor works for the most part

But sometimes it doesn't. I'm referring to having the FP sensor detecting FPs when the screen is off. But meh, not a big deal. If it doesn't work, I'll just press the button.

---

State of the rom:

The rom at this state has met my expections. If I want any better, I'd have to go for a Nexus or Pixel. I'm going to keep this homemade rom as my daily driver. Mostly because to me it is "done" now. Not going to update or flash anymore until the next major Android update (beyond Nougat) to Omni.
[Nextbit Robin] Gandalf:
Thanks!

On that note, could you check and ensure your device is getting to deep sleep via settings > More ?

Also, I have another test build that should eliminate any final lag :)
[Nextbit Robin] substanceneil:
Flashed the 0219 weekly (not the homemade test) build last night and it is great. There is the same lag, but it doesn't bother me at all after using Omni for the last 6 weeks.

A few notes

1. Snap camera is still slow. Google camera works well. I am perfectly happy with the performance using google camera. I did see a few items in the changelog related to Snap camera, though, and look forward to progress.

2. Like the prior builds of Omni, I cannot figure out how to get file-based encryption and direct boot. I only have an option to enable full disk encryption from the Settings > Security menu. No option to change to FBE in Dev settings. I found this, but I am not sure how to check or modify the setting described: "FBE is enabled by adding the flag fileencryption with no parameters to the fstab line in the final column for the userdata partition." I tweak /etc/fstab on my home PC, but I know it doesn't work the same way in Android and may not be user editable.

3. The Fingerprint scanner works about 90% of the time with screen off. Nice feature!

4. I flashed Magisk this time around including the integrated root. Seems to work well. Safetynet does not pass, as we know. Did anyone ever revert to the earlier January builds where SN did pass to see if the issue is some tweak to Google's process vs something different in the kernel/rom?

5. I am unable to get Substratum themes to work... I saw a few screenshots where folks had custom themes, but these may have been homemade builds with OMS integrated. No big deal for me.

I am curious about the homemade build. [MENTION=3878813]Gandalf[/MENTION], does this one also use different keys, so that updating from homemade to the next weekly will require a clean flash? I assume so. I also am curious the difference between a weekly and a homemade from an engineering perspective... is it that the weeklies align with Omni development at large (across all devices) whereas the homemade diverges in a way to allow you to test and tweak more freely?
[Nextbit Robin] goaldispirited:
Please let me have the next test build. KILL THE LAG!

https://dl2.pushbulletusercontent.com/nRdTdmMJ75ttiAWZWOAKsEI2DawbdiM3/Screenshot_20170220-000902.png

Yeap, getting into deep sleep.
[Nextbit Robin] substanceneil:
New bug:

Encryption will not unlock. After Settings > Security > Encryption > Encrypt performs, behavior is odd:

1) The first boot after encryption is done will pause for password. In my case (on 2 occasions using the current and previous weeklies) I am using a pattern. Interestingly, the boot will continue regardless of the pattern I enter this first time only. I know this because I made an error entering the pattern, but boot proceeded.

2) On subsequent boots, Omni will pause for password, but the pattern is not accepted. The first time this happened (last last night), I assumed that I had remembered by pattern wrong, so I reset the device (TWRP > format data > full wipe > clean flash current Omni + nano gapps). After clean flashing the current weekly and reinstalling my apps, I tried to encrypt again and have the same issue.

Additional notes: I haven't tried using an alphanumeric passcode. I have been using Omni since the first weekly, but I think yesterday may have been the first time I encrypted. I was using encryption on my prior devices (Nexus 5x, 6p) without issue. Obviously I cannot post a logcat, etc. I have reproduced this error with the current and last weeklies. The first time I was unrooted. The second time I was magisk rooted. I have not made any changes to the kernel, etc.

Thoughts?
[Nextbit Robin] substanceneil:
Update:

1. The issue seems to occur on the 0219 weekly and 0216 home made for what its worth.

2. Interestingly, what seems to be happening is that Settings > Security > Encryption > Encrypt proceeds as it should. On the initial boot, whatever pattern I enter (whether it matches the pattern that is set to unlock or not) becomes set as the encryption password. So, if the initial unlock is done incorrectly, the incorrect pattern not only passes, but becomes the pattern required to decrypt on subsequent boots. I don't think this is intentional. Interestingly, this process sets the unlock code *after* the encryption is done. I have testing and confirmed twice.

Side note: The homemade build is awesome so far.... I haven't installed all my apps (testing this encryption issue repeatedly), but the scroll is buttery smooth in the settings app.
[Nextbit Robin] raddatt:
Perfect ROM, thanks so much again. Noob here, but I was curious, how difficult would it be to implement (maybe as an option) the Pixel's navbar as well as its blue system accents? (I understand there are higher priority issues right now, but was just curious)
[Nextbit Robin] Gandalf:
[MENTION=3564416]substanceneil[/MENTION] I haven't removed stock encryption, I just threw together cryptfs_hw from CAF so that stock decryption works. I'll look into it.

File-based encryption... I haven't touched that either. You can try editing the fstab as described and then pushing it to /system/etc/fstab.qcom while in recovery (with system mounted rw, of course)

SnapdragonCamera is a HUGE PITA. But I'm still working on it after I finish these powerhal and cpuset changes from bullhead to fix up UX.

[MENTION=8069827]goaldispirited[/MENTION]: it's compiling now. I will post a link when it's done.
[Nextbit Robin] DuelistRaj:
Use the S.i.X substratum theme. You can download it from the play store. For navbar use N navbar or Navigate. They as well are available in the Play Store. The overlay is pretty great without much issues. Try it, it is for free.
[Nextbit Robin] zibo29:
[MENTION=3878813]Gandalf[/MENTION] I think there is a little bug on the 1902 build (directly downloaded from omni site), flashed on top of old build - at every reboot i get the message "Device Features has stopped working", should be related with the Touch ID off-screen detection (which I don't use anyway) - hope it helps

[ROM almost perfect, my daily driver with no regrets, amazing stability]
[Nextbit Robin] substanceneil:
Getting this on every boot with both the 0219 and 0216-homemade builds. It just comes once within a few seconds of boot. Device Features > screen-off detection works, though, although I have it turned off.

PS. Out of curiosity, do we think the screen-off fingerprint feature consumes more battery? I would assume it would, requiring constant attention to the FP scanner, but other devices including the SD808 Nexus 5x has the FP scanner "always on." Perhaps its somehow built into the hardware to work with minimal power.
[Nextbit Robin] jimmyzyx:
[MENTION=3878813]Gandalf[/MENTION] thanks for your huge dedication to this ROM, looking good so far. Just wanted to check the status on any plans to enable further Navigation Bar customization? (long press + double tap features)

Thanks again for your great work :good:
[Nextbit Robin] Gandalf:
Just clear app data for RobinParts and reboot

1) You can NEVER dirty flash between HOME-MADE and WEEKLY builds, ever, no matter what.

2) Yes, I haven't done it yet.

3) Not as of now but potentially in the future when I have time. I still need to fix up SnapdragonCamera -_- I've been really busy lately with other stuff.
[Nextbit Robin] jimmyzyx:
That is definitely good news and do take your time as you're doing this out of your own time! For 1) I mean can you dirty flash updates to homemade builds on top of homemade builds?
[Nextbit Robin] Gandalf:
Yes
[Nextbit Robin] goaldispirited:
Any updates on your new HOMEMADE build?
[Nextbit Robin] valhallen.282:
Patience yo! Testing the Homemade before it comes out for the world is key!

Those attempting to use MicroG please note that flashing between builds will cause you to lose functionality of MicroG's cloud messaging and your Google accounts. So keep backups at all times.
[Nextbit Robin] goaldispirited:
I'm testing the last HOMEMADE build. There are performance degradation after the first day. Hoping the next build will resolve it.
[Nextbit Robin] valhallen.282:
Could you please provide logs or some metrics. I've run it since the day it released and I have faced no such issues except when sync is in progress. (that's to be expected)

The Big cores come online under load and the rescaling is a WIP. But without logs there is no way to tell what is causing the slow down on your device.

Between Homemade and Weeklies the Homemade is currently better in terms of performance but most of it will be merged for the coming week.
[Nextbit Robin] substanceneil:
After 24h on Homemade I am noticing the phone running hotter than it has before. Nothing too intense, but definitely warm from typical use. Logcat posted on Jira.
[Nextbit Robin] jimmyzyx:
Notification lights actually do work. Just have to enable it in Notifications Settings.
[Nextbit Robin] substanceneil:
JIRA ticket is here. I didn't assign it properly and cannot figure out how... sorry.

http://jira.omnirom.org/browse/OMNI-1359
[Nextbit Robin] Gandalf:
Ah, Jira is only for official builds. Regardless I need to post the 2nd one. I'll be home soon
[Nextbit Robin] goaldispirited:
Awesome. Been checking this every few hours for it to drop.

On another note, the battery life has dropped.
[Nextbit Robin] substanceneil:
Agree. Homemade build seems to be smoother performing at the expense of battery and heat. Occasionally it will get hot enough to affect performance. Looking forward to the next iteration. Thanks, Gandalf.
[Nextbit Robin] Gandalf:
Try changing governor to ondemand, it's working great for me
[Nextbit Robin] goaldispirited:
How to do that?
[Nextbit Robin] substanceneil:
I did a little searching and found this page. Using Solid Explore with root access on, I looked at /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and found the default to be "performance." Can I change this via SE Text Editor to "ondemand"? I've never manipulated these files myself and am nervous.

Update: I made the change and phone booted fine. I'll use it for the rest of my workday and report back. Makes sense that a default performance governor setting would increase performance and decrease battery. I wonder what the default governer profile was for the prior weeklies?

2nd Update: after reboot, the /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor file is set back to performance! Must be another way to set this. Any advice, [MENTION=3878813]Gandalf[/MENTION]? I bet there are apps for this, but I like to know how to make the changes directly just to learn more.
[Nextbit Robin] Gandalf:
The kernel is setting performance by default. You can use an app like Kernels idiot to change it and set on boot for now
[Nextbit Robin] sykomaniac:
I've used kernel auditor mod here and free from xda
[Nextbit Robin] substanceneil:
Thanks, using Kernel Adiutor now. Are you folks happy with "ondemand"? Any argument for "interactive"?

The phone seems a bit less smooth but definitely less hot using "interactive" compared to default "performance".
[Nextbit Robin] Saythis:
Personally I'd look into using the Hawktail interactive Governor tweaks. It makes the phone quite streamlined without sacrificing battery life.
[Nextbit Robin] sykomaniac:
Same here using hawktail setup
[Nextbit Robin] substanceneil:
I had a random reboot (first time on Omni, I think) using homemade build and ondemand governor via Kernel Adiutor. Logcat attached. Note that the crash happened around 4:08pm ET, but I didn't get home to dump the logcat until now, so there is a lot of activity after the crash.

---------- Post added at 06:12 PM ---------- Previous post was at 05:41 PM ----------

How do I use Hawktail governor? This isn't an option from Kernel Adiutor using the Omni homemade build, which I presume keeps the stock kernel.
[Nextbit Robin] Saythis:
It's not a Governor per se, it's tweaks to interactive that changes how it functions. Sadly you'll need something like EX Kernel Manager to apply a pre-made script with the tweaks. Check out the Nexus 5x General Forum for more info ?
[Nextbit Robin] substanceneil:
Got it .Trying to create a bash script to apply the hawktail changes, but running into trouble at the command line. To use Audiutor, one must type in all of the settings manually? Whereas EX has the settings pre-loaded and saved? Probably worth the $4, but I'd much rather have the script execute from init.d rather than have a root access app running at every boot.
[Nextbit Robin] Saythis:
Bash is certainly another option. There's some su.d bash scripts floating around
[Nextbit Robin] sykomaniac:
Hi [MENTION=3564416]substanceneil[/MENTION],

If you download kernel auditor mod from here https://xdaforums.com/android/apps-games/kernel-adiutor-mod-singularity-kernel-t3333549

Install it and run it. Then FC it.

Then copy the attached files into /data/data/com.kerneladiutor.mod/files (requires root).

You will rename the two files from .txt to .json e.g commands.json

If you then open the app and go to profiles hopefully it's listed.

This isn't tested - just trying to help :)
[Nextbit Robin] Gandalf:
update:

fixed FC on Device Settings on boot (forgot to remove Startup broadcast receiver from manifest :silly:)

cleaned up ramdisk

removed some unused stuff leftover from the CM kernel

other goodies

https://gerrit.omnirom.org/#/q/status:merged

I'm going to remove SnapdragonCamera for now from the next official build tomorrow until I can fix video recording with HAL1.
[Nextbit Robin] goaldispirited:
Any performance tweaks?
[Nextbit Robin] DECHTECH:
Didn't work for me :\ Trying to get this working without paying for some app!
[Nextbit Robin] sykomaniac:
Just tried it now. When copying in the 2 JSON files change permissions to owner read and write (600). Then under profiles you should see one labelled great.
[Nextbit Robin] DECHTECH:
Silly me! Forgot about permissions, thanks! :silly:

---------- Post added at 11:24 PM ---------- Previous post was at 11:20 PM ----------

+1 Would like to see less micro-stuttering, other than that this is the best rom for the Robin :)
[Nextbit Robin] Gandalf:
I went and just merged the PowerHAL and cpuset changes we've been testing, I recommend if you are playing with governors and other things to remove all changes before flashing this weekly. Thanks.
[Nextbit Robin] DECHTECH:
Whoops, I jumped right ahead to flashing it before undoing the changes as I didn't see your post... Can I revert the changes and have no problems after flash? Or something else. Would like some assistance as my Antutu score is around 30k right now :( !
[Nextbit Robin] Gandalf:
Just clean flash. AnTuTu and other benchmarks are stupid. Just worry about how it runs for usage, don't worry about benchmarks
[Nextbit Robin] jimmyzyx:
Will you be releasing the next HOMEMADE version any time soon? If you are, I might wait for that as I am currently running the HOMEMADE 0216 version, and I won't need to clean flash this week's official Weekly.
[Nextbit Robin] Gandalf:
It's all merged into this weekly
[Nextbit Robin] jimmyzyx:
Thanks. I'm guessing there won't be any more homemade builds going forward as it's all going to be in the official weeklies then?
[Nextbit Robin] Gandalf:
Just stick with official :good:
[Nextbit Robin] goaldispirited:
Flashed the latest weekly. Performance was really bad compared to 19/2. I had to revert the change.
[Nextbit Robin] Gandalf:
Try clean flashing it.
[Nextbit Robin] jimmyzyx:
I'm afraid I have to agree with [MENTION=7541986]DECHTECH[/MENTION] and [MENTION=8069827]goaldispirited[/MENTION]. Came from 0216 HOMEMADE and 0219 Official version. Now that I am on the current 0226 Official version (did clean flash), I'm a little disappointed with the drop in performance... Poor benchscore aside, I'm noticing performance reduction and stuttererness compared to the old versions..

I attached the benchmark logs that I know many users would like to see, though it is up to one's own interpretation, and this is for my own device only. DO NOT use this as an excuse not to experience the ROM on your own, this is only reference for those that are interested.
[Nextbit Robin] freeezer98:
Yeah i am too facing lags the new build.
[Nextbit Robin] Gandalf:
i forgot an sepolicy rule. i'll push a hotfix shortly. I found a few more denials I want to address *properly* first.
[Nextbit Robin] goaldispirited:
What are "denials"?
[Nextbit Robin] Gandalf:
processes being denied from executing tasks based on selinux rules.

good read here on the subject from Google: https://source.android.com/security/selinux/index.html
[Nextbit Robin] goaldispirited:
Thanks :good:

---------- Post added at 08:47 AM ---------- Previous post was at 08:41 AM ----------

BTW, do you have any idea why there are these micro stutters in the rom? Even with the kernel/governor tweaks implemented, and even if the phone is running on "performance" governor with both little/big cores all maxed out. I still experience micro stutters.

What could be it?
[Nextbit Robin] sabresfan:
I agree with previous posts. Latest build lags compared to the 2/19 build. Its a very noticeable difference for me. I always clean flash.