yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] hairycheez:
Try using Kernel Adiutor from the appstore
[Nextbit Robin] rcsharath:
Regarding LOS 14.1 Launcher

[MENTION=5795145]javelinanddart[/MENTION] Is there any possibility of replacing the current launcher with a newer one(with swipe-up)?

Thanks
[Nextbit Robin] malerocks:
Swipe up launcher would be awesome. I currently use Evie which gives me the same functionality though.
[Nextbit Robin] MDGeist:
Anyone else experiencing apps getting killed for seemingly no reason on the 15.1 builds?

Even with 1.5GB of free RAM, it starts killing apps. I already set the OOM Killer to minimum via Kernel Adiutor and disabled battery optimizations for apps i need running in the background, but Oreo keeps killing them.

If anyone has a solution for this, i'd be really grateful.

Running latest Oreo build from codefire.
[Nextbit Robin] boxes:
Change swappiness to 20
[Nextbit Robin] rcsharath:
Reg: LOS 15.1

Any updates on Los 15.1 [MENTION=5795145]javelinanddart[/MENTION] ?
[Nextbit Robin] shunjou:
It's dead, Jim.
[Nextbit Robin] dopaminejunky:
No commits since April 2. Here's hoping it get's picked up.
[Nextbit Robin] /root:
Well 14.1 is being worked on so there is that hope that sooner or later work on 15.1 will happen.

https://download.lineageos.org/ether/changes/
[Nextbit Robin] demeez:
No it's not. 14.1 auto builds weekly.

15.1 work stopped and is unlikely to continue unless someone else takes over.
[Nextbit Robin] rcsharath:
Why was that?
[Nextbit Robin] malerocks:
Any ideas on how to get Google Pay to work on LOS (apart from installing Magisk)? Just switched to it and it won't allow me to use since I am on a custom ROM (I am not using root).
[Nextbit Robin] rcsharath:
Just register your device with Google here.

https://www.google.com/android/uncertified
[Nextbit Robin] joeminati:
The 15.1 LOS unofficial rom appears to be a bit sluggish scrolling between screens with over 1.2GB of memory left over and not too many apps running. Am I the only one?

Just came from a Pixel but could not resist having this phone again. So awesome.
[Nextbit Robin] shunjou:
I thought the same thing so I pulled the power changes from omni along with some stuff from PA and a few more changes. The result is a lot smoother. I haven't tested battery life extensively, but idle drain overnight seemed low. Build is here.

Migration script if coming from official: https://androidfilehost.com/?w=files&flid=254680

Newer twrp than official, from lineage wiki: https://androidfilehost.com/?fid=817906626617957398
[Nextbit Robin] NurKeinNeid:
Cool. Many thanks for sharing.
[Nextbit Robin] joeminati:
Where you mention the build, is that the whole build to flash to get the setting built into the room?
[Nextbit Robin] jabashque:
(Might want to keep in mind that the most recent build javelinanddart posted defaults to running the display at 45Hz. If you run `setprop persist.sys.display.frame_rate 2` in a root or adb shell, you can change the framerate back to 60Hz.)
[Nextbit Robin] michaelmcnutt:
Try the LOS based Oreo ROM from [MENTION=4258086]firebird11[/MENTION] CRDroid, I find it to be smooth and stable, with nice extras and great battery life.
[Nextbit Robin] shunjou:
Can't speak for that guy, but I wasn't running the last posted build. I ran a new build initially, purely from last available official sources, since I didn't like the baked in gapps/su or the weird icons. The hacky custom power hal just has too many issues.
[Nextbit Robin] jabashque:
Ah, I see. Could you clarify what sort of issues the custom power hal had, just out of curiosity?
[Nextbit Robin] shunjou:
I think I already explained it. The lag was excessive. Feedback from the change is already positive in the omni thread.
[Nextbit Robin] jabashque:
I meant that as in "what particular tweaks in the custom power hal were causing the lag", though I didn't really make that clear in my previous post.
[Nextbit Robin] shunjou:
Diff the power init scripts and you'll see the changes. I didn't review every line, but it's easy to tell that it's less of a mess. I'm not even the one that authored the commit. I think the main issue was that the big cores weren't turning on reliably or utilizing a greater freq range when they were. I think the governor could definitely use some tuning to improve battery life a bit, but otherwise I can't see your argument that it isn't an improvement. If you have any suggestions, I'd love to hear them.
[Nextbit Robin] jabashque:
Oh, no, I am finding my experience to be overall smoother on Omni with the CAF power hal, but I wanted to know if you were able to narrow down what tweaks were causing the issues. I remember that javelinanddart had pulled in a bunch of tweaks from the sambar (Yu Yutopia) device tree for the Lineage power HAL and was trying to figure out how he could squeeze more battery life out of his Robin.

