yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] javelinanddart:
OK - That patch was shipped.

Next nightly should have working RIL. Another one of the changes that went into that pulled build was that we use an opensource camera HAL now.

If you were having touch to focus issues, that now seems to be fixed.

More bugs I'm aware of:

- GPS is crap

- WiFi drops out

- Device lags when waking by plugging in USB (maybe just me?)

- Sometimes device fails to turn on after sleep (maybe just me?)

- Device shuts off in cold weather sometimes (happens on stock too)

If you have any other bugs that you can think of, let me know. These are what I've noticed on my ether. I don't care about small things like broken wifi calling or volte, just FYI.

If you're having GPS and/or WiFi issues, and are willing to wipe to try my build, try flashing this build:

http://downloads.codefi.re/jdcteam/...age-14.1-20180127_025946-UNOFFICIAL-ether.zip
[Nextbit Robin] jabashque:
So, among the bugs you listed:

- GPS is crap

What do you mean by that? I know that the current ether builds don't use the GLONASS satellites at all for GNSS, but are you also talking about GPS accuracy?​

- WiFi drops out

Thankfully, I've either haven't experienced this bug, or it happens infrequently enough and lasts short enough that I don't notice.​

- Device lags when waking by plugging in USB (maybe just me?)

Happens to me occasionally too. Sometimes when I plug in, the device is completely unresponsive for maybe 5-10 seconds before I finally hear the charging sound and see the screen turn on. Pressing the power button does nothing too. I know mikeNG tried improving this problem with this commit, and maybe it might be placebo, but I think (?) my device doesn't lag as often anymore whenever I plug in, at least compared back to September/October last year. Maybe I should note the time every time this happens and grab a logcat and dmesg too, if that would help with tracking down this issue.​

- Sometimes device fails to turn on after sleep (maybe just me?)

Happened to me quite often back around September/October last year. Ended up clean-flashing to OmniRom... and then back to LineageOS again about a month ago since the kernel in OmniRom doesn't let me turn off the big cores. Since then, this has happened only once, which was today, but then my device actually woke up after I plugged it into my computer. Need to remember to grab time of occurrence and logs next time.​

- Device shuts off in cold weather sometimes (happens on stock too)

Not a problem with California weather :D​
[Nextbit Robin] pattyboi:):
currently running latest build with the extra gps + wifi commits,i never have wifi issues so i cant comment on that,my gps seems slightly faster,might be placebo,but i havent had it bounce my location around randomly like it used to,which is rather nice,i dont really have screen on lag,and even in PA in the negatives i havent had the device shut off on me,also,RIL is working just dandy.

awesome work as always.:good:
[Nextbit Robin] javelinanddart:
On GPS:

- Yes, I've had accuracy issues and I've noticed my location jump around at times. I've never been able to get GLONASS to work, unfortunately.

On WiFi:

- Generally I've noticed it as WiFi not being connected when I turn my phone on in the morning.

On wake-on-plug lag:

- Yeah, I guess it's now OK for mike, but I still have lag (up to 10 or more seconds sometimes)

On SODs:

- I don't have a reproducible test case unfortunately, but I disabled an overlay that might be causing that in the build I linked (it was checking prox sensor before waking device, which even the overlay says may make the device fail to wake reliably)

On cold weather shutdowns:

- Heh, it certainly is a problem in my Minnesota weather :)

For cold weather: It generally does take extended exposure, but it could also just be my battery getting old.

Thanks for testing. Do you mind doing some extended testing with GPS and/or WiFi? (WiFi I can do here, it's GPS that I don't have the chance to test too often)

Since this falls into the category of "improvements" rather than "full on bug fix", it's probably best to give it a little longer.
[Nextbit Robin] shunjou:
On GPS / WiFi:

- I haven't noticed anything too bad myself. If the vehicle is actively moving, GPS is OK. As for wifi, I only notice a bug where when the device connects to 5G after initially connecting to 2.4G, the quick setting tile still reflects the name of the 2.4G SSID rather than the currently connected 5G SSID as shown in full wifi settings and confirmed on router. This is fixed by toggling wifi on and off manually.

On wake-on-plug lag:

- This is definitely still there, even after that commit. It only seems to happen if plugged in while off and the device has had a chance to enter deep sleep though.

On SODs:

