yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] javelinanddart:
Yes it would, to both questions.

Perfd is a server that handles certain code values (known as opcodes) sent from the power hal through the client library to change certain system parameters. Some of them are publicly documented, some of them are magic numbers that nobody without BSP (Board Support Package - the source for the proprietary bits) access knows the meaning of.
[Nextbit Robin] jabashque:
Ah, I see. Thanks!

I'm sort of horrified at how much chipset-specific userspace software that one needs to use for Android, but I guess that's how it is. It does go on to show why bringing up a device tree for a newer version of Android ends up being a pain in the ass, though.
[Nextbit Robin] javelinanddart:
New builds:

Changelog for both: Highspeed recording fixed, some other weird recording bugs fixed, thermal throttling toned down, fingerprint enrollment blinking dot fixed

Without input boosting:

http://downloads.codefi.re/jdcteam/...age-15.1-20180311_035750-UNOFFICIAL-ether.zip

With input boosting:

http://downloads.codefi.re/jdcteam/...age-15.1-20180311_041338-UNOFFICIAL-ether.zip

What I want tested:

- UX (fluidity, etc)

- Battery life

I don't care about synthetic benchmarks.

There are also a few misc. kernel patches, so let me know if other stuff starts acting up out of nowhere.
[Nextbit Robin] AndroidLover564:
Are you going to make a new thread soon for these updates? Also thank you for putting your time into these updates, we appreciate them!
[Nextbit Robin] raulrash:
Does anybody else face a crashing phone app when selecting manage conference call option (while on a con call)?

On the 20th Feb nightly
[Nextbit Robin] rahul200023:
I think the problem still remains i flashed the input boosting zip and still see the same pattern on kernel auditor. I ran a stess test in the backgorund, the little CPU's were running at 100% but the big two were remaining at idle

https://drive.google.com/file/d/16kASOxnWFQwYep3absptowMcTxtmx7f6/view?usp=sharing
[Nextbit Robin] javelinanddart:
Maybe a new thread when O nightlies come around. ATM, it's nice staying in this thread because more people know it exists, so more people can/will test when they see it.

FWIW, input boosting has nothing to do with big/LITTLE cores. All it does is boost the CPU frequency (and various other system parameters) to make things smoother.

I'm not sure how I feel about input boost, I haven't noticed a noticeable difference, but everyone has their own tolerance to these things.
[Nextbit Robin] javelinanddart:
Err...I'm seeing breakage on the latest build with video recordings not being saved with the proper length. Looks like I pulled in something that broke it. I'll rebuild later today.
[Nextbit Robin] jabashque:
Currently running the 20180311_041338 build (touchboost one), but ever since at least 20180308_144850, I've been having issues where my phone doesn't ever enter deep sleep when the screen is off. Today, I was able to identify that it's the kernel wakelock "sensor_ind" that's blocking my phone from entering deep sleep.

Running `dumpsys sensorservice` indicates that "BMA2X2 Accelerometer/Temperature/Double-tap" is active and is being used by "com.google.android.gms.persistent", but that's not very helpful because that's literally Google Play Services. (EDIT2: Should also mention that dumpsys was saying that the wakelock for Play Services's connection to sensorservice wasn't being held either.)

I might as well ask if anyone else has the same problem, because if it's only just me, then I need to identify what keeps trying to use my accelerometer when my phone screen is off.

EDIT: still experimenting. Used Privacy Guard to disable Play Services from accessing body sensors, then rebooted, and re-enabled body sensor access. No sensor_ind wakelock to be seen so far, even after running CPU-Z and looking at the sensor info.

EDIT3: My apologies, I made this post far too quickly. This might have possibly been a false alarm on my part, so ignore for now. If the sensor_ind wakelock does get stuck again, I'll post again.

