yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] pintasmapila:
I'm waiting for yet another release. But when its out, i would like to help out, at least to present some logs to Gandalf. I know i have to perform a clean install. Can you tell me how i can collect the necessary logs?
[Nextbit Robin] Kaleshwar:
You can use an app called catlog. It's in the play store.
[Nextbit Robin] pierremtb:
Sure thing, stock camera opening logs attached ?
[Nextbit Robin] tanishq.dubey:
Any updates on the "miscellaneous" battery usage? Seems to be the main factor in battery drain. I can provide logs if told where to look.
[Nextbit Robin] Gandalf:
im looking into it.

i'm rewriting the entire device tree from scratch and basing it on bullhead (another 8992) and integrating CAF bits when necessary. mainly i'm doing this to get the stock init and then i'm going to try and run cpuquiet for hotplugging . last i did this, it definitely fixed the battery drain but the cores were scaling improperly and i didn't feel like tracking down the problem, so i'm just starting over with a clean slate.
[Nextbit Robin] wecameasjesse:
I'm having the same issue, log is exactly the same. Been using stock camera app, and snapchat for days with no issue until today. Very puzzling.

---------- Post added at 12:44 AM ---------- Previous post was at 12:23 AM ----------

Just flashed the latest weekly (dirty), seemed to fix my problem, for now.
[Nextbit Robin] voilamos:
Flashed the new weekly. The fingerprint sensor seems to work randomly , and there's still a delay with the lock screen. I'm not really sure about how to provide logs for this - since its really random.

Really appreciate your efforts OP!

Cheers
[Nextbit Robin] Kaleshwar:
Yeahhh there's a lockscreen delay Alright. Try catlog. It's an app.
[Nextbit Robin] CertifiedBlyndGuy:
[MENTION=3878813]Gandalf[/MENTION] okay, so I started working on adapting the thermal driver I made for Robin, but then I realized that Qualcomm had already implemented cluster control and stuff like that into the stock thermal driver so doing so would be pointless (in it's current state), and I would have to rewrite great proportions of the driver to work alongside it. As it stands, it is just offlining core's 5 and 6 (the cluster) and the second to last frequency throttle zone.

I think I will begin a rewrite whenever I can get my hands on a device like this, but for now, Onyx with the 801 seems to be doing fine for me even if I am stuck on 3.4.113 lol

I did however do this, because I wouldn't want to leave anyone empty handed, and I do keep my word:

https://github.com/CertifiedBlyndGuy/android_kernel_nextbit_msm8992/commits/android-7.1

In short, I just added power efficient workqueues, and added sysfs nodes to the thermal driver so that it can be configured in the user space. Also made a couple changes to CPU boost as well. Like I said though, I will definitely come back to this in the future as I am very close to having something for CPUs using clusters; I just don't have a device that has them yet to test

I would push them to Gerrit, but it seems you guys are using a hook that checks for Change Id's and it was giving me some issues even though I had went through the process of adding them in the footer of the message. I did gitdir=$(git rev-parse --git-dir); scp -p -P 29418 CertifiedBlyndGuy@gerrit.omnirom.org:hooks/commit-msg ${gitdir}/hooks/ and all of that to ensure that an ID was applied to the commit, but Gerrit didn't seem to pick up on it

Thanks for your time

Edit: Also started work on CPUQuiet too. It is based off of the Find7s implementation, and slightly adapted for Ether's source
[Nextbit Robin] Gandalf:
Gerrit should kick back a command if you're missing change IDs, just copy/paste it and then do "git commit --amend" and save it as-is, it will append the change id and you should be able to submit changes. Only needs to be done once per project.

Regarding hotplugging, I added sonys implementation of Nvidia's cpuquiet and it idled beautifully, but wasn't scaling correctly which led to extremely sluggish UX. I'm going to look into it again once I finish my new device tree using stock NBQ init.

Update: just took a peek at your source. This is how I handled the cpuquiet port from Sony's 3.10.x kernel: https://github.com/jakew02/android_kernel_nextbit_msm8992/commits/cpuquiet

Ah also it relies on some ramdisk changed and some system props
[Nextbit Robin] CertifiedBlyndGuy:
Awesome. I will take a look at Gerrit again, and have a look at your implementation of CPUQuiet
[Nextbit Robin] Gandalf:
I was lazy and just cherry picked everything from Sony, and then whatever else was needed to compile ?
[Nextbit Robin] bmac6996:
Just d/l the weekly. Thanks.

Is it just me because when I have the device locked, it now requires me to push down the power button, the screen will activate and then it will read my fingerprint?
[Nextbit Robin] FlamieFox:
Is it only me or others are getting performance issues as well?

Since updating to today's build the phone has started to lag a lot inside apps. Loading times are about the same but the rest is not. Web pages load in chunks, the sticker menu takes one or two secs to load in Telegram, this sort of things.

Together with the update I reflashed SuperSU.

Also, is it because of root that the updates aren't delta but the whole rom?
[Nextbit Robin] Kaleshwar:
Yes I've noticed the lags but it's not root causing it because I haven't rooted mine.
[Nextbit Robin] GoToHealth:
Performance really fell apart after this last update. How do we report this kind of bug?
[Nextbit Robin] voilamos:
Yes, performance seems to have taken a big hit.
[Nextbit Robin] Gandalf:
I'm rewriting the entire device tree. Bear with me, it's almost ready, just a few minor things left until it's ready for deployment.

I disabled active fingerprint sensor so it matches stock functionality. I'll implement a switch for it soon.
[Nextbit Robin] FlamieFox:
That's great to hear! Thank you ?
[Nextbit Robin] gr3y_:
I don't mean to push or anything... I'm just curious, can we expect the new device tree with the next weekly? :)
[Nextbit Robin] Jacobwitt:
Saw there was a weekly released today. o.0 is it the slowness fix?