As for the big cores, well, you didn't change anything in configs/thermal-engine-8992.conf, where javelinanddart had lowered the temperature thresholds for when to turn off the big cores, so the big cores are still unplugging pretty quickly whenever any significant CPU activity is happening.
[Nextbit Robin] shunjou:
I don't think anything is wrong with the thermal throttling. From what I've observed, the big cores turn off when the little cores run at max freq for a certain amount of time, otherwise they most often idle at the lowest freq. I haven't experienced any lag with this behavior. Previously, the little cores were remaining at max freq much more often which kept the big cores from idling on at all. This commit may also have had something to do with it.
[Nextbit Robin] jabashque:
I hadn't observed that big core behavior back on the Nougat-based roms. Instead, I'd end up seeing both the little cores and big cores being slowed down (787MHz for the little cores, 384MHz for the big cores), but the big cores never being shut off.

For what it's worth, on Omni 8.1.0, I went and outright deleted /system/etc/thermal-engine-8992.conf, restarted, killed perfd, then set min big CPU to 2 and set all 6 cores to their highest clockspeeds (1440MHz for little, 1824MHz for bit), and none of the big cores have shut off after a few minutes. The cpus do slow down their clockspeed when I proceed to do any heavy CPU activity, but otherwise, the big cores don't shut off.

Also, to address you thinking that the big cpus not turning on reliably was the main issue: even with the big cpus still not really remaining on, I still have a smoother experience with the CAF power HAL on Omni. There are too many differences in code style between the old power init scripts and the CAF ones though, so I can't really just diff them to see what's different.

EDIT: I only meant to ask you if you knew what specific changes javelinanddart made that cause performance issues, not to try and prove you wrong or anything like that; sorry about that. When I talk about my experience on Omni being smoother, I meant that as in whenever I wake my phone from sleep, I don't have to worry about my phone possibly lagging to hell and back for maybe 5 to even 30 seconds because of heavy IO activity, unlike on the Lineage nightlies. I suspect that the slowdowns and lagginess you're referring to is not the slowdowns and lagginess I had in mind.
[Nextbit Robin] shunjou:
I'm not sure why you're bringing up your experience in N. I think what you said here is in response to an O build? What you said there describes the behavior I mentioned before fairly well.

If you set ro.core_ctl_min_cpu to 2 that would imply that they'd stay on. I don't know why this wasn't the case in your old post I linked, but what you're saying now makes sense.

The big cores do remain on now, idling at lowest freq, and turn off momentarily when the little cores are fully stressed for long enough. If this is a result of the thermal throttling, then I don't see a reason to change it. I'm not sure if it's any different in omni. The only major difference in style I can see is that the caf hal script uses echo instead of write, otherwise they are comparable in the values they assign.

Overall, I'm not sure what you're trying to get at here. What exactly was wrong with the old power hal? Dunno, couldn't tell you, but I doubt anyone could right now since it likely wouldn't have still been an issue. Why spend the time to find an exact fault with a complex part when you can simply replace it with far less effort and get the intended result? You should probably ask the omni maintainer for more info, since he's the one that originally saw fault with it as far as I can tell.