EDIT4: Still find it strange that my phone hasn't ever entered deep sleep mode until only just now (on the 15.1 builds). I'll be watching it carefully.
[Nextbit Robin] eisenbergw:
[MENTION=5795145]javelinanddart[/MENTION], do you guys plan on improving/fixing the bluetooth part? I can't reliably use A2DP or the regular phone connection to my BT car speakerphone. I see lots of othe features that are being fixed, but nothing about BT. If I can help with logs or something else to help troubleshoot, please just let me know what to do to get it to you. Thanks.
[Nextbit Robin] favefan:
i saw the option about aptx in the developer option of bluetooth(los15.1 0311).but it didnt work useable,,,,i have a sony headphone which suppored aptx, so i give more attention on iy....:laugh:
[Nextbit Robin] pattyboi:):
Battery life is pretty solid on non touchboost build...I also have location on high accuracy as well..

..bonus nachos: new thermal limits are mucho better than previous ones,my phone barely ever throttles now since i dont use it too hard,can def notice touchboost being off in usage,but i could really care less for that extra 10 ms for the extra battery life
[Nextbit Robin] Luisalejandroqi:
I'm getting this battery life on the 20180310_170949 build
[Nextbit Robin] javelinanddart:
Completely new power tuning, because why not give it a try?

http://downloads.codefi.re/jdcteam/...age-15.1-20180312_034900-UNOFFICIAL-ether.zip

If it does end up being rotten, I'll start looking as to what broke it.

Battery life observations appreciated.
[Nextbit Robin] pattyboi:):
That enabling lpm is pretty sweet, independent testing of that on the no touchboost build is yielding wonderful results.
[Nextbit Robin] javelinanddart:
This build I linked this morning does have touchboost enabled (at a higher freq than it ever was before), so let's see how it responds. It might be a tad bit more power hungry because the freq is high, we can lower it again if the impact on battery is bad, or keep input boost disabled if the difference between input boost and not is very noticeable.
[Nextbit Robin] rahul200023:
on recent builds im on the one with input boost, and updated to the one u posted today morning. i have noticed some stuttering right when you unlock the phone. for example when i tap the home button it registers as a long press triggering assistant rather than going home, however this goes away after a few seconds.
[Nextbit Robin] javelinanddart:
Was this issue not present without input boost?
[Nextbit Robin] rahul200023:
not sure, i just started noticing it yesterday. other users havent reported anything so I might just need a clean flash
[Nextbit Robin] pattyboi:):
I should have been more specific,I'm still using the original no touchboost build,I just saw that Gerrit commit last night and found it interesting,so I tested enabling lpm on my own,seems to work rather nice,no issues to speak of and battery seems to be pretty improved,may be placebo though
[Nextbit Robin] javelinanddart:
Yeah, I understand - Just saying I want you to test the linked build as well, if you don't mind :)
[Nextbit Robin] rahul200023:
i know this sounds really picky but would you be able to forward port the center clock. It's ok if you don't but i'm sort of ocd about it. Sorry if i sound like im naggin, you dont need to do it if you dont want
[Nextbit Robin] jabashque:
So, I'm still getting plagued by kernel wakelocks preventing my phone from entering deep sleep. However, at least in build 20180312_034900, my phone only drains ~2%/hr with screen off when out and about (at my school), which is absolutely amazing considering it used to drain at approximately 4-5%/hr back on LOS 14.1 (with deep sleep actually happening :P).

I've attached a bugreport to this post just because. I tried running the bugreport through Battery Historian to see what I can figure out about why I'm getting stuck with a kernel wakelock, but maybe some pointers from anyone who's used Battery Historian before would be helpful.
[Nextbit Robin] javelinanddart:
Errr...I just checked my phone and noticed the same. It was fine before I started fiddling with power tunings from another device. Maybe I fiddled a *little* too much. Time to see what broke it.... battery stats are saying it's qcom_rx_wakelock or something. Not sure what that's attributed to. I'll start rolling things back and seeing where it broke.
[Nextbit Robin] javelinanddart:
Would any of y'all be interested in testing outside of XDA, BTW?