---------- Post added at 08:09 PM ---------- Previous post was at 07:32 PM ----------

Boot Animation is pretty neato! Lets see if he fixed the slowness?
[Nextbit Robin] wecameasjesse:
Please let me know if it did :)
[Nextbit Robin] Jacobwitt:
Speeds are pretty adverage, but I dunno really. I haven't seen the terrible lag for what it really is yet.
[Nextbit Robin] GoToHealth:
Looking at the change log on cmxlog, I int see any device specific changes in the manifest. Hopefully something else got changed
[Nextbit Robin] valhallen.282:
This is the OmniROM-> https://github.com/omnirom/android/commits/android-7.1

The is the new device tree is coming along

The wait is for NextBit to come back with a few things. We are all anxiously waiting for their next release. That should make it easier. A little more patience and it'll be well worth the wait.
[Nextbit Robin] substanceneil:
Coming from the Jan8 weekly, there is definitely a new lag in this weekly. Still usable, though. I haven't noticed and other changes.

Is it possible to roll back to the Jan8 release by dirty flashing over this one? I am nervous to do so...

UPDATE: Wiped cache and dalvik, dirty-flashed 1-8 weekly, and I am back in business. As snappy as ever. Looking forward to the new device tree, etc to improve this ROM even more.
[Nextbit Robin] bmac6996:
For fun, I cleaned flash this week's release and still pretty laggy.

Reverted back to the 20160108 release. Works fluid enough for daily usage.

Looking forward to the new device tree release.
[Nextbit Robin] zibo29:
searching for the stablest ROM on nougat, currently on AOKP but with GPS issues and fingerprint detection after unlocking device (the sensor does not turn off)

Any of these here (is the 20170108 the stables as now right?)

Otherwise I'll give a try to lineage and report feedback here

Thanks everyone
[Nextbit Robin] substanceneil:
Fingerprint reader on 1/8 weekly works 90% perfectly. The issue is that about half the time I can unlock simply by placing your finger on the power button (without pushing). Half the time I need to push the button down. Gandalf in subsequent releases has put the fingerprint button behavior as stock with a toggle to have it read without a button-press.

GPS works perfectly for me.