I think we're talking about the same thing. Even on 14.1, the fingerprint scanner would be a bit sluggish. Now it feels more responsive than it's ever been. Still just as annoyingly inaccurate though.
[Nextbit Robin] jabashque:
Yeah, that was why I ended up adding in the EDIT in my previous post after I realized that I didn't really know what I was trying to achieve at the end, especially when you were referring to overall lagginess when interacting with the phone in general and not just when waking the phone up. Sorry about the trouble.

EDIT: It wasn't just the fingerprint scanner that was lagging. Anytime the lag happened, all the UI elements would lag to hell and back too, and it would continue to be that way until all the background I/O activity finished (checked in iotop) . Even then, I don't know if that issue I had with Lineage 15.1 was something that happened only to me, as I hadn't set aside time to clean flash Lineage again to see if it persisted.
[Nextbit Robin] namikiri:
Hi guys. I don't know where to post so correct me if I'm wrong.

TL;DR: I want to fix left and right audio channels by swapping them. What should I do?

Recently I flashed latest LOS Nightly. As you know our Robin has two microphones and two speakers. And LOS uses them wrongly!

Usually when you want to use your phone in landscape orientation you turn your phone in 90 degrees counter-clockwise.

So the top speaker and corresponding mic become left ones.

But they are used by Lineage as right! Audio from the top mic is recorded into the right channel and the right channel of your music is played on the top speaker. That's wrong I guess, so I decided to try to fix it. I use /system/etc/mixer_paths.xml and /system/etc/audio_platform_info.xml file to set up correct routes.

What I want:

Swap mic channels for video recording

Swap speaker channels

Use both microphones when using vocie recorders, as it was in stock ROM.

I could do only the first.

First, I defined the new path and called it "camcorder-dmic-endfire". It's just a copy of "handset-dmic-endifire" with DEC10 and DEC7 swapped.

<path name="camcorder-dmic-endfire">
<ctl name="AIF1_CAP Mixer SLIM TX7" value="1" />
<ctl name="AIF1_CAP Mixer SLIM TX8" value="1" />

<ctl name="SLIM TX7 MUX" value="DEC10" />
<ctl name="DEC7 MUX" value="DMIC1" />

<ctl name="SLIM TX8 MUX" value="DEC7" />
<ctl name="DEC10 MUX" value="DMIC3" />

<ctl name="SLIM_0_TX Channels" value="Two" />
</path>

Then I corrected audio_platform_info.xml as follows:

<device_names>
<device name="SND_DEVICE_IN_VOICE_DMIC" alias="voice-rec-dmic-ef-fluence" />
<device name="SND_DEVICE_IN_CAMCORDER_STEREO_DMIC" alias="camcorder-dmic-endfire" />
<device name="SND_DEVICE_IN_VOICE_REC_DMIC_STEREO" alias="camcorder-dmic-endfire" />
</device_names>

It worked and now I have top mic as left channel and bottom as right.

But I'm stuck with swapping the speakers and mixing both mics into a single channel for voice recording. How to do it? Who can help me with understanding of these files and tell how to do what I want?

When you start recording your voice using any app, a path called handset-mic is used. In the XML file it refers to dmic1. How to make it to use both mics?

Lineage's mixer_paths for ether can be found on GitHub
[Nextbit Robin] witnit:
I recently flashed Lineage for the first time on my Robin. One issue I ran into is with the speakerphone. Regardless of how low I turn the volume, it still seems to be quite loud, so much so that the person I'm talking to can hear an echo of their own voice. Are others of you experiencing this same issue?

My installation:

* lineage-14.1-20180425-nightly-ether-signed.zip

* open_gapps-arm64-7.1-nano-20180423.zip