IRC, Hangouts, or even a Slack instance might be easier to get real-time feedback with. Discord is not preferred because I can't reliably access it when I'm at school.
[Nextbit Robin] jabashque:
smh go to a school that gives you public IP addressls and the entire range of ports open on eduroam

I'm very interested, sure. Slack, IRC, and Hangouts (in that order) would be my next preferred choices, since your school interferes with Discord for whatever reason.

Slack, because it feels similar to Discord.

IRC, because it's super easy to scroll back or grep for something in the logs.

Hangouts, not as inclined, but I use Google Voice + Hangouts for my telephony needs so I have it always available anyway.

EDIT:

oh no
[Nextbit Robin] javelinanddart:
Eduroam isn't exactly a thing in highschool :/
[Nextbit Robin] pattyboi:):
I can do Hangouts or whatever for testing.
[Nextbit Robin] BearOfXDA:
Can we expect 15.1?
[Nextbit Robin] malerocks:
It is 15.1 that is been discussed here
[Nextbit Robin] Sparubens:
Is Substratum also not working on other peoples phones with latest Oreo build? Phone suddenly rebooted and now Subtratum won't install any theme. Apart from that, stellar Oero ROM with no other issues, amazing for a pre release build
[Nextbit Robin] jabashque:
O-Oh...

I am so sorry. Back when I was a high school student, my school used iBoss to filter traffic, and the damn thing would actually completely block you for 10 minutes and raise a warning for the sysadmin if you tried to start an SSH session because it's "dangerous activity".
[Nextbit Robin] iluvatrix:
Back to official 14.1, will it ever get March security patch?
[Nextbit Robin] javelinanddart:
Thankfully, SSH is allowed.

Testing group:

https://hangouts.google.com/group/liXr36fCJv32Lq5h2

I haven't found a fix for our deep sleep issue, but I think I do know what is causing stuttering. There's a lot of permission failures all over the place, with files perfd is trying to access.
[Nextbit Robin] JaN0h4ck:
Substratum worked for me, exept for system apps, with Swift Dark on "lineage-15.1-20180308_144850-UNOFFICIAL-ether".
[Nextbit Robin] NurKeinNeid:
"Substratum doesn’t work well with*March Oreo security patch*for Nexus\Pixel. If you install the overlays, they can end up not enabled at all. They may also not even show in the ‘Manager’ tab. To enable them if they don’t even show in ‘Manager’, open the theme again after rebooting, pick the same options that you installed the theme with, select all and use the ‘Enable selected’ option in the theme overlays list. The overlays should then be enabled and can be handled as normal. The procedure might be required for new overlays. This has absolutely nothing to do with the theme overlays code and is not a thing we can fix with a theme update, it depends on the theme engine and the code changes by Google." -copied from swift black faq

But it's only a line or two of code that needs to be removed. Those cheeky people at Google snuck a bit of the P code in this months security update, thinking people would blindly merge it.

Most Custom ROMs have already fixed this.

just fyi ;)
[Nextbit Robin] Darkstar_Devil17:
Is there any Volte related bug reported in this Rom, as I'm facing it in every oreo Rom for ether.

Someone please tell me if it could be fixed.
[Nextbit Robin] Methawin:
Oreo

Anyone can tell me?How to get oreo for ether? (except crdroid)
[Nextbit Robin] Rimmer1966:
http://downloads.codefi.re/jdcteam/javelinanddart/ether
[Nextbit Robin] malerocks:
Read the instructions on the 1st page.
[Nextbit Robin] Sparubens:
Thanks dude, flashed latest build now and now everythings applying :)
[Nextbit Robin] KUJO1001:
Anybody having issues using Google camera on the latest build?
[Nextbit Robin] boxes:
Running the nightly 3/7 build of 14.1 and it works perfectly! Absolutely no bugs and great battery life. The charge-freeze bug is gone, the speakerphone volume is normal, bluetooth pairs normally every time too. I think I'll be sticking with this build.