- I've gotten this about twice the whole time using the device. At first I thought it bricked for some reason because it wouldn't recover for about 10 minutes no matter what I did. It hasn't happened for a long time though.

On cold weather shutdowns:

- I haven't gotten this myself yet.
[Nextbit Robin] pattyboi:):
Update on GPS:so far,after 2 hours of walking through town,and around a hour on a bus going through 2 different cities,I only bounced once,and it kept on my location damn near perfect aside from the occasional stall (I think it was due to connection issues)
[Nextbit Robin] jabashque:
[MENTION=5795145]javelinanddart[/MENTION] I nearly forgot to ask, do you have issues with speakerphone call volume range being nearly exactly the same as normal call volume range, i.e. barely loud at all? It makes trying to do speakerphone and video calls over the phone, Hangouts, FB Messenger, etc. very hard when I can barely hear the other party.
[Nextbit Robin] javelinanddart:
I don't use speakerphone, so I don't experience the issue, but I've heard of it. Do you recall if this was an issue in cm-13.0 as well?

And thinking on it a little bit more (about more bugs), I know certain FLAC files have issues playing, and I've occasionally ran into https://www.reddit.com/r/LineageOS/comments/7tf9ue/problem_charging_to_100_ether/ as well.
[Nextbit Robin] jabashque:
Unfortunately, I can't answer about whether that had been an issue in cm-13.0 because that had been discontinued over half a year before I got my Robin (July 2017).

All my music is in ~70kbps opus, so I never tried playing FLAC files on my device ?. I also personally haven't run into that sort of charging issue, so I can't comment on that or provide any logs.

EDIT: Also before I forget, the battery level tends to drop directly from 91% to 89%.
[Nextbit Robin] javelinanddart:
Managed to fix 24-bit FLAC playback. Here's a test build with some audio changes that may help speakerphone: http://downloads.codefi.re/jdcteam/...age-14.1-20180128_031045-UNOFFICIAL-ether.zip

Bugs remaining that aren't fixed:

- Wake on plug lag

- Charging sometimes just doesn't work

- Battery shutdowns in cold (maybe just my old battery)

- Actuator clicking (happens on stock too)

- Speakerphone

Bugs that may or may not be fixed:

- SODs

Bugs that seem to be fixed:

- WiFi drops

- GPS

- 24 bit FLAC playback
[Nextbit Robin] jabashque:
Hey, thanks for the test build.

So, I should probably clarify that the speakerphone volume range is actually slightly lower than the normal phone volume range, which makes speakerphone mode pretty much useless, haha.

Now with that clarification out of the way, this test build didn't end up fixing this bug, unfortunately. Not only that, but it introduced a new bug where any time the default vibration was being used (e.g. navbar button presses, dialer button presses, lock screen pin button presses, opening the app drawer in Trebuchet, tap-and-holding on an app in Recents), the phone vibrates twice for each event instead of once. Cases like the AOSP keyboard, which I assume uses its own custom values for vibrations, don't have this issue.

If this doesn't happen on your side, I'll be able to get necessary logs tomorrow when I can reflash the test build on my phone.
[Nextbit Robin] javelinanddart:
Haptic thing was my bad. It sounds like the amplifier isn't being properly enabled on speakerphone, I'll look into that.
[Nextbit Robin] javelinanddart:
[MENTION=8079424]jabashque[/MENTION] Try this for speakerphone: http://downloads.codefi.re/jdcteam/...age-14.1-20180128_152637-UNOFFICIAL-ether.zip

It has a few different haptic tunings now as well.
[Nextbit Robin] jabashque:
Glad I kept my TWRP backup from last night!

Can confirm that the AMP HAL is indeed amplifying the audio output with speakerphone mode in both Hangouts and the normal dialer (I can't make any calls with my FreedomPop sims, but I can listen to AT&T on the phone telling me that I'm not allowed to make outbound calls on my sim ?).