* Not Rooted
[Nextbit Robin] hairycheez:
Yea think it's been like that for a while. Never use speakerphone tho so
[Nextbit Robin] freddd1:
What is the struggle to push out 15.1?
[Nextbit Robin] malerocks:
Nobody is working on it.
[Nextbit Robin] malerocks:
Guys, I have the latest 14.1 rom on my Robin. No root. I am facing a issue ever since I flashed the rom a month ago. Whenever I am on a call, if I am using the loud speaker the other person is not able to hear me after a few minutes. Only think that fixes it is a reboot but the same thing happens again after a while. There is also a weird disturbance.

Any suggestions how I can fix it.
[Nextbit Robin] Zen12:
Solution

For anyone still searching for an answer, go in settings>notifications>gear button and lower the light brightness completely then turn it back on.then enable and disable notification light
[Nextbit Robin] ted583:
I can't find access point in settings is this available for this room?
[Nextbit Robin] boxes:
My suggestion would be to just run stock N108 build and use the bluetooth battery fix I posted in the general section. Stock 7.1 works great. I always had issues with every custom rom I tried. I flashed magisk from TWRP for the stock 7.1 rom and my wife is happy now.

I tried many LOS 14.1 nightlies up to late march, all of them had issues with the speakerphone, freezing on plugin to charger, and random hard freezes. I also tried OMNI, got TERRIBLE battery life. YAOSP had issues with certain apps crashing and hard freezes. All these custom roms are just super unpolished. I'm currently running LOS 14.1 on an LG G2 with zero issues, and an LG k20 Plus with zero issues except for lack of VoLTE.. Luckily we have a pretty good stock 7.1 rom.
[Nextbit Robin] hairycheez:
This is still the best Nougat rom and has weekly updates. Way better than stock.

Everything works except speakerphone for calls is a little weird.

There are no bluetooth problems and my phone has never randomly rebooted.

Android Pay and everything works as it should (Even with Magisk root which I have). Same with VoLTE.

Also battery lasts all day, way longer than stock. And phone doesn't over heat like it does on stock or OMNI.

I guess when you plug it into the charger with the screen off it might take 5 seconds for the screen to turn on. Can't understand how thats a deal breaker for people. Plug it in with the screen on then. Don't even think this can be called a bug.

Thanks devs
[Nextbit Robin] shunjou:
The "random freezing" was resolved. A dirty fix for plug delay is to strip out the usb driver that causes the issue. The kernel isn't bothered by its absence and functionality seems unchanged. It might have an effect on otg, but that doesn't really matter with this device. A boot image that does this is here.
[Nextbit Robin] boxes:
Any idea when the random freezing was resolved? Last build I used was 5/9 nightly. It also had bluetooth issues, wouldnt connect/pair often times. The phone would also hard freeze when plugged into the charger sometimes, perhaps that was the "random" freezing. After a couple weeks of use it would hard freeze daily. The play music app also would crash/fail to load.
[Nextbit Robin] WoodenMind:
May 14th.

https://review.lineageos.org/c/LineageOS/android_kernel_nextbit_msm8992/+/215097
[Nextbit Robin] boxes:
I checked my downloads and the last build i ran was actually 5/9. I'll have to give it another try
[Nextbit Robin] hairycheez:
Weird. I've been updating every week since probably february and haven't had any Bluetooth or random hard freezes.

Actually I think I did have issues after flashing OMNI and trying to go back to lineage and other ROMs. If you've flashed Omni rom before you should flash to stock using the failsafe method then flash the latest lineage.