I saw a dev talking about trying to fix the freeze on charger plug-in bug, but never saw a post about having found a fix. Glad that they got it worked out!

Edit: wont seem to go into deep sleep now. Not sure if it did this originally, as its my spouses phone so I just look at it here and there. Guess I'll try the 3/14 build
[Nextbit Robin] malerocks:
Any news to share on the Oreo build?
[Nextbit Robin] javelinanddart:
If you want to try the O builds, there's a lot of BT differences in O.

For those that aren't in the hangouts group, most recent build: http://downloads.codefi.re/jdcteam/...age-15.1-20180316_150334-UNOFFICIAL-ether.zip
[Nextbit Robin] malerocks:
I won't be able to test builds, but can I join the hangouts group just to know what's happening with the Oreo since not much is posted here now? Just so I am aware of what the issues currently are.
[Nextbit Robin] jabashque:
I mean, I don't see why not. The hangouts has around 30 people, but only 5 of them (including me) even talk; the rest just lurk.

And lurking is perfectly fine.
[Nextbit Robin] shnnxn:
i want to join the group where is the link
[Nextbit Robin] :
I can confirm this as well. After turning on the notification light option for the first time, it stayed on constantly. I had to reboot to get it to turn off. This seems to be triggered by using the brightness level slider. Once that's used, the light doesn't seem to turn back off.
[Nextbit Robin] lentm:
I'm trying to reproduce this bug to get the logs out, no luck yet or am I lucky for not having it anymore. :silly:
[Nextbit Robin] crpalmer:
What brightness level slider?
[Nextbit Robin] :
In the notification light options, there's a brightness level setting that pulls up a slider. I've attached a screenshot of where I found this.
[Nextbit Robin] ron580:
Hey crpalmer! is it possible to have the cloud leds function as a notification light? thanks for your work.
[Nextbit Robin] VenomMOD:
Anyone else notice a screen of static for an extremely short time before the screen turns on when locked? Happens at random sometimes.
[Nextbit Robin] :
I can confirm this as well. I haven't been able to figure out a pattern for when it will happen, either.
[Nextbit Robin] AnierinB:
I've gotten the same issue on all the latest ROMs besides omni.

Looks sorta similar to when you turn your screen off and back on in twrp right? B&W static
[Nextbit Robin] VenomMOD:
Correct. I suppose it's just a software bug.
[Nextbit Robin] crian:
What is the release cycle of new builds?
[Nextbit Robin] lentm:
Every Monday

---------- Post added at 01:24 PM ---------- Previous post was at 01:22 PM ----------

Today's build shows the battery stats as 50% when it's not.
[Nextbit Robin] keanuk:
Bluetooth and battery issues on latest update

The May 15 update won't let me turn Bluetooth on again, the button just grays out and becomes unresponsive when tapped in the settings. It looks like the battery indicator is stuck at 50% too even though TWRP is giving me a different value. Anyone else having these issues? I updated from the May 8th release.
[Nextbit Robin] crian:
I can confirm that Bluetooth isn't working. I did a clean flash.

My battery was below 50% after the clean flash, so I can't report something to the battery indicator stuck. Will see it tomorrow.

The volume keys are controlling media sound and not the ring tone by default.
[Nextbit Robin] VenomMOD:
Stuck here at 50% too.
[Nextbit Robin] crpalmer:
Battery percentage problem should be fixed in the next build. Looks like someone was being too aggressive about cleaning up "unused" parts of the kernel and broke that not long before the automated build was started.

Sorry about that!
[Nextbit Robin] XxXPachaXxX:
Despite the bugs introduced in latest build, how is it generally performing? Compared to Omni?
[Nextbit Robin] VenomMOD:
Very snappy and is close to Omni, maybe even the same as Omni's performance. Also, battery life is way better then the old builds with the latest release.
[Nextbit Robin] crian:
I dirty flashed the latest build over the clean flash and the battery indicator bug and volume keys bug are gone.