Also, haptic feedback no longer vibrates twice, thanks! If the haptic feedback is supposed to still be slightly different compared to the pulled 2017-01-23 nightly, it was too subtle for me to notice, sorry.
[Nextbit Robin] javelinanddart:
So speakerphone bug is fixed? And yeah, haptic change was probably very subtle.
[Nextbit Robin] jabashque:
Yep, I'd say the speakerphone bug is fixed.
[Nextbit Robin] javelinanddart:
That patch will make its way into this week's build, enjoy
[Nextbit Robin] jabashque:
Thanks! I'm glad to see that you've been actively fixing the issues with ether recently.
[Nextbit Robin] pattyboi:):
[MENTION=5795145]javelinanddart[/MENTION] awesome job on squashing bugs dude.
[Nextbit Robin] jabashque:
[MENTION=5795145]javelinanddart[/MENTION] quick update: I've started getting more occasions where my ether doesn't wake up from sleep mode on pressing the power button. BUT, it seems that plugging it into my computer causes it to wake up. Let me know what logs to grab besides a dmesg and logcat the next time it happens
[Nextbit Robin] javelinanddart:
Hmm... I was hoping there'd be less of that. Out of curiosity, do you enable proximity check on wake? (Settings -> Display -> Prevent Accidental Wakeup)

If so, try turning that off. Those two logs should be enough.
[Nextbit Robin] jabashque:
Nope, I do not have that setting enabled.

Will post again once I have some logs.
[Nextbit Robin] javelinanddart:
For those with wake on plug lag, please try flashing this image: http://downloads.codefi.re/jdcteam/javelinanddart/ether/etherusbnew3.img to the boot partition, and see if the issue persists

It seems to fix it for me
[Nextbit Robin] Sparubens:
Thanks for developing for our device. I don't ask for ETA's on here but as development seems a bit dead now on this device, I'd like to ask if you're working on Lineage OS 15.1?
[Nextbit Robin] javelinanddart:
I most likely will be. I might be the only one who still cares about this device. I've been dragging my feet, I probably should/will get started soon.
[Nextbit Robin] jabashque:
tfw three official maintainers for ether but the only dev actively working on the device isn't even listed on the wiki

In any case, lemme check if the boot image you provided works. I tried it earlier but patched with Magisk, and I was still getting up to 15 seconds of delay when plugging in, so I need to rule out any possibility of Magisk interfering with that first by using the boot image as is instead.
[Nextbit Robin] shunjou:
Seems to still have some delay when waking on plug, usually when the device has been idle for at least a minute and the screen is off.
[Nextbit Robin] jabashque:
All right, can confirm screen-on delay upon plugging in is still happening.

Logcat and dmesg attached. Plugged phone into computer at 15:51:22, screen turns on at around 15:51:32. dmesg was captured at 15:53:20, if that helps with trying to locate the time when the screen on delay happens in the dmesg log.
[Nextbit Robin] javelinanddart:
EDIT: Oops, double post.
[Nextbit Robin] javelinanddart:
Hmmmmmmmmm....I swear it worked in a previous revision of this patch...

I'll keep playing with this tomorrow (build server is down), thanks for all the feedback.
[Nextbit Robin] jabashque:
No problem. Thank you for continuing to work on this device in the first place!
[Nextbit Robin] pattyboi:):
should fix ya donate button homie ;););););)
[Nextbit Robin] javelinanddart:
I'm going to give a quick rundown of what the issue is, but my further experiments were still unfruitful.

The USB device is controlled by i2c, and for power saving, it's disabled in suspend. When plugging in to wake the device, the USB controller driver is attempting to do something with the I2C device before it is ready, which messes up the I2c resuming process. This is causing the wake-on-plug lag that we are seeing. I'm not really sure what to even attempt as a fix/workaround here. It's possible that the hack I've been playing with is timing out, so I'm trying without any kind of timeout (the hack is to stall interrupts in the controller until the controller has fully suspended). This is the test boot.img http://downloads.codefi.re/jdcteam/javelinanddart/ether/etherusbmaybe.img. For those that are curious, https://review.lineageos.org/#/c/204874/ is the hack I've been using, I removed the timeout code locally as a test, and compiled the boot.img I just linked without the timeout. Feedback appreciated.
[Nextbit Robin] jabashque:
I'll be trying this out in a bit, but out of curiosity, have you checked what Gandalf does for his OmniROM build? I hadn't had screen-on-plug-in delay issues or any sort of failure-to-wake-on-power-button issues when I used it before.
[Nextbit Robin] Arktronic:
Ether on LOS appears to be unable to use roaming data, at least with a T-Mobile US SIM. When roaming data is enabled (or disabled) and an "R" roaming indicator is shown, cellular data simply refuses to work. The TMo plan is fine as the SIM works in other phones, and the APN config seems to be correct. This was happening before the recent RIL changes, so those aren't to blame.