Flash Stock - Failsafe Method
[Nextbit Robin] boxes:
Omni was the first rom I tried. (Battery life was awful) I did a factory image restore of n108, so I'll have to try LOS again.
[Nextbit Robin] ptzink:
My wife's Robin freezes a lot to the point where it is not acceptable to use as a "daily driver". Initially, I thought it was the GCam port app that would cause her phone to heat up and freeze until today when it happened when she wasn't using the camera. Unfortunately, I think I am going to have to flash her back to stock and use [MENTION=2018204]boxes[/MENTION] Bluetooth battery drain fix unless someone can point me to an LOS 14.1 fix for the freezing. I have been updating every week for the past 2 months hoping the issue would be fixed, but it persists.
[Nextbit Robin] michaelmcnutt:
I'm not aware of a LOS 14.1 fix, but can share there's a LOS based Oreo 8.1 ROM from crDroid, v4.2, by [MENTION=4258086]firebird11[/MENTION] that I use as my daily driver with Bluetooth, no heating issue, freezes / random restarts only maybe once a week. I use Open Camera vs. the stock app; the ROM works great! Find it here.
[Nextbit Robin] boxes:
Open camera is my preferred camera app. Just enable camera2 API in the settings for much better performance!
[Nextbit Robin] michaelmcnutt:
Thanks! forgot about that option, just tried and it does speed up image capture, especially in HDR mode.
[Nextbit Robin] SeriousGeorge:
I've been pretty consistently seeing around one freeze/reboot a week on LOS. It's just enough to be a bit annoying, but not enough to worry about switching to something else.
[Nextbit Robin] malerocks:
How does one enable that? Care to guide a noob?
[Nextbit Robin] boxes:
It's near the bottom of the main settings page, just click the gear icon.
[Nextbit Robin] DiePirate:
Is this project abandoned? ?
[Nextbit Robin] freddd1:
There is no maintainer right now and unless somebody offers their expertise to become one, newer LineageOS releases will not be available on Nextbit.

OmniROM however does support the latest Android (8.1) on the Nextbit Robin.
[Nextbit Robin] Prospero.X-3:
[MENTION=5795145]javelinanddart[/MENTION] is still making unofficial builds of 15.1 available here.
[Nextbit Robin] freddd1:
Why not offer to become a LineageOS maintainer?
[Nextbit Robin] Raiz:
Maintaining is a lot of work, I think he has other things to do. Maintainers are volunteers that maintain ROMs on their free time , there isn't many people that have the free time and the sufficient knowledge to do that unfortunately :(

He is building unofficially because he's free to do whatever he wants. If he wants to build not regularly, he's free to do so .

Official maintainers have duties , just look the build frequency of LineageOS : once a week . And each time with merged general changes, sometime kernel and device specific changes .

Trust me that's a lot of work .
[Nextbit Robin] dr_vaice:
Is the image flashes to boot, system image or recovery?

Thanks
[Nextbit Robin] shunjou:
Though instead of using 14.1, you're better off using the latest 15.1 build here.
[Nextbit Robin] oshane126(jamaican):
How stable is 15.1? what are the bugs?
[Nextbit Robin] shunjou:
Everything is pretty much working. It's close to being official.
[Nextbit Robin] oshane126(jamaican):
whats not working? And are there any hiccups?
[Nextbit Robin] javelinanddart:
https://xdaforums.com/nextbit-robin/orig-development/rom-lineageos-15-1-nextbit-robin-ether-t3832264

Builds should start next Monday.

The reason it's been so long is I did the majority of the O bringup, then I took a break (and in the meantime, Omni, Havoc, etc. all used my bringup to get O). I put the finishing touches on it, and pushed it from 14.1 to 15.1.

Fun note: Wake on plug lag is fixed in O.
[Nextbit Robin] crpalmer:
Should be fixed in the next build. Another casualty of over enthusiastic cleaning up of the config.
[Nextbit Robin] iluvatrix:
Is 15 May update pulled?

I can't find it on the download page
[Nextbit Robin] :
Yep, the download link was taken down due to a few commits breaking battery percentage and Bluetooth (I think).
[Nextbit Robin] wyntre5150:
I can confirm that Bluetooth and the battery sensor are working again.
[Nextbit Robin] wyntre5150:
Notification Light