Only Bluetooth isn't working. Can you do something with over exposure while using the flash on snap camera?

---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------

With latest build it's very smooth. No performance issues and battery seems identical.
[Nextbit Robin] iluvatrix:
So Bluetooth is confirmed broken?
[Nextbit Robin] crian:
Yes
[Nextbit Robin] NaterTots:
Go back about 7 posts
[Nextbit Robin] boxes:
Im having a peculiar issue with the 3/7 build of 14.1. If i install ex kernel manager and apply any settings, or kernel adiutor, then my robin wont go into deep sleep. Obviously this kills standby battery life. After uninstalling them all is normal. I guess ill try the 3/14 build sometime, but otherwise the 3/7 build has fixed all the little issues for me.

update: re-installed EX Kernel Manager and only changed two settings, max/min big cores online: 0 for better battery life. Now it will go into sleep fine. So one of the other settings was affecting deep sleep.
[Nextbit Robin] Mchasard:
Is there another link cause by me its very slow.thé download allways stop..it would be useful to get this group link....thanks
[Nextbit Robin] Mchasard:
Which twrp version should work to flash 15.1 lineageos ?

I triée with 3.1.1 it doesn't work i have an error
[Nextbit Robin] :
Try this one.

https://androidfilehost.com/?fid=817906626617957398

It's from this page

https://wiki.lineageos.org/devices/ether/install
[Nextbit Robin] Mchasard:
Thanks otherwise how functional is this ROM 15.1?

---------- Post added at 09:29 AM ---------- Previous post was at 09:04 AM ----------

Thanks I just succeed to flash it
[Nextbit Robin] rahul200023:
Functionality on the 15.1 rom is pretty good. However, I wouldn't say it's as refined as current nougat builds, but that is to be expected given its early status. Battery life is also pretty good, i have been able to test everything with the exclusion of nfc. It's definitely worth a try. Also whenever ur flashing a new android version its always a good idea to flash the latest twrp first.
[Nextbit Robin] VenomMOD:
Data doesn't work on AT&T for the latest 14.1 build. (Data works on previous builds and 15.1 Unofficial)
[Nextbit Robin] malerocks:
Which camera app would you all recommend to use with the 14.1 version of LOS?
[Nextbit Robin] boxes:
The stock camera is decent, especially for panoramas. Opencamer is good too, just enable camera2api in the settings, has a good hdr mode.

---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------

The 3/7 14.1 build is flawless for me on at&t. Try it out.
[Nextbit Robin] pintasmapila:
What GApps do you guys recommend for oreo version?
[Nextbit Robin] demeez:
Rom comes with gapps and root.
[Nextbit Robin] Methawin:
Fingerprint

Is fingerprint working perfectly in lineage 14.1 ?
[Nextbit Robin] pintasmapila:
Not sure. Ir works fine in version 15
[Nextbit Robin] The Nub:
It's been working perfectly fine for me on the most recent build of 14.1
[Nextbit Robin] Methawin:
Official lineage 15.1

When Official Lineage 15.1 release ?
[Nextbit Robin] VenomMOD:
Whenever they release it ¯\_ (ツ) _/¯
[Nextbit Robin] Darkstar_Devil17:
Is there anyone who can help me out. I can't make Voice calls on any of the Oreo Rom currently available for Robin.

How could I trigger this?
[Nextbit Robin] vagaba1:
There are two dialers, actually.

One of them can be erased. Do that and use the other one.

"Ooh, but where is the other one?"

I use Nova Launcher, so i just searched and pinned to the homescreen.

Hope this helps!
[Nextbit Robin] Darkstar_Devil17:
There is no other dialer and I've also seen Volte unavailable in testing menu (*#*#4636*#*#). Now what? :confused:
[Nextbit Robin] Rex2018:
Link offline