Is anyone able to confirm this roaming data issue?
[Nextbit Robin] pattyboi:):
As a temp workaround could we disable the suspend of the co troller? Obviously this would increase power consumption but for those who get the supppper long delays it could be worth it.
[Nextbit Robin] javelinanddart:
It seemed to only be with Edge data (2G) for me, but I was unsure if it was just me because IIRC I was on the MM baseband at the time. If you get some radio logs from boot (adb reboot && adb logcat -b radio > radio.log), I could try to take a look, although I recall being confused last time I looked.

I've been considering that. I'll have to test it and gauge the power consumption of such a hack to see whether or not I'm OK with it. If I'm not, I'll release the boot.img here to for people who prefer that to the wake on plug lag.
[Nextbit Robin] pattyboi:):
for (i = 0; i < I2C_RETRY_MAX; i++) {
ret = i2c_transfer(i2c_bus, &msg, 1);
if(ret != 1) {
pr_err("I2ci(W) retry 0x%02x:0x%02x: 0x%02x \n",device_id, offset,*values);
ret = -EIO;
msleep(20);

this is in hd3ss3220_platform_i2c.c,maybe that msleep has something to do with it? could we possibly be triggering the max retry for i2c before we resume and that msleep causes that lag?

...eh,nvm,dont see anything in the logs related to the error it prints.
[Nextbit Robin] Arktronic:
Log PM'd.
[Nextbit Robin] javelinanddart:
The fix will make its way into today's build, you can test it by resetting your APN settings from the settings app, and check if data connects with the T-Mobile US LTE APN. I went ahead and consolidated the MMS APN into the main APN as well, because that's how T-Mobile does it. I verified that it works here here (I'm on T-Mobile US with my Robin, and I'm currently in the states), so if you could recheck that, that would be awesome.
[Nextbit Robin] crimsonyellow:
lineage-14.1-20180206-nightly-ether-signed.zip

Installed this build today. New to this whole flashing thing. Apologies if i'm posting this on the wrong thread. please do redirect me if I am.

Moved to Lineage Today. Was hoping for Razer to give out a good update before they stopped all support but clearly they burned that bridge.

I went through this thread as well. Any solution on the battery notification light. The one at the bottom of the phone. Doesn't seem to turn on or do anything.
[Nextbit Robin] pattyboi:):
Its actually "backwards" on lineage,the blue light on the bottom is the notification light and the cloud lights are the battery lights.
[Nextbit Robin] crimsonyellow:
So the notification light doesn't work but the cloud lights are working perfectly

Also, I've installed the nextlit app for the cloud lights as well. Can this cause any issues?
[Nextbit Robin] Arktronic:
Awesome, thanks! The new settings work in NL without issue. I thought there was a problem with them during my connection in Heathrow, but a reboot fixed that.
[Nextbit Robin] naveed.hasan:
I am having very poor GPS signal acquisition and location fix on the 2018-01-30 build - where I see many GPS updates in the changelog. This is on multiple devices that were actually doing pretty well, even indoors with GPS location where as now it takes multiple minutes to lock outdoors.
[Nextbit Robin] James1o1o:
Torch not working for anyone else either? From the quick settings?

Also getting some rather large phone idle battery drain. Not much, but a good 15% over the course of 8 hours or so.
[Nextbit Robin] WoodenMind:
I have the same issue with every ROM. Either use another app to turn on the flashlight or wipe the dalvik cache from twrp, that should enable the quick setting. However if you then do another reboot without the wipe it'll probably fail again.
[Nextbit Robin] Arktronic:
I've not seen any issues with the torch functionality on recent builds.
[Nextbit Robin] :
Press the edit icon (pencil) on top of the quick settings. then go back. This should enable the torch button. It worked for me. but it became gray after every reboot. Also it's working fine in recent builds. Have you updated to the latest build
[Nextbit Robin] VenomMOD:
Has battery drain improved for anyone else on the latest build? :confused:
[Nextbit Robin] linckandrea:
I have abnormal battery drain on last build
[Nextbit Robin] pattyboi:):
Even after a clean wipe and install,I'm getting INSANE cpu frequency jumping on the latest build. Literally every nanosecond the frequency is increasing or decreasing. Gonna go back to a previous build tomorrow and also look in the logs.
[Nextbit Robin] KUJO1001:
I have had issues on the latest build where my phone will go into a deep sleep and wont wake up for a long time although if I plug it in the notification light will flash
[Nextbit Robin] James1o1o:
Happy to say that the battery drain on the latest build has been fixed for me.