Wifi hotspot is not working.

Using 1/8 as my daily driver.
[Nextbit Robin] Gandalf:
Going to look at WiFi hotspot tonight and find out whats causing the lag.

Been busy with work lately so I haven't checked in the past few days
[Nextbit Robin] Jacobwitt:
Dirty Flashed to 8/1 Runs smooth as butter compared to 8/22 Can't Wait for new device tree also!
[Nextbit Robin] substanceneil:
Has anyone flashed the Jan29 weekly? I am very happy with Jan8, found the subsequent weeklies to be slower performing, but may try later today.
[Nextbit Robin] pintasmapila:
I did. It still has the same lag, unfortunately.
[Nextbit Robin] lionruler2:
I wasn't on the earlier weeklies, but I like what I'm seeing now. Thanks Gandalf.
[Nextbit Robin] Akoolive:
No lag on my end. Latest weekly.
[Nextbit Robin] pintasmapila:
Well.... Time to test it again :)
[Nextbit Robin] Gandalf:
I just fixed the laggy UX, thanks to suggestions from [MENTION=4003363]xboxfanj[/MENTION]. Going to see how cpuquiet works now
[Nextbit Robin] sabresfan:
Latest weekly is running great. Thank You
[Nextbit Robin] gr3y_:
Thanks! Is the fix included in the latest weekly?
[Nextbit Robin] Gandalf:
Next week it will be. If I have a breakthrough I'll push a hotfix via OpenDelta
[Nextbit Robin] noonebhargav:
Will flash omni ROM. so which date one should i flash? Does the latest build lag?
[Nextbit Robin] picaso86:
I'm trying to flash the zip for root and it's not working. Anything additional I have to do to get this working?
[Nextbit Robin] GigahurtzUK:
How will MicroG Project be used/incorporated or is it just for tinkerers? Thx for a great ROM.
[Nextbit Robin] Gandalf:
we just support signature spoofing so you can just install microG without needing to mess with anything for that.

if anyone wants to try this out: https://whatley.co/omni-7.1.1-20170130-ether-HOMEMADE.zip
[Nextbit Robin] GigahurtzUK:
Thx

Thank you. Great as always.
[Nextbit Robin] Gandalf:
https://whatley.co/omni-7.1.1-20170131-ether-HOMEMADE.zip

That's a new one which I'm going to ship soon. If you guys can give me feedback on performance that'd be great. Its running nicely here for me.
[Nextbit Robin] hengx:
It's performing much better than the last few weeklies. The lag seems to be gone, thanks Gandalf!
[Nextbit Robin] freeezer98:
I can't connect to camera, did you face this bug?

Edit:supersu breaked camera. using phh without any isues.
[Nextbit Robin] baurez:
Gandalf, can we flash your Homemade version over the 29/01 version ?

Thx.
[Nextbit Robin] freeezer98:
[MENTION=3878813]Gandalf[/MENTION] A small request- Could u please add elementalX governor.
[Nextbit Robin] sykomaniac:
[MENTION=3878813]Gandalf[/MENTION] are these changes pushed to your personal repo? Thanks :)
[Nextbit Robin] substanceneil:
Dirty flashed the 0131-homemade rom last night and have been using for about an hour today. So far so good. Lag from the last several weeklies is resolved. Everything else working so far except the wifi Hotspot which returns the same error. Thanks!

EDIT:

1. The fingerprint reader seems a bit less reliable. I am finding that about 10% of the time the fingerprint does not read at all. When it does read, it is accurate.

2. [MENTION=3878813]Gandalf[/MENTION], I've shared a logcat of the wifi-hotspot error via Jira before. Let me know if it is worth doing again for this newer version.
[Nextbit Robin] sabresfan:
Running great for me. Lag is gone. No problem with connecting to camera with the latest SuperSU. Outstanding job thank you.
[Nextbit Robin] bmac6996:
Tried the homemade rom. So far at par about in terms of lags to 01082017 build. . For me I still noticed a Bluetooth lag/skip during streaming music to a device. GPS seems to work. Will need to test some more.