I am still getting the stuck notification light on though. Has anybody else updated yet that can confirm?
[Nextbit Robin] crian:
Yes, it still persist.
[Nextbit Robin] ToHellWithGA:
I built locally on the 18th and the battery and Bluetooth issues were both fixed.

I don't see a toggle to enable HDR in the Snap camera app; can that be added to a list of things to improve?
[Nextbit Robin] saltytip:
Coming from the honor5x another phone crpalmer maintains this phone is amazing. Can't wait for all the improvements made to that to trickle I to this build.

Biggest issue I have with it apart from those mentioned is the over exposure with the camera flash but I think he is aware of that already.

Keep up the great work
[Nextbit Robin] LBN1:
2 big cores of the kernel seem off-line. Do others see this too, as I had thought this issue was fixed?
[Nextbit Robin] VenomMOD:
They are enabled when needed. Kernel adiutor shows them being enabled. When undergoing heavy tasks.
[Nextbit Robin] Nintonito:
Does this rom support Vulkan?
[Nextbit Robin] :
According to an AIDA64 test, I'm afraid not.
[Nextbit Robin] iluvatrix:
Does the 0529 version still have notification light issue?
[Nextbit Robin] lentm:
yes
[Nextbit Robin] DECHTECH:
New weekly just got built, hope that fixes the issue!

Edit: It's up now, gonna clean flash and see how it goes.
[Nextbit Robin] lentm:
Yep. The link finally showed up, but broken as of now.

Hope it gets fixed soon.

Edit: Link fixed, downloading.
[Nextbit Robin] xBane_:
Does LOS still have the horrid 'battery optimazation' 'feature'?
[Nextbit Robin] DECHTECH:
This? Also if it is explain why its horrid?
[Nextbit Robin] xBane_:
It limits performance in all games.
[Nextbit Robin] DoobyDroid:
Anybody got link to toolkit one in main thread not working
[Nextbit Robin] carguy303:
For anyone that's running into the notification led getting stuck on, there is a temporary work around to fix it. If it gets stuck on go to the notification settings and select the brightness for the notification led. Rotate the phone into landscape with the brightness selector UI up and when you tap out of it, the led should turn off
[Nextbit Robin] DoobyDroid:
Solution didn't work for me still stays on have to turn it off all together , also when I plug phone into charge if screen off I can't unlock device or will it start to charge I have to remove USB turn on screen then plug into charge and it works , bit odd anyone els experience this
[Nextbit Robin] otonieru:
is VoLTE working on LOS ? tried to search about it in whole robin forum, but cant find specific answer
[Nextbit Robin] lentm:
Yup. These issues made me go back to stock since 7.1.1 came out.

The most reason I want LOS is swapping back and recent buttons; this is resolved by using Custom Navigation Bar app: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner&hl=en
[Nextbit Robin] DoobyDroid:
Quick question I returned to stock N88 by flashing via fastboot I still have TWRP recovery although all ok untill update came up so clicked update now phone stuck on nextbit boot logo , should I just re flash N88 them not update just flash this Rom instead of stock ?
[Nextbit Robin] carguy303:
Stock OTA will not work unless the entire phone is stock. But if you are going to flash stock you should flash the 108 build.
[Nextbit Robin] otonieru:
You now that you can use gravity box to swap that as well right ?
[Nextbit Robin] lentm:
You mean GravityBox for xposed?
[Nextbit Robin] carguy303:
Does anyone else have issues adding tiles to quicksettings from third party apps? I'm trying to add a tile from nougat quick settings and I cannot drag it up into the live quick settings.
[Nextbit Robin] crian:
It's working fine for me.
[Nextbit Robin] carguy303:
It is an interesting issue for me. The tiles for some apps work but not for others.
[Nextbit Robin] anders13:
Hey guys, pretty new here. If I install this ROM, will the smart storage feature still work? I'm sure this is already answered somewhere but I have not been able to find the answer.