please, someone can post the rom 15.1 again
[Nextbit Robin] WoodenMind:
http://downloads.codefi.re/jdcteam/javelinanddart/ether
[Nextbit Robin] EAT_CHICKEN:
My WiFi on the newest build is unusable. It's so slow. Anyone know a fix? A build without the issue?
[Nextbit Robin] Rex2018:
dude thanks a lot, great rom.
[Nextbit Robin] Sparubens:
Is there a way to remove gapps from the rom package? Would like to try MicroG
[Nextbit Robin] Sandivisi:
how to update lineage os if i installed magisk? help
[Nextbit Robin] hairycheez:
Works great. Thanks a lot
[Nextbit Robin] :
Just Install the update. Magisk will be automatically reinstalled.

Also make a backup before updating.
[Nextbit Robin] tlxxxsracer:
coming from AOSPA.. I tried to flash 15.1

I get an "ERROR: 7" E3004: package is for device: ether; this device is ,

Update: Had to update my TWRP version. Flashing fine
[Nextbit Robin] Sarzeck:
received an update today and after install my phone rebooted into recovery. This happen to anyone else?
[Nextbit Robin] SeriousGeorge:
No issues installing today's update, but it does include a "hilarious" april fools prank you'll have to deal with. Skip it. I ... words fail me. I don't even know how to respond to developers that think putting this **** in an operating system is a good idea.
[Nextbit Robin] Sarzeck:
I only got this phone last week, all the zips are still there from when I flashed them over the weekend. But even trying to flash them again it still keeps rebooting into recovery...I'm away from home and don't have adb with me. Don't know how to fix it. Luckily I brought my backup phone....
[Nextbit Robin] Methawin:
Can u help me how to remove LineaGenuine notification?
[Nextbit Robin] hairycheez:
Flash magisk 16 zip then reboot
[Nextbit Robin] SeriousGeorge:
You can boot into TWRP and go to the terminal there. Type in the following and then reboot.

setprop persist.lineage.nofool true
[Nextbit Robin] cramrobin:
:cool:
[Nextbit Robin] Sarzeck:
Didn't work. I can't get this thing out of recovery. I just tried flashing the stock rom and same thing.
[Nextbit Robin] marvelljones:
Shot in the dark, but have you tried uninstalling Magisk and then trying to boot? It shouldn't be the problem, but it's remotely possible.

You might have to wait until you are able to adb from your PC again. Sounds like you need to wipe everything, reboot into recovery ignoring the no OS installed message, then start a fresh install.
[Nextbit Robin] Sarzeck:
I am back home with adb now. What should I try? I've tried flashing Lineage, the flashable stock rom, AICP. No errors and TWRP doesn't give any warning that there is no OS, but still just reboots into recovery.

EDIT: Disregard, I am an idiot :( I wasn't on the latest recovery somehow. updating to the latest recovery let me flash the current lineageOS rom...
[Nextbit Robin] oshane126(jamaican):
Has the wifi problem been fixed in the latest version?
[Nextbit Robin] boxes:
Anyone know if the freeze on charger plug-in has been fixed in the latest 14.1 builds? I'm currently running the 3/7 build of 14.1 and its extremely solid. The speakerphone volume was fixed, and it only freezes on charger-plugin sometimes. Absolutely no bugs otherwise, which makes me skeptical to try a new build. With how solid nougat is, I really have no urge to try oreo.

I also run the phone with both big cores disabled (max big cores online = 0) to get better battery life, usually 4-5 hours screen-on time. Phone is still very smooth.
[Nextbit Robin] jabashque:
The freeze on charger plug-in hasn't been fixed. javelinanddart did fix the issue where sometimes, trying to turn on the screen with the power button results in a deadlock and the screen never powering on, but it's only in the lineage-15.1 branch, not cm-14.1 branch.
[Nextbit Robin] oshane126(jamaican):
Why is it that in cpu z my phone is showing me 4 cores running and the other 2 stopped