Seems this fix here did the trick.

https://review.lineageos.org/#/c/207112/
[Nextbit Robin] Sparubens:
Audio is really bad the last months. Very distorted at low volumes
[Nextbit Robin] DiePirate:
For me is working like a charm. Very smooth. Good SOT. I think the sound can be better.

Edit: I dont know why too much errors in logcat.

Edit2: 4hrs SOT heavy usage. 7hrs power on.
[Nextbit Robin] eisenbergw:
Hi,

Just started using LOS, and the latest update was downloaded to the phone and wants to install. Will this update process behave like a fresh load, wipe data, etc? Do I need to run a full backup before letting the upgrade happen, or is this just an incremental thing that won't disrupt all the installed apps, etc?

Thanks,
[Nextbit Robin] :
No. it won't wipe data.

Yeah. Make a backup. Just in case anything goes wrong.

Yes. Just an incremental thing.
[Nextbit Robin] vegasjj:
Hi,

I've been looking forward to buy this phone but just today the people of LineageOS announce the release of the Oreo version, i guess my question is if there is a chance for Robin to be upgraded to 15.1 in the short term or should i start looking for another phone...? Also, has someone had any issues with the fastboot drivers for this phone? The universal adb driver does the trick? The last thing i need right now is not been able to install LOS, i'm not at all interested in the stock ROM for this device.
[Nextbit Robin] pitchdarkice:
Ideally you want the latest platform tools for your os.

https://developer.android.com/studio/releases/platform-tools.html

It works without an issue. I used it in Linux.

As for Oreo and 15.x, my understanding is we need some updates from Razer which do not appear to be happening.
[Nextbit Robin] javelinanddart:
Sorry about the frequency thing. It was well intentioned, but I guess it backfired.

Been working with sultanxda for our wake on plug lag issue, as he knows more about the kernel than I do.

Experimental boot.img here: http://downloads.codefi.re/jdcteam/javelinanddart/ether/etherbootusbhopefullyworks.img

EDIT: Looks like I may have screwed something up. Device is hard rebooting a lot.
[Nextbit Robin] pattyboi:):
May I ask what you changed/tried? Possibly that new i2c patch on sultans github?
[Nextbit Robin] javelinanddart:
Yes, that's exactly what I tried. At risk of stating the obvious....https://imgur.com/r/gifs/IgU4Y
[Nextbit Robin] pattyboi:):
Lmfao,trailer park boys is the best show ever.

In regards to the current issue though,have you found any hint in the kernel log? I keep checking mine to see if some magic error will give me a hint to what to check out,aside from finding a log message,I'm kinda lost on how to help...
[Nextbit Robin] DiePirate:
Sorry for my english, I think sultanxda can check all the kernel source and make the best changes for our device. He is a monster kernel developer.

Thank you [MENTION=4800121]Sultanxda[/MENTION] and [MENTION=5795145]javelinanddart[/MENTION]
[Nextbit Robin] javelinanddart:
The kernel wasn't even logging the reboot reason while it's just rebooting when sitting on my desk, so no. When the device is on, I can't seem to replicate the wake-on-plug lag, but the loss of stability is a huge issue

Sultan does not own this device, and is helping me debug this out of the kindness of his heart. He will not be checking our entire kernel source because I can't ask him to do so -- It's not his device.
[Nextbit Robin] HoganSam123:
Any update on Oreo?
[Nextbit Robin] eisenbergw:
Hi,

So I've been running the latest weekly of LOS 14.1 (Feb 20) on my Robin now, and although it's been a good experience so far, I am thoroughly frustrated with the Bluetooth part. It is by far the worst compatibility I've ever had between my phone and my car (the multimedia system/bluetooth mic/speaker is based on KitKat. No I did not make a typo.) The official Robin image was ok, but had a few hiccups. This is a disaster and basically useless. Is there anything I can do to troubleshoot it? Are there logs I can gather? I see an entry in the developer options for 'enable bluetooth hci snoop log'. Would that be helpful? I can get into the details of exactly what behavior I am seeing if someone is interested in listening to them.

Thanks,