Also used Magik for root and doesnt pass SN like it use to.

Thanks for your hard work.
[Nextbit Robin] Gandalf:
i'll post another test build that can be dirty flashed over the last HOMEMADE build shortly
[Nextbit Robin] keredini:
Mine does, did you enable Magisk Hide and reboot?
[Nextbit Robin] bmac6996:
I did.. i'll reflash to see if something is goofed up for some reason then.

Also FYI, under battery alot of the usage or standby usage is still being thrown under the "misc" bucket or bluetooth
[Nextbit Robin] keredini:
Same here ...
[Nextbit Robin] Gandalf:
i need to decompile SystemUI and tune the power ration overlays
[Nextbit Robin] DooSteve:
WiFi Hotspot error.

First, I would like to thank you for your contribution. I am using OMNI ROM for a week now. Other features work well, but the wifi hotspot function does not seem to work. When I turn on the hotspot, I get an error like the screen shot below.

[IMG="https://drive.google.com/file/d/0B2vD2-UZ4kIARGkxS2NScXc3Tnc/view?usp=drivesdk"]WiFi Hotspot setting[/IMG]
[Nextbit Robin] gryphonza:
Does this ROM have ambient display? I really miss the active display from my Moto X and would love to get something similar on my Robin.
[Nextbit Robin] Kaleshwar:
Yeah it does.
[Nextbit Robin] Gandalf:
i'm working on it right now.
[Nextbit Robin] Gandalf:
lots and lots of fixes and changes in tomorrow's weekly build:

entirely reworked audio configs

use PureNexus Gapps for "always-on/screen off" hotword detection

added SnapdragonCamera

updated qcacld-2.0 to latest CAF tag (was previously cherry-picked from bullhead kernel)

first step to fixing Tethering (it's not fixed yet)

disabled cpusets for now

fixes the unacceptable lagginess

made my first java commit

longclick on Hotspot tile now takes you to the Tethering settings instead of the Networks settings

a bunch of other stuff i forgot https://gerrit.omnirom.org/#/q/status:merged

I've been using this base for the past few days and it is completely stable minus tethering
[Nextbit Robin] hengx:
Thanks Gandalf. Looking forward to the next build.

Also, does anyone have HDR mode in this ROM? I've never seen it enabled and I've never seen anyone mention anything about it.
[Nextbit Robin] freeezer98:
Can I dirty flash the next weekly, or should i clean flash as there many changes? [MENTION=3878813]Gandalf[/MENTION]
[Nextbit Robin] substanceneil:
I have the same question. Can I dirty flash from the 0131 homemade build? I guess there is only one way to find out! Thanks, [MENTION=3878813]Gandalf[/MENTION]!
[Nextbit Robin] Gandalf:
I will look into this.

If you are currently on a WEEKLY build then yes since your build is signed with private keys. If not, them you must clean flash. As always if you have problems them clean flash.
[Nextbit Robin] substanceneil:
Sounds like updating from the homemade build will require a clean flash. Is that right?
[Nextbit Robin] Akoolive:
Yes
[Nextbit Robin] substanceneil:
Homemade 0130 was dirty flashed on top of weekly 0108, so perhaps I can dirty flash back to 0108 before taking the future weekly... Worst case I can wipe and clean flash.

Usually the weekly is posted by now, but I don't see it. I'll back up my phone tonight and hope to see the 0204 weekly tomorrow. Looking forward to all the new features.
[Nextbit Robin] Gandalf:
build failed from server issue.

NO, as I said, you CANNOT FLASH OFFICIAL OVER HOMEMADE. The official builds are signed with private keys and will not work. Going from Official -> Homemade works because homemade builds are not signed with private keys.

Weekly build will be started in a few minutes once I verify the last remaining CAF updates.

TETHERING IS FIXED.

In my testing the past week, the ROM seems quite ("quite" as in, completely) stable. Everything just works. Now that it's stable, I am going to start looking at adding cpuquiet again.
[Nextbit Robin] sabresfan:
Latest weekly is even better. Nothing I can see that's having issues. Overall great job.
[Nextbit Robin] substanceneil:
Incredible build! Everything just works.

- Fingerprint is now at stock speed and reliability

- Wifi tethering works perfectly

- No lag for me

[MENTION=3878813]Gandalf[/MENTION], I am not able to get the "Ok Google" hotword to detect while the screen is off, though, as you suggested would work in an earlier post. It works perfectly while the screen is on if phone is plugged in, even if locked. I tried with Pure Nexus Mini_Dynamic_GApps-7.1.x-20170121.zip (and with Open Gapps for the heck of it). Perhaps I misunderstood you in an earlier post. No complaints, though... I can live without that feature.
[Nextbit Robin] raddatt:
2/5 here but I still have light stuttering in everything :(

All cores are being used now, though.

Any tips before I clean flash?
[Nextbit Robin] substanceneil:
I may have some light stuttering as well after a clean flash. Nothing that bothers me. I write only to normalize what you may be seeing. Obviously hard to compare devices.

I did notice that Android Pay will not let me add a credit card, returning an error about this being a custom ROM. This may be expected, but the 0108 weekly and others did not seem to trip this. That said, I was never able to get Android Pay to work on OMNI. Everything looked good to go, with NFC on, etc, but when I'd hold my phone to a terminal it would not detect. I wasn't able to test whether NFC was working at all. FYI I have the bootloader locked.
[Nextbit Robin] hraharjo:
How can you get the bootloader locked with custom rom?
[Nextbit Robin] bmac6996:
I would use Magisk to make AP work. But never I have tried to relock the bootloader
[Nextbit Robin] :
It's a nightmare... I don't have nuch feel with cpuquiet hotplug
[Nextbit Robin] substanceneil:
After flashing twrp, i use fastboot oem lock to relock.
[Nextbit Robin] valhallen.282:
CLEAN FLASH is a must. This ROM's kernel has had a considerable rebuild. If you face even the slightest of issues reflash.

Yes something about hotword is a little broken right now. It does seem to be something that's affecting nexus/pixel devices as well. Might just be a Google issue.

NFC Transfers seem to be working alright. My country doesn't have android pay. Bluetooth streaming works much better than earlier. Lag is almost completely gone.

CPU quiet implementation will take some testing. Hopefully next weekly should have it. Thanks [MENTION=3878813]Gandalf[/MENTION] for the hard work!
[Nextbit Robin] Gandalf:
Hotword detection is probably a Gapps issue. I believe the 0107 pure nexus gaps worked and 01/21 don't, so I need to check again.
[Nextbit Robin] pintasmapila:
Maybe it doesn't work on initial setup but after that it works fine. I have to say Gandalf... I'm very very impressed with this rom. Congratulations and thank you. You really are one of the reasons Robin is still alive. :svetius:
[Nextbit Robin] Saythis:
Found my new daily driver. Excellent work [MENTION=3878813]Gandalf[/MENTION]. Performance is awesome, Bluetooth runs flawlessly, it's far smoother than Lineage by a mile. Using Hawktail Interactive Governor and scored 71k in Antutu ?
[Nextbit Robin] substanceneil:
OMNI on Robin is truly incredible.

Pintasmapila, do you have "ok google" hotword working when the screen is off and phone unplugged? If so, which gapps did you use.
[Nextbit Robin] pintasmapila:
No, only when the phone is unlocked. Sorry... :( I'm not sure it even works with this processor.
[Nextbit Robin] Saythis:
It will do screen off Okay Google but it seems to kill battery since it uses a wakelock probably.
[Nextbit Robin] bmac6996:
Do we know if the ROM's boot image is pre-patched for SuperSU? I think it is. SuperSU looks preinstalled on here.
[Nextbit Robin] pintasmapila:
Loudspeaker not working for phone calls for me...
[Nextbit Robin] adeelmysore:
Loving the latest weekly build all the issues I had have been resolved! Thank you for your hard work. Fingerprint works like a charm, no lag and hotspot is working.
[Nextbit Robin] Gandalf:
No, we just add hooks in settings. This ROM is not rooted.

Works fine for me. Can you get a logcat please
[Nextbit Robin] bmac6996:
I'm trying to use Magisk 11 and even at 10.2 and I could never get it to work and past Safety net. I was doing some reading and read that if boot.img was patch for SuperSU it could fail. Anyways that's why I'm asking.

Also using new build, so far bluetooth looks good and seems pretty smooth for the most part. Will check on other things and report back.

Thanks! :good::good::good:
[Nextbit Robin] Jacobwitt:
Having the same issue as you, Can't get it to pass Safety Net w/Magisk Installed strangely.

-\(:/)/-
[Nextbit Robin] sykomaniac:
Yep same here. Also for you guys running magisk are you able to delete from system e.g calendar app etc. I can't. Might be my issue though as I'm running a homemade version of Omni with substratum support
[Nextbit Robin] substanceneil:
Loudspeaker on calls working normally for me on a clean flash.
[Nextbit Robin] sabresfan:
Same
[Nextbit Robin] Saythis:
[MENTION=3878813]Gandalf[/MENTION] do you plan to incorporate the February security patch to the next update?
[Nextbit Robin] telmob:
Here it is:

http://pastebin.com/W8yZMszv

I might have messed something, not sure. The log is quite big, but the problems regarding the lodspeaker are at the very end.
[Nextbit Robin] Gandalf:
speakerphone was broken on NON-VoLTE calls. Anyway, it's fixed now and i'll start a build on jenkins to get a hotfix out since that's a pretty critical bug.

And yes, we merge every security bulletin...
[Nextbit Robin] baurez:
Hi,

There are a new weekly today, is this build contains the fix for speaker on call ?

(for future release, a changelog exist ?)

Thanks.
[Nextbit Robin] pintasmapila:
Phenomenal. Working perfectly. Thank you so much Gandalf. :highfive:
[Nextbit Robin] Gandalf:
I literally said in the post above yours that I was triggering a Jenkins build to push the speakerphone fix...
[Nextbit Robin] baurez:
As the time between build and your message was short, I was not sure. Sorry for misunderstanding.
[Nextbit Robin] keredini:
Same here, and i know for a fact it would pass SafetyNet in previous Omni versions using Magisk 10.2 w/ Magisk Hide enabled. I think it even passed on one of Gandalf's 'homemade' builds.

---------- Post added at 09:24 AM ---------- Previous post was at 09:18 AM ----------

Is that a custom governor? In Kernel Aduitor i only see the standards governors: interactive, ondemand, userspace, powersave, and performance
[Nextbit Robin] Saythis:
It's a profile that configures interactive so it functions differently. Basically instead of adding new governors to the kernel you can just load a script into EX Kernel Manager and it'll turn interactive into another governor basically.

https://xdaforums.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557/page626

From what I've seen (checking the script and such), the Robin has the same parameters for its interactive Governor as the Nexus 5x.
[Nextbit Robin] keredini:
Cheers for that ... I just grabbed EX Kernel Manager and GlassFish and HawkTail profiles. Will try them out over the next few days.
[Nextbit Robin] bmac6996:
Previously if you didn't root, you can pass SN and AP but it now detects a unlocked bootloader. There is something that you can edit in the kernel that can fool SN to believe it's still locked. That may be one part of the issue. It would be up to Gandalf to comment and see if he wants to take the ROM and the kernel to that direction.

The other part is to fool SN that the device is not rooted and Magisk and Magisk hide could provide both but something has happened lately that has broken that compatiblity part.

Another thing down the line if this all gets fixed is why Magisk/Some Roms doesn't play nicely with Arise 2.33. I know it does with some roms and other Root methods but not others. Thats is a whole different conversation though. :laugh:

---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------

BTW update on the latest weekly: Good battery for standby so far. When bluetooth is on but not connected,m it does drain a bit more than compared than the usual. It's actually number 3 on my battery drain after screen, and phone idle.